Bug 352355 – crash on Time and Date

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 352355 - crash on Time and Date


Summary:	crash on Time and Date


Status:	RESOLVED DUPLICATE of bug 355849

Product:	gnome-system-tools
Classification:	Deprecated
Component:	time-admin
Version:	2.15.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Carlos Garnacho
QA Contact:	Carlos Garnacho

URL:
Whiteboard:

Duplicates:	354077 (view as bug list)
Depends on:
Blocks:

Reported:	2006-08-22 09:14 UTC by Anders Kaseorg
Modified:	2006-10-10 11:23 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Anders Kaseorg 2006-08-22 09:14:50 UTC

Version: 2.15.2

What were you doing when the application crashed?
Unchecking an entry for time.mit.edu that I had just added in the Time servers dialog.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.91 2006-08-08 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 53497856 vsize: 0 resident: 53497856 share: 0 rss: 14893056 rss_rlim: 0
CPU usage: start_time: 1156238026 rtime: 0 utime: 212 stime: 0 cutime:207 cstime: 0 timeout: 5 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 -1225439040 (LWP 17943)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 70804

Thread 1 (Thread -1225439040 (LWP 17943))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 dbus_watch_handle
from /usr/lib/libdbus-1.so.2
#5 dbus_error_has_name
from /usr/lib/libdbus-1.so.2
#6 dbus_error_has_name
from /usr/lib/libdbus-1.so.2
#7 dbus_message_iter_append_basic
from /usr/lib/libdbus-1.so.2
#8 oobs_ntp_config_get
from /usr/lib/liboobs-1.so.0
#9 oobs_object_get_type
from /usr/lib/liboobs-1.so.0
#10 oobs_object_commit
from /usr/lib/liboobs-1.so.0
#11 ??
#12 ??
#13 ??
#14 ??
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-09-03 11:09:57 UTC

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.

Comment 2 Christian Kirbach 2006-09-03 11:10:57 UTC

*** Bug 354077 has been marked as a duplicate of this bug. ***

Comment 3 André Klapper 2006-10-10 11:23:35 UTC

Thanks for the bug report. This particular bug is a duplicate of bug 355849. Please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 355849 ***