Rolling back to the version of Unity from Raring updates (7.0.0daily13.06.19~13.04-0ubuntu1) I cannot replicate this issue, whereas with 7.1.2+13.10.20131014.1-0ubuntu1 I am able to produce a crash. If someone could verify/disprove a connection between Unity and this issue that would be very helpful. Hesitant to throw Unity up as a potential package at fault until we are able to narrow down what is actually going on.
I do agree with Tom that Java-Common be removed as a potential culprit, as it seems to span several Java versions and affects both OpenJDK and Oracle's JDK, but for the same reasons, I'd rather hang on there for a bit. Gtk seems to be part of the issue, but may (if Unity doesn't end as a dead end) tie into Unity at some point. Regarding shared libs between QtCurve and gtk2-engines-oxygen, there isn't a lot that stands out. There is of course libc6, qt4-x11, and kde4libs. It's entirely possible that there was a change in one of those libraries that is causing this behavior. For the moment if you plan to test Unity 7.0.0 use the .deb file for your architecture. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/java-common/+bug/1241101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
