I've also tested this using Juno (the version included in Zend Studio
10) and unfortunately share auspex's experience, it doesn't solve the
issue for me.
I also tried explicitly launching the application with an affinity:
taskset 0x0001 zend-studio
with the same reslult.
--
You received
It's probably worth mentioning that with the latest Eclipse (Kepler)
this bug does not occur. Perhaps looking at the differences between
what happens on close in the find dialog in Kepler and Juno will shed
some light on what is causing the crash.
--
You received this bug notification because
Unfortunately running Eclipse via sudo does not fix the issue for me and
I get the exact same crash:
Stack: [0x7f252c76,0x7f252c861000], sp=0x7f252c85d040, free
space=1012k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C
This may also be relevant: It doesn't seem to be an Ubuntu/Debian based
distro specific bug. I also have an Arch Linux installation and it
happens on that as well.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
I'm not sure this is helpful or not but:
I don't have Unity installed. I'm running Linux Mint which is built from
Ubuntu and I'm running KDE. Whether that rules out a unity bug or not I
don't know.
Setting UBUNTU_MENUPROXY has no effect at all.
Using
Has anyone managed to track the package which is the source of this bug?
Here's my understanding so far:
It's not an Eclipse bug as the same version of Eclipse running on Ubuntu
13.04 does not suffer the problem
It doesn't appear to stem directly from oxygen-gtk as the QtCurve theme
suffers
That's a different bug. I can confirm that does fix several issues with
oxygen-gtk but not the g_object_get_qdata crash.
See https://bugs.kde.org/show_bug.cgi?id=329814 for the
g_object_get_qdata crash.
** Bug watch added: KDE Bug Tracking System #329814
