GNOME Bugzilla – Bug 352265
crash on Trash
Last modified: 2008-08-18 15:55:44 UTC
What were you doing when the application crashed? Changing themes Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.91 2006-08-08 (Ubuntu) BugBuddy Version: 2.15.90 Memory status: size: 75476992 vsize: 0 resident: 75476992 share: 0 rss: 9555968 rss_rlim: 0 CPU usage: start_time: 1156178248 rtime: 0 utime: 87 stime: 0 cutime:84 cstime: 0 timeout: 3 it_real_value: 0 frequency: 13 Backtrace was generated from '/usr/libexec/trashapplet' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224231248 (LWP 28311)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 70768
Thread 1 (Thread -1224231248 (LWP 28311))
*** Bug 354821 has been marked as a duplicate of this bug. ***
*** Bug 354989 has been marked as a duplicate of this bug. ***
*** Bug 355854 has been marked as a duplicate of this bug. ***
Matching stacktraces from gnome-applets and deskbar-applet. Looks like bonobo or gdk. Moving over. Dudes, please feel free to move further if you see fit. :)
Note: bonobo/libbonobo version is 2.16.x. Unfortuately missing in the version field.
Everyone, thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Those who where switching themes: Which theme are you using? Before and after changing the theme?
*** Bug 356233 has been marked as a duplicate of this bug. ***
*** Bug 356232 has been marked as a duplicate of this bug. ***
Another two "switching theme" duplicates. Doesn't seem to be bonobo. Moving further to GTK+.
*** Bug 356851 has been marked as a duplicate of this bug. ***
*** Bug 357170 has been marked as a duplicate of this bug. ***
*** Bug 357284 has been marked as a duplicate of this bug. ***
*** Bug 357961 has been marked as a duplicate of this bug. ***
*** Bug 359331 has been marked as a duplicate of this bug. ***
*** Bug 360715 has been marked as a duplicate of this bug. ***
*** Bug 360818 has been marked as a duplicate of this bug. ***
Can anybody of the reporters here please help the developers to fix this bug by trying to reproduce this crash with debugging packages of at least gtk+ and bonobo installed? See http://live.gnome.org/GettingTraces/DistroSpecificInstructions for more information. Those who were switching themes: Which theme are you using? Before and after changing the theme? Thanks a lot in advance, your help is appreciated! Developers: also see traces at bug 358155 and bug 360867.
*** Bug 361019 has been marked as a duplicate of this bug. ***
*** Bug 361862 has been marked as a duplicate of this bug. ***
*** Bug 361864 has been marked as a duplicate of this bug. ***
*** Bug 361868 has been marked as a duplicate of this bug. ***
*** Bug 362453 has been marked as a duplicate of this bug. ***
*** Bug 362679 has been marked as a duplicate of this bug. ***
*** Bug 362780 has been marked as a duplicate of this bug. ***
Hi, the crash was changing between QT and Raleigh GTK themes in the gnome theme manager. I'll install the debugging stuff and try and get it to crash again. Regards Anthony.
anthony, thanks in advance for helping!
*** Bug 362985 has been marked as a duplicate of this bug. ***
*** Bug 362992 has been marked as a duplicate of this bug. ***
this is getting more and more urgent as this bites many users.
*** Bug 363273 has been marked as a duplicate of this bug. ***
*** Bug 363418 has been marked as a duplicate of this bug. ***
*** Bug 363512 has been marked as a duplicate of this bug. ***
>the crash was changing between QT and Raleigh GTK themes in the gnome theme >manager. One important part that is missing from the original bug report I made (363512), was that this occurred after I installed QT (Kubuntu-Desktop), played around with it for a couple of hours, then logged to GNOME and uninstalled. The theme looked like some cross breed of the GTK+ and QT elements of the default Ubuntu themes, and when I tried to resolve it by switching to a high-contrast theme, and back, it crashed applets in the panel.
*** Bug 363698 has been marked as a duplicate of this bug. ***
*** Bug 363932 has been marked as a duplicate of this bug. ***
*** Bug 363957 has been marked as a duplicate of this bug. ***
*** Bug 361612 has been marked as a duplicate of this bug. ***
*** Bug 364053 has been marked as a duplicate of this bug. ***
*** Bug 364075 has been marked as a duplicate of this bug. ***
*** Bug 364093 has been marked as a duplicate of this bug. ***
*** Bug 364119 has been marked as a duplicate of this bug. ***
*** Bug 364230 has been marked as a duplicate of this bug. ***
i was also testing out some themes when it crashed on me.
(In reply to comment #17) > Can anybody of the reporters here please help the developers to fix this bug by > trying to reproduce this crash with debugging packages of at least gtk+ and > bonobo > installed? See http://live.gnome.org/GettingTraces/DistroSpecificInstructions > for more information. > > Those who were switching themes: Which theme are you using? Before and after > changing the theme? > > Thanks a lot in advance, your help is appreciated! > > Developers: also see traces at bug 358155 and bug 360867. > Which packages would those be? gtk+-dbgsym and bonoboo-dbgsym do not exist.
hi jpbogan, right... ubuntu users please try to reproduce this crash with libgtk2.0-0-dbg and libglib2.0-0-dbg installed. thanks a lot in advance for your efforts!
Mass re-Cc'ing...
Since almost no one got this note by bugzilla mail, here goes again: (In reply to comment #45) > ubuntu users please try to reproduce this crash with libgtk2.0-0-dbg and > libglib2.0-0-dbg installed. thanks a lot in advance for your efforts!
*** Bug 364519 has been marked as a duplicate of this bug. ***
*** Bug 364522 has been marked as a duplicate of this bug. ***
*** Bug 364520 has been marked as a duplicate of this bug. ***
*** Bug 364596 has been marked as a duplicate of this bug. ***
*** Bug 364669 has been marked as a duplicate of this bug. ***
*** Bug 364748 has been marked as a duplicate of this bug. ***
*** Bug 364834 has been marked as a duplicate of this bug. ***
27 duplicates in the last 15 days - gnome 2.16.x blocker.
*** Bug 364910 has been marked as a duplicate of this bug. ***
*** Bug 365324 has been marked as a duplicate of this bug. ***
*** Bug 365532 has been marked as a duplicate of this bug. ***
*** Bug 365568 has been marked as a duplicate of this bug. ***
*** Bug 365648 has been marked as a duplicate of this bug. ***
*** Bug 365797 has been marked as a duplicate of this bug. ***
*** Bug 365875 has been marked as a duplicate of this bug. ***
*** Bug 365909 has been marked as a duplicate of this bug. ***
*** Bug 365922 has been marked as a duplicate of this bug. ***
Can anybody of the reporters here please help the developers to fix this bug by trying to reproduce this crash with debugging packages of at least gtk+ and glib installed? See http://live.gnome.org/GettingTraces/DistroSpecificInstructions for more information. Ubuntu users please try to reproduce this crash with libgtk2.0-0-dbg and libglib2.0-0-dbg installed. Thanks a lot in advance, your help is appreciated!
*** Bug 365948 has been marked as a duplicate of this bug. ***
*** Bug 366086 has been marked as a duplicate of this bug. ***
*** Bug 366100 has been marked as a duplicate of this bug. ***
*** Bug 366104 has been marked as a duplicate of this bug. ***
*** Bug 366158 has been marked as a duplicate of this bug. ***
*** Bug 366258 has been marked as a duplicate of this bug. ***
*** Bug 366263 has been marked as a duplicate of this bug. ***
*** Bug 366270 has been marked as a duplicate of this bug. ***
*** Bug 366257 has been marked as a duplicate of this bug. ***
*** Bug 366268 has been marked as a duplicate of this bug. ***
*** Bug 366291 has been marked as a duplicate of this bug. ***
*** Bug 366292 has been marked as a duplicate of this bug. ***
I'm ubuntu user's who often have this bug. (The first time when I was changing theme, but just the first time). I have installed kubuntu before (as comment 33). I have now install libgtk2.0-0-dbg and libglib2.0-0-dbg. 'Hope it 'll help.
*** Bug 366296 has been marked as a duplicate of this bug. ***
*** Bug 366124 has been marked as a duplicate of this bug. ***
*** Bug 366598 has been marked as a duplicate of this bug. ***
*** Bug 367082 has been marked as a duplicate of this bug. ***
*** Bug 367121 has been marked as a duplicate of this bug. ***
*** Bug 367186 has been marked as a duplicate of this bug. ***
*** Bug 367422 has been marked as a duplicate of this bug. ***
*** Bug 367487 has been marked as a duplicate of this bug. ***
*** Bug 367475 has been marked as a duplicate of this bug. ***
*** Bug 367478 has been marked as a duplicate of this bug. ***
*** Bug 367892 has been marked as a duplicate of this bug. ***
*** Bug 367891 has been marked as a duplicate of this bug. ***
*** Bug 368248 has been marked as a duplicate of this bug. ***
(In reply to comment #45) > hi jpbogan, right... > ubuntu users please try to reproduce this crash with libgtk2.0-0-dbg and > libglib2.0-0-dbg installed. thanks a lot in advance for your efforts! > My applications started crashing after I installed kubuntu-desktop on my fresh Ubuntu Edgy install and changed theme in Gnome. If I don't use the default Human theme, I get a lot of crashing messages when I login (though applications look a bit weird in the default theme too now). -------------------------------------------------------------- Memory status: size: 36261888 vsize: 0 resident: 36261888 share: 0 rss: 10805248 rss_rlim: 0 CPU usage: start_time: 1162324164 rtime: 0 utime: 56 stime: 0 cutime:56 cstime: 0 timeout: 0 it_real_value: 0 frequency: 8 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225410896 (LWP 7262)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 81132
Thread 1 (Thread -1225410896 (LWP 7262))
*** Bug 367865 has been marked as a duplicate of this bug. ***
*** Bug 368723 has been marked as a duplicate of this bug. ***
*** Bug 368771 has been marked as a duplicate of this bug. ***
*** Bug 368796 has been marked as a duplicate of this bug. ***
*** Bug 368980 has been marked as a duplicate of this bug. ***
*** Bug 368998 has been marked as a duplicate of this bug. ***
*** Bug 368997 has been marked as a duplicate of this bug. ***
*** Bug 368996 has been marked as a duplicate of this bug. ***
*** Bug 369082 has been marked as a duplicate of this bug. ***
*** Bug 369098 has been marked as a duplicate of this bug. ***
*** Bug 369270 has been marked as a duplicate of this bug. ***
*** Bug 369303 has been marked as a duplicate of this bug. ***
*** Bug 369622 has been marked as a duplicate of this bug. ***
*** Bug 369825 has been marked as a duplicate of this bug. ***
*** Bug 369932 has been marked as a duplicate of this bug. ***
*** Bug 370139 has been marked as a duplicate of this bug. ***
*** Bug 370155 has been marked as a duplicate of this bug. ***
*** Bug 370199 has been marked as a duplicate of this bug. ***
*** Bug 370222 has been marked as a duplicate of this bug. ***
*** Bug 370587 has been marked as a duplicate of this bug. ***
*** Bug 370586 has been marked as a duplicate of this bug. ***
*** Bug 370585 has been marked as a duplicate of this bug. ***
*** Bug 370796 has been marked as a duplicate of this bug. ***
*** Bug 370793 has been marked as a duplicate of this bug. ***
*** Bug 371045 has been marked as a duplicate of this bug. ***
*** Bug 371175 has been marked as a duplicate of this bug. ***
*** Bug 371203 has been marked as a duplicate of this bug. ***
*** Bug 371235 has been marked as a duplicate of this bug. ***
*** Bug 371173 has been marked as a duplicate of this bug. ***
As comment #92 tel me if it's not the god way to do. (for remember edgy+kubuntu+first bug when changing theme) gnome-netstatus-rapport-d-anomalies.txt: Memory status: size: 177176576 vsize: 0 resident: 177176576 share: 0 rss: 45187072 rss_rlim: 0 CPU usage: start_time: 1162582625 rtime: 0 utime: 59940 stime: 0 cutime:54383 cstime: 0 timeout: 5557 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/gnome-netstatus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225554256 (LWP 6050)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 84053
Thread 1 (Thread -1225554256 (LWP 6050))
#0 0
don't see any reason why this is still needinfo, comment #92 provides a nice stacktrace. manumuller, thanks a lot for your stacktrace! it seems that this is another crash, namely bug 352444. i have copied your stack trace to bug 352444. thanks! :-)
*** Bug 371556 has been marked as a duplicate of this bug. ***
The cause for my problem was the package gtk2-engines-gtk-qt. When I removed it, both GNOME and KDE sessions worked and if I reinstalled it, GNOME stopped working properly.
*** Bug 372346 has been marked as a duplicate of this bug. ***
*** Bug 372667 has been marked as a duplicate of this bug. ***
*** Bug 372724 has been marked as a duplicate of this bug. ***
*** Bug 372745 has been marked as a duplicate of this bug. ***
Closing NOTGNOME, according to comment 125
no new rejected reports for more than a month now (we reject reports from GNOME <=2.16). removing from the auto-reject list.
*** Bug 405679 has been marked as a duplicate of this bug. ***