output in terminal # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fb443d3016c, pid=14126, tid=140413647234816 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [liboxygen-gtk.so+0x7416c] Oxygen::MenuStateData::menuItemIsActive(_GtkWidget*) const+0x1c # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /media/oldhome/swex/bin/pydev/eclipse4.3/hs_err_pid14126.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Reproducible: Always Steps to Reproduce: 1.try to navigate in eclipse menu Actual Results: crush Expected Results: smooth work :)
*** Bug 324440 has been marked as a duplicate of this bug. ***
will need version of - eclipse - gtk+-2.0 - oxygen-gtk2 Thanks !
eclipse 4.3, 4.2 (both versions I have crushing) gtk 2.24.20-1ubuntu1 oxygen-gtk-1.3.4-0ubuntu1
here: eclipse 4.2.1 gtk 2.24.17 oxygen-gtk-1.4 Can't reproduce. However, eclipse crash on startup as soon as I set "appears-as-list" to 1 in options. Ruslan ? Can you reproduce any of the above ? I'll investigate some more (will update gtk, and downgrade oxygen-gtk)
upgrading gtk, downgrading oxygen-gtk did not help. I could not reproduce.
in the meanwhile you can probably prevent the crash by - opening oxygen-settings in terminal - select the "animations" tab - disable (uncheck) the "menu highlight" animation Tell me if it helps.
Created attachment 82297 [details] error log for zend studio 10.1 crash (eclipse 3.8) Using Kubunty 13.10 beta 1 (up to date) Zend Studio 10.1 crashes when I go to set up an SSH connection for remote systems. The Eclipse version is 3.8 which ZS is built on top of. I do not have this problem with Kubuntu 13.04 and ZS 10.1 though. I disabled animations as suggested here but ZS still crashes. Here is an excerpt of the error log (somewhat different than before) # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f651fab38c8, pid=3046, tid=140072619947776 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x198c8] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
@Dave Report looks unrelated to the other (problem with gobject, from glib): [libgobject-2.0.so.0+0x198c8] g_object_get_qdata+0x18 It is likely a different bug/crash, and likely unrelated to oxygen also. Can you check whether or not you still have the crash when using a different widget style ? Hugo
*** Bug 325072 has been marked as a duplicate of this bug. ***
@Hugo - Thanks for the quick response! Sorry for my slow one. I also tried the Eclipse package installed from Muon and it crashes right after setting the default workspace. This was with the Oxygen menu highlighting enabled and disabled. # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007faa007d28c8, pid=2203, tid=140368452265728 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x198c8] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # When I changed to Plastique I was able to load Eclipse without crashing. Zend Studio 10.1 is also working. Before I was unable to add (caused crash) or edit remote systems and connecting to them did not appear to work. (no remote files were displayed even though it said I was connected) Other than installing Skype from the .deb provided on thier site and installing Zend Studio my Kubuntu install is stock 13.10 beta 1 (with all updates as of this posting) I prefer the Oxygen look for sure. Hopefully this can be resolved before the final release date. :)
@Hugo Versions installed: dave@DarkMetal:~$ sudo apt-show-versions -r gtk|eclipse|oxygen No command 'oxygen' found, did you mean: Command 'doxygen' from package 'doxygen' (main) oxygen: command not found dave@DarkMetal:~$ sudo apt-show-versions -r gtk|eclipse|oxygen No command 'oxygen' found, did you mean: Command 'doxygen' from package 'doxygen' (main) oxygen: command not found dave@DarkMetal:~$ sudo apt-show-versions -r 'gtk|eclipse|oxygen' eclipse-jdt:all/saucy 3.8.1-4 uptodate eclipse-pde:amd64/saucy 3.8.1-4 uptodate eclipse-platform:amd64/saucy 3.8.1-4 uptodate eclipse-platform-data:all/saucy 3.8.1-4 uptodate eclipse-rcp:amd64/saucy 3.8.1-4 uptodate eclipse-rse:all/saucy 3.4.2-1 uptodate gtk2-engines-oxygen:amd64/saucy 1.3.4-0ubuntu1 uptodate gtk3-engines-oxygen:amd64/saucy 1.2.0-0ubuntu1 uptodate kde-config-gtk-style:amd64/saucy 3:2.2.1-1fakesync1 uptodate kde-style-oxygen:amd64/saucy 4:4.11.1-0ubuntu3 uptodate libdbusmenu-gtk4:amd64/saucy 12.10.3+13.10.20130913-0ubuntu1 uptodate libgtk-3-0:amd64/saucy 3.8.4-0ubuntu1 uptodate libgtk-3-bin:amd64/saucy 3.8.4-0ubuntu1 uptodate libgtk-3-common:all/saucy 3.8.4-0ubuntu1 uptodate libgtk2.0-0:amd64/saucy 2.24.20-1ubuntu1 uptodate libgtk2.0-bin:amd64/saucy 2.24.20-1ubuntu1 uptodate libgtk2.0-common:all/saucy 2.24.20-1ubuntu1 uptodate libreoffice-style-oxygen:all/saucy 1:4.1.1-0ubuntu1 uptodate libswt-cairo-gtk-3-jni:amd64/saucy 3.8.2-3 uptodate libswt-glx-gtk-3-jni:amd64/saucy 3.8.2-3 uptodate libswt-gnome-gtk-3-jni:amd64/saucy 3.8.2-3 uptodate libswt-gtk-3-java:amd64/saucy 3.8.2-3 uptodate libswt-gtk-3-jni:amd64/saucy 3.8.2-3 uptodate libswt-webkit-gtk-3-jni:amd64/saucy 3.8.2-3 uptodate libwxgtk2.8-0:amd64/saucy 2.8.12.1-14ubuntu1 uptodate oxygen-cursor-theme:all/saucy 0.0.2012-06-kde4.8-2.1ubuntu1 uptodate oxygen-icon-theme:all/saucy 4:4.11.1-0ubuntu1 uptodate python-gtk2:amd64/saucy 2.24.0-3ubuntu1 uptodate ttf-oxygen-font-family:amd64/saucy 0.3~git20130121-0ubuntu1 uptodate I hope that helps some. :)
(In reply to comment #10) > @Hugo - Thanks for the quick response! Sorry for my slow one. > > I also tried the Eclipse package installed from Muon and it crashes right > after setting the default workspace. This was with the Oxygen menu > highlighting enabled and disabled. > > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007faa007d28c8, pid=2203, tid=140368452265728 > # > # JRE version: 7.0_25-b30 > # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 > compressed oops) > # Problematic frame: > # C [libgobject-2.0.so.0+0x198c8] g_object_get_qdata+0x18 > # > # Failed to write core dump. Core dumps have been disabled. To enable core > dumping, try "ulimit -c unlimited" before starting Java again > # > # If you would like to submit a bug report, please include > # instructions on how to reproduce the bug and visit: > # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > > When I changed to Plastique I was able to load Eclipse without crashing. > Zend Studio 10.1 is also working. Before I was unable to add (caused crash) > or edit remote systems and connecting to them did not appear to work. (no > remote files were displayed even though it said I was connected) > Plastique ? You mean the Qt widget style ? (I am not aware of a Gtk Widget style called plastique). Does that mean that the gtk widget style you are using for gtk application is actually gtk-qt ? (which somehow wraps Qt widget style into gtk, and is bound to fail with the fancy Qt oxygen widget theme) ? If yes you should definitely try oxygen-gtk instead. In any case: your crash is different from the others (the "problematic frame" is different). So this is unrelated. Please - try the suggestion above (use oxygen-gtk) - see if your applications are still crashing - see if the backtrace (the problematic frame) is the same "gobject" or like the one from Alexey (Oxygen::MenuStateData::menuItemIsActive) - if yes, try again with disabling animations.
> Plastique ? > You mean the Qt widget style ? (I am not aware of a Gtk Widget style called > plastique). > Does that mean that the gtk widget style you are using for gtk application > is actually gtk-qt ? > (which somehow wraps Qt widget style into gtk, and is bound to fail with the > fancy Qt oxygen widget theme) ? > If yes you should definitely try oxygen-gtk instead. > In any case: your crash is different from the others (the "problematic > frame" is different). So this is unrelated. > Please > - try the suggestion above (use oxygen-gtk) > - see if your applications are still crashing > - see if the backtrace (the problematic frame) is the same "gobject" or like > the one from Alexey (Oxygen::MenuStateData::menuItemIsActive) > - if yes, try again with disabling animations. From the application menu > Computer > System Settings > Application Appearance > Style > Widget Style > (CDE | Cleanlooks | GTK+ Style | MS Windows 9x | Motif | Oxygen | Plastique) On Kubuntu 13.04 I use Oxygen without issue. On 13.10 it crashes Eclipse. (with and without animations disabled) From the application menu > Computer > System Settings > Application Appearance > GTK > Select a GTK2 Theme > (oxygen-gtk | Raleigh) From the application menu > Computer > System Settings > Application Appearance > GTK > Select a GTK3 Theme > (Default | Emacs | oxygen-gtk) Selecting Raleigh for GTK2 theme and Emacs for GTK3 theme with Style > Oxygen > Animations (all disabled) prevents Eclipse from crashing. Selecting Raleigh for GTK2 theme and Emacs for GTK3 theme with Style > Oxygen > Animations (all enabled) causes Eclipse to crash: # Problematic frame: # C [libgobject-2.0.so.0+0x198c8] g_object_get_qdata+0x18 Selecting Raleigh for GTK2 theme and Default for GTK3 theme with Style > Oxygen > Animations (all enabled) prevents Eclipse from crashing.
The latest round of updates has fixed this for me. Both eclipse and zend studio are working as expected. Thanks!
So, what includes fix of crashes?
I'm pretty sure there was no update on the oxygen-gtk side. so either ecclipse, or gtk itself, or anything. @Dave: you have animations enabled ? or disabled ? (in kde this is changed via system-settings or directly with "oxygen-settings")
PS: if confirmed by Alexei, I'll close the bug as upstream.
@Hugo After updating the crash is back. :( This one is a bit different in how it happens. If I open an already existing connection for which eclipse prompts me for the secure storage password and then close out I can then create a new connection without crashing. But if I right click on the remote systems panel to create a new connection straight off, and enter my secure storage password, and then try and create the new connection eclipse crashes when I click finish. # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007ff35a0e7528, pid=2637, tid=140683485423360 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18 #
I get the same error on a patched Kubuntu 13.10 with Zend Eclipse for PHP Developers. Disabling menu animations as suggested solves the problem. However, everything looks very ugly after that, so that can only be a temporary solution. # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f56a8f70528, pid=28259, tid=140010407618304 # # JRE version: 7.0_25-b15 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug.
@Bodo please post screenshot of what's look ugly
A reliable way to generate the crash on my System is to start a file-search in eclipse. This started after the upgrading to Kubuntu 13.10 yesterday. The error message is: > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007fc4e1e87528, pid=5877, tid=140484018239232 > # > # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18) > # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18 > # > # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again > # > # An error report file with more information is saved as: > # /tmp/hs_err_pid5877.log > Compiled method (nm) 20797 1400 n org.eclipse.swt.internal.gtk.OS::_g_object_get_qdata (native) > total in heap [0x00007fc4f1254690,0x00007fc4f1254a10] = 896 > relocation [0x00007fc4f12547b0,0x00007fc4f1254810] = 96 > main code [0x00007fc4f1254820,0x00007fc4f1254a10] = 496 > # > # If you would like to submit a bug report, please visit: > # http://bugreport.sun.com/bugreport/crash.jsp > #
I forgot to mention, that none of the workarounds mentioned here improved something.
(In reply to comment #20) > @Bodo > please post screenshot of what's look ugly It's every UI component that now looks kind of nineties. Especially buttons, menus and scrollbars. Yes, It's working - but the beauty of KDE has gone. Odd: most of KDE software still looks pretty (i.e kcalc, System Setting dialog, ...). http://picload.org/image/oclradi/gimp_no_menu_ani.png http://picload.org/image/oclraow/firefox_no_menu_.png http://picload.org/image/oclralr/kcalc_no_menu_an.png
@Bodo: from the screenshots, it seems you are not using oxygen-gtk as a gtk widget theme any more. (falling back to Raleigh). I don't think this is related to your disabling the menu animations ... Does it "come back" when you re-enable the animation ?
@Wolfram see comment to Dave (#7 and #8) This is a gobject crash. Unrelated with the original crash report, and likely unrelated to oxygen-gtk. Which also explains why the workaround don't work.
Hugo, you are right, this problem affects linux in all. I swiched to eclipse-kepler, where they fixed it.
@Hugo: Yes, you are right. GTK2-Design is set to Raleigh. Switching to oxygen brings back the beauty but has the side effect that eclipse crashes very often (i.e. when performing a file search etc)
Hi, I got the same problem on kubuntu 13.10 (everything up to date) with gtk2-engines-oxygen version 1.3.4-ubuntu. Trying with upgrading this package to 1.4.0 by getting it here http://packages.debian.org/unstable/gnome/gtk2-engines-oxygen did not solved the problem. Here are the console logs I get when Eclipse crashes (I used android ADT to test, and to make it crash go to AVD manager, edit a device and click OK in edit window) : With gtk2 oxygen version 1.3.4 : # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fa6e29d9528, pid=3137, tid=140355564074752 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/vincent/hs_err_pid3137.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # And in version 1.4.0 : # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f6d3a5d5528, pid=3612, tid=140107928499968 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/vincent/Téléchargements/hs_err_pid3612.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Not seeming to change something... Changing the GTK theme works properly, but eclipse and other gtk apps are awful
Hallo me to. With 13.04 it works fine. Changing the GTK theme works , but gtk apps looks like Apps from1980 lg Chris
*** This bug has been confirmed by popular vote. ***
Problem with latest ADT from Google (Eclipse based). Works great before the upgrade to 13.10. Try switching for Oracle's JDK, but same thing. Switching GTK2's theme to RALEIG solve the problem. Cannot imagine an OS with such awfull design in 21st century ;-)
Yup, System Settings > Application Appearance > GTK > GTK2 Theme: Raleigh works excellent as workaround. Eclipse looks awful? Firefox too with the Raleigh theme :(
Git commit c52b7367d99444ace2743c87364591cb0dd164a7 by Hugo Pereira Da Costa. Committed on 03/01/2014 at 17:47. Pushed by hpereiradacosta into branch '1.4'. properly reset _previous and _current widget, if matching, in case of child destruction, for ToolbarStateData, MenuStateData, MenuBarStateData Related: bug 329112, bug 328495, bug 325196 M +91 -0 src/animations/oxygenmenubarstatedata.cpp M +15 -0 src/animations/oxygenmenubarstatedata.h M +90 -0 src/animations/oxygenmenustatedata.cpp M +15 -0 src/animations/oxygenmenustatedata.h M +13 -0 src/animations/oxygentoolbarstatedata.cpp http://commits.kde.org/oxygen-gtk/c52b7367d99444ace2743c87364591cb0dd164a7
Can anyone experiencing the crash with "Oxygen::MenuStateData::menuItemIsActive(_GtkWidget*) " try with latest oxygen-gtk branch 1.4, retrieved from git and compiled from source ? I "think" the change fixes the bug (the code change in MenuStateData makes sense in terms on how the old code could indeed crash and the new one should not)
Git commit a9fd101716d92623e410099d9b13f31cb3236fe8 by Hugo Pereira Da Costa. Committed on 03/01/2014 at 17:47. Pushed by hpereiradacosta into branch 'gtk3'. properly reset _previous and _current widget, if matching, in case of child destruction, for ToolbarStateData, MenuStateData, MenuBarStateData Related: bug 329112, bug 328495, bug 325196 M +91 -0 src/animations/oxygenmenubarstatedata.cpp M +15 -0 src/animations/oxygenmenubarstatedata.h M +90 -0 src/animations/oxygenmenustatedata.cpp M +15 -0 src/animations/oxygenmenustatedata.h M +13 -0 src/animations/oxygentoolbarstatedata.cpp http://commits.kde.org/oxygen-gtk/a9fd101716d92623e410099d9b13f31cb3236fe8
Git commit bd052fe914c6cf9da70dd4ab931a4b563cb6e742 by Hugo Pereira Da Costa. Committed on 03/01/2014 at 17:47. Pushed by hpereiradacosta into branch 'gtk3-1.2'. properly reset _previous and _current widget, if matching, in case of child destruction, for ToolbarStateData, MenuStateData, MenuBarStateData Related: bug 329112, bug 328495, bug 325196 M +91 -0 src/animations/oxygenmenubarstatedata.cpp M +15 -0 src/animations/oxygenmenubarstatedata.h M +90 -0 src/animations/oxygenmenustatedata.cpp M +15 -0 src/animations/oxygenmenustatedata.h M +13 -0 src/animations/oxygentoolbarstatedata.cpp http://commits.kde.org/oxygen-gtk/bd052fe914c6cf9da70dd4ab931a4b563cb6e742
It also happen With ZendStudio 10.5 / ApacheDirectoryStudio and other eclipse based product. Will try the patches
(Feel free to delete this if not considered constructive) The above patches worked perfectly for me, it just took a while to locate exactly where I needed to install the files after compilation. Thank you Hugo Pereira Da Costa!
@Tom Thanks for the feadback. Closing then.
Ok update: It fixed it when adding remote systems in Zend Studio but there's an issue in another part. Opening and closing the Find dialog multiple times causes a crash. This also happens in Eclipse. In Eclipse it seems to happen every single time "Close" is pressed on the find dialog. In Zend studio it happens (roughly) every other time.
@Tom That's probably another issue. Will try to reproduce. If unable (will tell you), I'd like a stack trace/core dump. As usual.
Created attachment 84560 [details] Zend Studio JRM Crash log
I've attached the log file which causes the crash. However, like the previous issue it can be worked around by changing the GTK2 theme to something other than Oxygen-GTK.
yeah well, this is definitly "the other bug" that got reported here. crashing in "g_object_get_qdata" that's the kind of mess we end up with when multiple crashes are reported in the same bug report. please open a new one (with the same attachement, and a correct description of the crash). This bug is about "Oxygen::MenuStateData::menuItemIsActive", as reported in first comment, and got fixed. the rest is just hijack
PS 1: I have no clue (yet) how to debug and fix this one PS 2: this is likely a duplicate of bug 329445
Ok will do. Sorry it's difficult as a non-developer to distinguish between the two when the problem is similar and the workaround is the same.
See comments https://bugzilla.redhat.com/show_bug.cgi?id=1053565#c4 https://bugzilla.redhat.com/show_bug.cgi?id=1053565#c5 > oxygen-gtk2-1.4.2-1.fc20 works *much* better but sadly not predictable clean > enough, however, this update should be pushed because it makes things really > better as before > at night i tested all the cases where before in eclipse (Zend Studio 10.5.1 to be > precise) and it looked perfect - where i still can repdrocude *unpredictable* a > force close if by close the search dialog (CTRL+F), not always, not as i gave karma > but that is still critical and may lead to lose changes / work > in the cases i can reproduce the "force close" it looks like the same issue as before ([libgobject-2.0.so.0+0x19b48) [harry@rh:~]$ ZendStudio # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007ffa3e745b48, pid=23538, tid=140713467508480 # # JRE version: OpenJDK Runtime Environment (7.0_51-b02) (build 1.7.0_51-mockbuild_2014_01_17_13_38-b00) # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgobject-2.0.so.0+0x19b48] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /tmp/jvm-23538/hs_error.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # http://icedtea.classpath.org/bugzilla # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug.
@nucleo not the right bug report (see crash information in first comment, which is fixed). Right bug report is: https://bugs.kde.org/show_bug.cgi?id=329814 All comments posted here will be ignored, as the bug is marked as fixed (it is)
Note: as commented in the other report, the crash also happens with qtcurve and might actually be upstream (gtk or swt)
Ubuntu/Kubuntu Launchpad bug reports: 1. https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181 2. https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1241101 3. https://bugs.launchpad.net/ubuntu/+source/java-common/+bug/1205452
I see the comments that the bug is fixed, but I get the same crash in KDE Mint 16. Switching to Raleigh/Emacs theme "helps".
Which should be the resolution for this bug? It's not clear from this thread. Anyway I have this tedious bug too, I'm using 64bit kubuntu 13.10 and last release of Eclipse (Kepler 4.3.1)
@Raffaelle Depends on which bug you are talking about (more precisely what is in the stack trace). If you have something like: # Problematic frame: # C [liboxygen-gtk.so+0x7416c] Oxygen::MenuStateData::menuItemIsActive(_GtkWidget*) const+0x1c (see comment #1) This is the original bug, and should be fixed by now. If you have something like: # Problematic frame: # C [libgobject-2.0.so.0+0x198c8] g_object_get_qdata+0x18 This is a different bug, not addressed here, and which might not even be oxygen-gtk specific.