GNOME Bugzilla – Bug 355015
crash in Time and Date: installing ntp support f...
Last modified: 2007-09-13 09:52:01 UTC
Version: 2.15.4 What were you doing when the application crashed? installing ntp support from time and date Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 36737024 vsize: 0 resident: 36737024 share: 0 rss: 15659008 rss_rlim: 0 CPU usage: start_time: 1157751721 rtime: 0 utime: 437 stime: 0 cutime:417 cstime: 0 timeout: 20 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/time-admin' (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 -1225292112 (LWP 4857)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 71913
Thread 1 (Thread -1225292112 (LWP 4857))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
*** Bug 361794 has been marked as a duplicate of this bug. ***
*** Bug 366276 has been marked as a duplicate of this bug. ***
*** Bug 366706 has been marked as a duplicate of this bug. ***
*** Bug 366780 has been marked as a duplicate of this bug. ***
Of course it didn't crash when I tried it agin. Is there an easy way to remove the NTP support that is installed when first selecting "Keep clock synchronized..." checkbox?
*** Bug 368052 has been marked as a duplicate of this bug. ***
*** Bug 369291 has been marked as a duplicate of this bug. ***
*** Bug 369242 has been marked as a duplicate of this bug. ***
*** Bug 369667 has been marked as a duplicate of this bug. ***
*** Bug 369764 has been marked as a duplicate of this bug. ***
Hi, Further inspection of this problem after the heart attack it gave to my system indicates that it is a two-fold problem. Firstly, the NTP system is indeed working. The problem is that is seems to be unusually counter-intuitive (even by techie standards). The UI problem is that the user interface pops up a window asking if you want to install NTP support. The natural answer in my case was "sure, that's what I want to do", BUT it seems that there is a problem during the package install (I checked the logs and note that the package installer was indeed directed to /tmp/the_magic_package.tmp). After it fails it gives no warning (because the package intaller command is --not-interactive or some such). Secondly, being is bit of a dolt I kept clicking "install this package", which is what I think did it in. Conversely, after a few moments of calm. I went back to the machine. Did an "su" to root and did: apt-get update apt-get install ntp-server exit Then I went back to the "time and date" panel and voila: no more install ntp support message. I checked the sync time box, set the server I wanted to use, and all has been well since then. As you can see, it seems to be a bit of a minor bug, but exacerbated by a counter-intuitive lack of error message and package upgrade. (In reply to comment #0) > Version: 2.15.4 > > What were you doing when the application crashed? > installing ntp support from time and date > > > Distribution: Ubuntu 6.10 (edgy) > Gnome Release: 2.16.0 2006-09-04 (Ubuntu) > BugBuddy Version: 2.16.0 > > Memory status: size: 36737024 vsize: 0 resident: 36737024 share: 0 rss: > 15659008 rss_rlim: 0 > CPU usage: start_time: 1157751721 rtime: 0 utime: 437 stime: 0 cutime:417 > cstime: 0 timeout: 20 it_real_value: 0 frequency: 0 > > Backtrace was generated from '/usr/bin/time-admin' > > (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 -1225292112 (LWP 4857)] > 0xffffe410 in __kernel_vsyscall () > #0 0xffffe410 in __kernel_vsyscall () > #1 0xb73c32e3 in __waitpid_nocancel () > from /lib/tls/i686/cmov/libpthread.so.0 > #2 0xb7efe1b6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0 > #3 <signal handler called> > #4 0xb765b2f9 in g_type_check_instance_is_a () > from /usr/lib/libgobject-2.0.so.0 > #5 0xb7a00d9f in gtk_calendar_select_month () > from /usr/lib/libgtk-x11-2.0.so.0 > #6 0x0804dba9 in ?? () > #7 0x0814a600 in ?? () > #8 0x00000008 in ?? () > #9 0x000007d6 in ?? () > #10 0x00000000 in ?? () > > Thread 1 (Thread -1225292112 (LWP 4857)): > #0 0xffffe410 in __kernel_vsyscall () > No symbol table info available. > #1 0xb73c32e3 in __waitpid_nocancel () > from /lib/tls/i686/cmov/libpthread.so.0 > No symbol table info available. > #2 0xb7efe1b6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0 > No symbol table info available. > #3 <signal handler called> > No symbol table info available. > #4 0xb765b2f9 in g_type_check_instance_is_a () > from /usr/lib/libgobject-2.0.so.0 > No symbol table info available. > #5 0xb7a00d9f in gtk_calendar_select_month () > from /usr/lib/libgtk-x11-2.0.so.0 > No symbol table info available. > #6 0x0804dba9 in ?? () > No symbol table info available. > #7 0x0814a600 in ?? () > No symbol table info available. > #8 0x00000008 in ?? () > No symbol table info available. > #9 0x000007d6 in ?? () > No symbol table info available. > #10 0x00000000 in ?? () > No symbol table info available. > #0 0xffffe410 in __kernel_vsyscall () >
*** Bug 371932 has been marked as a duplicate of this bug. ***
*** Bug 372849 has been marked as a duplicate of this bug. ***
*** Bug 373703 has been marked as a duplicate of this bug. ***
*** Bug 374058 has been marked as a duplicate of this bug. ***
*** Bug 374525 has been marked as a duplicate of this bug. ***
*** Bug 375715 has been marked as a duplicate of this bug. ***
*** Bug 375928 has been marked as a duplicate of this bug. ***
*** Bug 376216 has been marked as a duplicate of this bug. ***
*** Bug 376579 has been marked as a duplicate of this bug. ***
*** Bug 377044 has been marked as a duplicate of this bug. ***
Please see comment #1 please install the glib, gtk+ and gnome-system-tools packages
*** Bug 377907 has been marked as a duplicate of this bug. ***
*** Bug 378109 has been marked as a duplicate of this bug. ***
*** Bug 378718 has been marked as a duplicate of this bug. ***
*** Bug 378990 has been marked as a duplicate of this bug. ***
*** Bug 379036 has been marked as a duplicate of this bug. ***
*** Bug 379349 has been marked as a duplicate of this bug. ***
*** Bug 379952 has been marked as a duplicate of this bug. ***
*** Bug 381368 has been marked as a duplicate of this bug. ***
*** Bug 382660 has been marked as a duplicate of this bug. ***
*** Bug 387314 has been marked as a duplicate of this bug. ***
*** Bug 387692 has been marked as a duplicate of this bug. ***
*** Bug 388234 has been marked as a duplicate of this bug. ***
*** Bug 390528 has been marked as a duplicate of this bug. ***
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces/ApplicationSpecificInstructions for more information on what packages to install. If that page confuses you, also read http://live.gnome.org/GettingTraces/ If still confused, please write a personal email to me and tell me why. Your feedback and help is appreciated.
*** Bug 396319 has been marked as a duplicate of this bug. ***
*** Bug 396392 has been marked as a duplicate of this bug. ***
*** Bug 398208 has been marked as a duplicate of this bug. ***
*** Bug 398784 has been marked as a duplicate of this bug. ***
*** Bug 398901 has been marked as a duplicate of this bug. ***
*** Bug 400065 has been marked as a duplicate of this bug. ***
*** Bug 400407 has been marked as a duplicate of this bug. ***
*** Bug 400539 has been marked as a duplicate of this bug. ***
*** Bug 402285 has been marked as a duplicate of this bug. ***
*** Bug 403731 has been marked as a duplicate of this bug. ***
*** Bug 404502 has been marked as a duplicate of this bug. ***
*** Bug 409026 has been marked as a duplicate of this bug. ***
*** Bug 409714 has been marked as a duplicate of this bug. ***
*** Bug 418006 has been marked as a duplicate of this bug. ***
*** Bug 418132 has been marked as a duplicate of this bug. ***
*** Bug 429737 has been marked as a duplicate of this bug. ***
Seems like this was a bug in version 2.15, I checked most duplicates. I think we can close this report as INCOMPLETE.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
*** Bug 440324 has been marked as a duplicate of this bug. ***
*** Bug 448301 has been marked as a duplicate of this bug. ***
*** Bug 456452 has been marked as a duplicate of this bug. ***
*** Bug 476087 has been marked as a duplicate of this bug. ***
*** Bug 476394 has been marked as a duplicate of this bug. ***