> And it was fixed in
>
> http://commits.kde.org/oxygen-gtk/878b0e626311cdf847e00dfd6ff96184021c1667
> http://commits.kde.org/oxygen-gtk/f272b269cd26e783ffb811c4a3584a675fac7a2b
>
Well, in fact the correct _fix_ commits are these two earlier:
http://commits.kde.org/oxygen-gtk/a515ab451f54cbc930d0a0
Hi,
> No need to open two reports for the same bug, you can reassign instead.
Sorry for this - I'll do that the next time (still have trouble with the
BTS interface sometimes). Thanks for doing this for me :)
> I've investigated a bit and this is a bug in the oxygen engine and it
> affects both t
reassign 707774 gtk2-engines-oxygen
forcemerge 707774 707699
affects 707699 gtk3-engines-oxygen
thanks
Hi,
On 11/05/13 10:19, Ralf Jung wrote:
Package: libglib2.0-0
Version: 2.36.1-2
Severity: important
Dear Maintainer,
after upgrading glib to the unstable version, emacs does not start anymor
Hi again,
> after choosing the oxygen style for GTK2 applications, emacs no longer starts.
> The process hangs before opening the window.
>
> While debugging the issue, I read somewhere that GTK styles using C++
> sometimes
> cause mysterious issues caused e.g. by mismatching libstdc++ versions
Package: gtk2-engines-oxygen
Version: 1.2.4-1
Severity: important
Dear Maintainer,
after choosing the oxygen style for GTK2 applications, emacs no longer starts.
The process hangs before opening the window.
While debugging the issue, I read somewhere that GTK styles using C++ sometimes
cause mys
5 matches
Mail list logo
