GNOME Bugzilla – Bug 472107
crash in Bug Report Tool: Logging into my desktop ...
Last modified: 2007-09-05 21:42:18 UTC
Version: 2.16.0 What were you doing when the application crashed? Logging into my desktop on Gnome, after a reboot. Distribution: Mandriva Linux release 2007.0 (Official) for i586 Gnome Release: 2.16.2 2006-11-24 (Mandriva) BugBuddy Version: 2.16.0 Memory status: size: 80224256 vsize: 0 resident: 80224256 share: 0 rss: 13848576 rss_rlim: 0 CPU usage: start_time: 1188533746 rtime: 0 utime: 107 stime: 0 cutime:103 cstime: 0 timeout: 4 it_real_value: 0 frequency: 11 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. [Thread debugging using libthread_db enabled] [New Thread -1231067456 (LWP 4784)] 0xbfffe410 in __kernel_vsyscall ()
+ Trace 159290
Thread 1 (Thread -1231067456 (LWP 4784))
As another comment, I had enabled 3ddesktop from within Mandriva 2007.0. However, there was nothing in that, that should have allowed this to happen. I've lost all of my Documents in trying to start a new user; in the process, did a full backup of my data first. In doing the copying of my documents folder (in /home), it segfaulted and dumped them all. I've lost work, I've lost a lot that I'll grieve for, for a long time, both for business and personal documents. It all started with the Metacity bug here: https://bugs.launchpad.net/gnome-session/+bug/35316 Then, proceeded to completely lose contact with my desktop. .xsession-errors at the time grew bigger and bigger; screenshots and more can be seen http://forum.mandriva.com/viewtopic.php?p=364241#364241 (along with one of the .xsession-errors I was getting). If I could, I'd post it all here; however, I've lost it all to post.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 356181 ***