GNOME Bugzilla – Bug 360297
crash in Time and Date: Attempting to open the T...
Last modified: 2007-02-11 22:42:04 UTC
Version: 2.15.5 What were you doing when the application crashed? Attempting to open the Time/Date control panel under the System menu. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 12681216 vsize: 0 resident: 66564096 share: 0 rss: 66564096 rss_rlim: 0 CPU usage: start_time: 12637 rtime: 0 utime: 1160180182 stime: 0 cutime:56 cstime: 0 timeout: 51 it_real_value: 0 frequency: 5 Backtrace was generated from '/usr/bin/time-admin' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 805564416 (LWP 15093)] (no debugging symbols found) 0x0eb44334 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 75006
Thread 1 (Thread 805564416 (LWP 15093))
Could you please add do this to get the backtrace with debugging information - In terminal type "sudo nano /etc/apt/sources.list" and add this line to it - deb http://people.ubuntu.com/~pitti/ddebs edgy main universe Now close nano by Ctrl+x and press y and then enter to save the file. Now at the terminal type - sudo apt-get update;sudo apt-get install gnome-system-tools-dbgsym This will install the debugging symbols for gnome-system-tools package. (Taken from http://live.gnome.org/GettingTraces/DistroSpecificInstructions ) Please try to reproduce the bug again and post the output of bug-buddy here. If you are unable to understand what I said, check http://live.gnome.org/GettingTraces and http://live.gnome.org/GettingTraces/DistroSpecificInstructions
*** Bug 368691 has been marked as a duplicate of this bug. ***
*** Bug 369386 has been marked as a duplicate of this bug. ***
confirming as per duplicate
*** Bug 370827 has been marked as a duplicate of this bug. ***
*** Bug 370895 has been marked as a duplicate of this bug. ***
This is a duplicate of Bug 366996.
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!
Sure, but it'll have to wait for the weekend - I don't have the debug packages installed....
*** Bug 378986 has been marked as a duplicate of this bug. ***
This is what I got after I installed the debug packages... ========================================================== Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 12705792 vsize: 0 resident: 59748352 share: 0 rss: 59748352 rss_rlim: 0 CPU usage: start_time: 54815 rtime: 0 utime: 1164468771 stime: 0 cutime:50 cstime: 0 timeout: 45 it_real_value: 0 frequency: 5 Backtrace was generated from '/usr/bin/time-admin' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 805544640 (LWP 6545)] 0x0eb43334 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 89285
Thread 1 (Thread 805544640 (LWP 6545))
*** Bug 384791 has been marked as a duplicate of this bug. ***
*** Bug 386671 has been marked as a duplicate of this bug. ***
*** Bug 388352 has been marked as a duplicate of this bug. ***
reopening as per comment 11, obviously
*** This bug has been marked as a duplicate of 363194 ***