it is most likely a _gtk_ bug. The reason it si visible in QtCurve and
oxygen-gtk is because they both use the "appears-as-list" option to display
combobox entries.
I'll test with clear-looks, setting this option to 1.
If confirmed, this has to be reported to gtk.
--
You received this bug noti
mcgyver
For oxygen, edit the normally already existing file
"/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc" and change
GtkComboBox::appears-as-list = 1
into
GtkComboBox::appears-as-list = 0
(I think you should be able to also achieve that by editing some
$HOME/.gtkrc, but which file exactly
Well:
- the fact that it happens in oxygen-gtk does not mean it is an oxygen-gtk bug:
just means the code path followed by oxygen-gtk triggers a bug that can be
anywhere in the chain
- nowhere in the core dump, as far as I can tell, is oxygen-gtk mentionned.
(sorry in advance if I missed it).
(n
I am closing this bug report
Last few posted crashes are unrelated to oxygen-gtk: they are libgobject.
I guess it is just someone pushing the "submit report" button.
So that it brings no new information
(besides java coredumps also have very little information to start with)
finally,
- none of the
Ok. Sorry if I misinterpretted the comment, and thanks for the upstream
bug report.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to gtk2-engines-oxygen in Ubuntu.
https://bugs.launchpad.net/bugs/1242801
Title:
meld assertion while selectin
Reporting the bug to gtk is as much your 'dutie' as ours.
I honestly do not remember whether we (or someone) has reported it to gtk.
Maybe you can find it out yourself ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
... also, a workaround is provided in comment #11
Really there is nothing more that we can do about it ...
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to gtk2-engines-oxygen in Ubuntu.
https://bugs.launchpad.net/bugs/1242801
Title:
meld a
ok. Crash seems to occur in our Qt configuration reading ... pretty low level.
Why would it crash for this application only and not all.
I'll investigate in more details as soon as I'm on the right machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
thanks. Closing then
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1142213
Title:
emacs23/24 and other GTK applications do not start when run in Kubuntu
13.04 with oxygen-gtk theme enabled
To man
is this bug still valid ?
It requires a recent enough version of glib, for g_spawn to be working properly.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to oxygen-gtk3 in Ubuntu.
https://bugs.launchpad.net/bugs/1142213
Title:
emacs23/24 an
@Lastique
As repeated several time above: indeed this is not a meld bug.
this is a GTK bug. We will _not_ workaround it in oxygen gtk.
It has to be fixed in gtk. Period. Arguing further is useless (as is posting
new, but identical, crash reports).
This bug is marked as "resolved, upstream" and t
Comming back to this bug, because I am not happy with the use of popen (which
is less portable than g_spawn):
testing with g_spawn again and glib-2.36.2, I do not get the issue anymore.
could someone double check ?
(would require some oxygen-gtk checked-out at, e.g.
a515ab451f54cbc930d0a09d25066
... digging:
https://bugzilla.gnome.org/show_bug.cgi?id=698081
seems, it was indeed a glib bug, that got fixed in glib.
I would be inclined to revert this change to popen, and close (again) this bug
as upstream.
Ruslan ? oppinion ?
--
You received this bug notification because you are a member
@Ruslan
problem with popen:
- it is defined on windows (with mingw at least) and works, but opens a
terminal to execute a command. (not so nice). And I'm not sure _popen would fix
this, would it ?
- on unix, it does not allow to easily redirect stderr, so you get an error
message (for every a
@Ruslan
So I'd suggest:
- keep current branches as they are (with popen).
- revert the change (sort of: I would like to keep the RunCommand method :))
for master (and gtk3 branch).
- if we want to be extra sure, add a minimal requirement on the glib version in
our (master) CMakefiles.
What do y
yeah well. More ifdefs ... not sure I want that. Especially if it is to
bypass a bug that is present in only one _minor_ release of glib.
The only advantage of keeping popen is if other (future) versions of
glib break, which the suggestion you propose would not prevent either
...
So in the end, g
PS: maybe we can revert the change in popen, in master only ...
(which will become our next feature release) ?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to oxygen-gtk3 in Ubuntu.
https://bugs.launchpad.net/bugs/1142213
Title:
emacs23/2
17 matches
Mail list logo
