GNOME Bugzilla – Bug 363732
crash in Time and Date: Installing the NTP suppo...
Last modified: 2007-04-18 02:19:10 UTC
Version: 2.15.5 What were you doing when the application crashed? Installing the NTP support Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 128102400 vsize: 128102400 resident: 18313216 share: 10539008 rss: 18313216 rss_rlim: -1 CPU usage: start_time: 1161368834 rtime: 104 utime: 100 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 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 47862544784256 (LWP 12520)] (no debugging symbols found) 0x00002b87dc737eb5 in waitpid () from /lib/libpthread.so.0
+ Trace 77356
Thread 1 (Thread 47862544784256 (LWP 12520))
Hello! After a fresh install of edgy i was setting up the time and the time zone. I did a double click onthe clock and another one on "Synchronize with time servers", after that the application asked me if i did want to install it. Another click on yes and after a LOT of time (about ten minutes) it crashed. A second try worked, but only after a gdm restart. Feel free to ask me everything you need. Thanks Marco
*** Bug 366765 has been marked as a duplicate of this bug. ***
confirming as per duplicate.
the stacktrace of bug 358747 looks pretty much the same.
*** Bug 368552 has been marked as a duplicate of this bug. ***
*** Bug 370906 has been marked as a duplicate of this bug. ***
*** Bug 372252 has been marked as a duplicate of this bug. ***
Possibly the same as bug 358383?
Yes, i did the same things of bug 358383. Also the effect was the same, but mine installation was fresh. The first thing i did was setting the time.
*** This bug has been marked as a duplicate of 358383 ***
*** Bug 380628 has been marked as a duplicate of this bug. ***
*** Bug 391758 has been marked as a duplicate of this bug. ***
*** Bug 394918 has been marked as a duplicate of this bug. ***
*** Bug 401811 has been marked as a duplicate of this bug. ***
*** Bug 413390 has been marked as a duplicate of this bug. ***
*** Bug 425633 has been marked as a duplicate of this bug. ***
*** Bug 424353 has been marked as a duplicate of this bug. ***
*** Bug 430606 has been marked as a duplicate of this bug. ***