GNOME Bugzilla – Bug 356181
crash before gdk_x11_drawable_get_xdisplay
Last modified: 2008-10-11 21:31:39 UTC
Version: 2.16.0 What were you doing when the application crashed? Distribution: Mandriva Linux release 2007.0 (Cooker) for i586 Gnome Release: 2.16.0 2006-09-04 (Mandriva) BugBuddy Version: 2.16.0 Memory status: size: 51007488 vsize: 0 resident: 51007488 share: 0 rss: 15331328 rss_rlim: 0 CPU usage: start_time: 1158354637 rtime: 0 utime: 177 stime: 0 cutime:161 cstime: 0 timeout: 16 it_real_value: 0 frequency: 22 Backtrace was generated from '/usr/bin/bug-buddy' (no debugging symbols found) Using host libthread_db library "/lib/i686/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231255872 (LWP 10447)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 72434
Thread 1 (Thread -1231255872 (LWP 10447))
*** Bug 356182 has been marked as a duplicate of this bug. ***
*** Bug 356183 has been marked as a duplicate of this bug. ***
*** Bug 356189 has been marked as a duplicate of this bug. ***
*** Bug 356190 has been marked as a duplicate of this bug. ***
*** Bug 356191 has been marked as a duplicate of this bug. ***
*** Bug 356249 has been marked as a duplicate of this bug. ***
*** Bug 356617 has been marked as a duplicate of this bug. ***
*** Bug 356787 has been marked as a duplicate of this bug. ***
Note: *ALL* duplicates have been filed by the same submitter! This actually is one bug with no duplicates.
*** Bug 357654 has been marked as a duplicate of this bug. ***
last duplicate isn't from the same submitter. confirming bug report.
*** Bug 365777 has been marked as a duplicate of this bug. ***
i don't know if bug 346179 is the same bug - is this a general gtk+ issue or really a bug-buddy thingy? :-/
Looks like a problem in GTK+/GDK to me. Moving to GTK+.
*** Bug 388381 has been marked as a duplicate of this bug. ***
*** Bug 388383 has been marked as a duplicate of this bug. ***
*** Bug 391380 has been marked as a duplicate of this bug. ***
*** Bug 391381 has been marked as a duplicate of this bug. ***
*** Bug 395404 has been marked as a duplicate of this bug. ***
*** Bug 381103 has been marked as a duplicate of this bug. ***
*** Bug 394839 has been marked as a duplicate of this bug. ***
*** Bug 407174 has been marked as a duplicate of this bug. ***
*** Bug 409265 has been marked as a duplicate of this bug. ***
*** Bug 412182 has been marked as a duplicate of this bug. ***
*** Bug 415912 has been marked as a duplicate of this bug. ***
*** Bug 417175 has been marked as a duplicate of this bug. ***
*** Bug 422859 has been marked as a duplicate of this bug. ***
*** Bug 409670 has been marked as a duplicate of this bug. ***
*** Bug 424390 has been marked as a duplicate of this bug. ***
*** Bug 424391 has been marked as a duplicate of this bug. ***
*** Bug 422858 has been marked as a duplicate of this bug. ***
*** Bug 425737 has been marked as a duplicate of this bug. ***
*** Bug 426245 has been marked as a duplicate of this bug. ***
*** Bug 430662 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 445370 has been marked as a duplicate of this bug. ***
*** Bug 437815 has been marked as a duplicate of this bug. ***
*** Bug 450827 has been marked as a duplicate of this bug. ***
*** Bug 457442 has been marked as a duplicate of this bug. ***
*** Bug 342671 has been marked as a duplicate of this bug. ***
*** Bug 459814 has been marked as a duplicate of this bug. ***
*** Bug 458883 has been marked as a duplicate of this bug. ***
*** Bug 455502 has been marked as a duplicate of this bug. ***
*** Bug 457550 has been marked as a duplicate of this bug. ***
*** Bug 458884 has been marked as a duplicate of this bug. ***
*** Bug 468109 has been marked as a duplicate of this bug. ***
*** Bug 472103 has been marked as a duplicate of this bug. ***
*** Bug 472107 has been marked as a duplicate of this bug. ***
I can confirm that they are all from the same submitter, yours truly. The problem was this (for MDV 2007.0): I had enabled the 3ddesktop to test out a new monitor. From the MCC, I had copped the Metacity bug described here: http://forum.mandriva.com/viewtopic.php?t=69876&sid=ecadff78aefc5d1a9613c53392a12eca Then, it went to log me out with no option to not log out, wouldn't save some changes, and when I logged back in several times over, it would pop up seemingly hundreds of Bug Buddy windows. This, right after I logged in. I tried to fix to no avail; the desktop would continue to segfault on me, I'd reboot, and log back in to the exact same thing. I tried to copy my data over to my backup drive, but it segfaulted in the process and dumped my whole Documents folder (of which I had literally years of info in, among work documents, and personal ones). At this point, I decided to reformat and reinstall (and pour water over my processor while i was at it because i was so disgusted at the whole thing). I had run into this before; however, had always been able to reset my desktop to some avail. This time, nothing worked to get it going again. I was in Gnome; it's my default desktop. Thank you.
Sorry, no, correction: This is not the same bug or backtrace that I got. Mine was considered a duplicate of this one, of which the backtrace looks very different. Thank you.
*** Bug 477948 has been marked as a duplicate of this bug. ***
*** Bug 470587 has been marked as a duplicate of this bug. ***
*** Bug 481541 has been marked as a duplicate of this bug. ***
*** Bug 496821 has been marked as a duplicate of this bug. ***
No new duplicates for a long time. Closing as INCOMPLETE.