GNOME Bugzilla – Bug 364396
crash in Trash: Changing GTK themes from...
Last modified: 2013-10-09 07:08:47 UTC
What were you doing when the application crashed? Changing GTK themes from QT to Raleigh. I am doing this to replicate a previous bug with libgtk and libglib debug packages installed. Hope it is useful :-) Let me know what else I can do to help. Regards Anthony. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 92516352 vsize: 0 resident: 92516352 share: 0 rss: 10338304 rss_rlim: 0 CPU usage: start_time: 1161605146 rtime: 0 utime: 37 stime: 0 cutime:36 cstime: 0 timeout: 1 it_real_value: 0 frequency: 5 Backtrace was generated from '/usr/libexec/trashapplet' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1224640848 (LWP 27567)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 77837
Thread 1 (Thread -1224640848 (LWP 27567))
*** Bug 364398 has been marked as a duplicate of this bug. ***
*** Bug 366152 has been marked as a duplicate of this bug. ***
*** Bug 366151 has been marked as a duplicate of this bug. ***
*** Bug 366150 has been marked as a duplicate of this bug. ***
It should be noted that bug 366150, just dup'ed to this by Karsten in comment #4, has a strack trace with debugging symbols.
Ignore my last comment... too many open tabs, I guess :-( Reporter, could you install debug symbols for the gtk-qt-engine package and try to get a new stack with that? If you are reporting using bug-buddy, it'd be helpful if you mentioned this bug in the new report. Thanks for all your help!
*** Bug 372960 has been marked as a duplicate of this bug. ***
so, gtk+ issue? i have marked duplicates from nautilus and deskbar-applet with the same trace. also see the trace at bug 355074 comment 2.
*** Bug 376646 has been marked as a duplicate of this bug. ***
Ubuntu bug about that: https://launchpad.net/products/gtk/+bug/71345
*** Bug 389083 has been marked as a duplicate of this bug. ***
I reported 389083. Gnome isn't usable from K/Ubuntu at present because of this bug after we login. Is a fix in the works for this critical crash?
We'll have a hard time fixing it here if the issue is in the gtk-qt theme engine.
*** Bug 433379 has been marked as a duplicate of this bug. ***
*** Bug 505245 has been marked as a duplicate of this bug. ***
*** Bug 505497 has been marked as a duplicate of this bug. ***
*** Bug 505244 has been marked as a duplicate of this bug. ***
*** Bug 505246 has been marked as a duplicate of this bug. ***
*** Bug 505248 has been marked as a duplicate of this bug. ***
*** Bug 505247 has been marked as a duplicate of this bug. ***
*** Bug 508993 has been marked as a duplicate of this bug. ***
Lots of the duplicates are not using the gtk-qt theme, so I don't think we can mark it as NOTGNOME.
*** Bug 514152 has been marked as a duplicate of this bug. ***
*** Bug 518090 has been marked as a duplicate of this bug. ***
*** Bug 508885 has been marked as a duplicate of this bug. ***
*** Bug 560168 has been marked as a duplicate of this bug. ***
*** Bug 560169 has been marked as a duplicate of this bug. ***
*** Bug 560178 has been marked as a duplicate of this bug. ***
*** Bug 560170 has been marked as a duplicate of this bug. ***
*** Bug 560171 has been marked as a duplicate of this bug. ***
*** Bug 560172 has been marked as a duplicate of this bug. ***
*** Bug 560173 has been marked as a duplicate of this bug. ***
*** Bug 560174 has been marked as a duplicate of this bug. ***
*** Bug 560175 has been marked as a duplicate of this bug. ***
Well, there is a problem with event filtering in the QT engine, so my guess is that this is the cause. If one looks at the sourcecode of the QT engine, it adds an event filter in createQApp in qt_qt_wrapper.cpp. However this event filter is NEVER removed, even when the engine is unloaded. Which means that GTK+ will jump into random memory. So my guess is NOTGNOME. If there are any bugs that are not related to the QT engine, then maybe there is more than one issue.
*** Bug 555063 has been marked as a duplicate of this bug. ***
Going by the huge amount of duplicate bug reports for the first 2 years and now nothing for the past 5 years I'm going to mark this bug as obsolete. Feel free to reopen if this is still an issue.