Using oxgen-gtk2 causes eclipse/swt to crash. Using another the 'Radience' gtk2 theme works without any problem. Reproducible: Sometimes Steps to Reproduce: 1. Use an out-of-stock eclipse from the eclipse web site. 2. Start it. 3. Use 'Search -> File Search -> Cancel Button' Actual Results: - Eclipse regulary crashes (see included VM dumps). The bug is normally trigger by hitting a SWT Button (e.g. Search -> File Search -> Cancel Button). Expected Results: Expected behaviour: - oxygen-gtk2 theme should work without any issue against a 'offical' eclipse/swt.
Created attachment 83485 [details] java crash dump file (from oracle jdk 1.7.0_45)
Some more details could be found at https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1245468
Created attachment 83486 [details] java crash dump file (from oracle jdk 1.7.0_45)
Created attachment 83487 [details] java crash dump file (from oracle jdk 1.7.0_45)
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 oxygen-gtk devevloppers are able to reproduce the crash, - The original (oxygen-gtk related) has been said to be fixed after some update (and was likely upstream too). To the others, sorry for the frustration This should be reported to either - glib - your distribution
Dear Hugo, thank you for your prompt response. Notice that I've reported the bug to (a) the distribution and (b) eclipse. Just to be very explicit: The bug _only_ occurs with the oxygen-gtk2 theme. If I use the 'Radiance' theme, everything is all right. Please also notice that a java crash dump does contain many information that are of significance for C/C++ developers, including a (symbolic) trace to the root problem.
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). (nor are there any function calls mentioned, nor line numbers) I at least, do not know how to use this report to go and actually debug the code.