GNOME Bugzilla – Bug 420085
crash in System Log: desperatelly trying to m...
Last modified: 2007-03-19 12:09:41 UTC
Version: 2.16.1 What were you doing when the application crashed? desperatelly trying to make another PC bootable from cdrom in order to reinstall its OS and theoretically to install Ubuntu on in. So OK :) I was doing nothing. Like really NOTHING just looking at the https://help.ubuntu.com/community/SmartBootManagerHowto without touching anything when it crashed. (Win rulez) Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 46718976 vsize: 0 resident: 46718976 share: 0 rss: 22179840 rss_rlim: 0 CPU usage: start_time: 1174299386 rtime: 0 utime: 6869 stime: 0 cutime:6469 cstime: 0 timeout: 400 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-log' (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 -1224914752 (LWP 5968)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 120008
Thread 1 (Thread -1224914752 (LWP 5968))
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 355887 ***