Bug 354486 – crash in Time and Date: opened "Time and Date" f...

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 354486 - crash in Time and Date: opened "Time and Date" f...


Summary:	crash in Time and Date: opened "Time and Date" f...


Status:	RESOLVED INCOMPLETE

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:	356949 358179 (view as bug list)
Depends on:
Blocks:

Reported:	2006-09-05 17:42 UTC by rrwillia
Modified:	2007-10-29 23:08 UTC

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

Description rrwillia 2006-09-05 17:42:35 UTC

Version: 2.15.2

What were you doing when the application crashed?
opened "Time and Date" from Adminstration menu for first time.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 16642048 vsize: 0 resident: 43671552 share: 0 rss: 43671552 rss_rlim: 0
CPU usage: start_time: 937 rtime: 0 utime: 1157478062 stime: 0 cutime:249 cstime: 0 timeout: 239 it_real_value: 0 frequency: 10

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 805534912 (LWP 8385)]
0x0ea7a334 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 71651

Thread 1 (Thread 805534912 (LWP 8385))

#0 __waitpid_nocancel
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
#4 ??
#5 ??
#6 ??
#7 ??
#8 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#16 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#23 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#25 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#29 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#32 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#33 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#35 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#36 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
#38 generic_start_main
at ../csu/libc-start.c line 231
#39 __libc_start_main
at ../sysdeps/unix/sysv/linux/powerpc/libc-start.c line 127
#40 ??
#0 __waitpid_nocancel
from /lib/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-09-20 18:56:58 UTC

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

Comment 2 Karsten Bräckelmann 2006-09-28 20:35:45 UTC

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

Comment 3 Kjartan Maraas 2006-11-09 20:26:25 UTC

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!

Comment 4 André Klapper 2007-10-29 23:08:47 UTC

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!