Bug 358179 – crash in Time and Date: changing time/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 358179 - crash in Time and Date: changing time/date


Summary:	crash in Time and Date: changing time/date


Status:	RESOLVED DUPLICATE of bug 354486

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:

Depends on:
Blocks:

Reported:	2006-09-28 19:51 UTC by jason
Modified:	2006-09-28 20:35 UTC

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

Description jason 2006-09-28 19:51:20 UTC

Version: 2.15.4

What were you doing when the application crashed?
changing time/date


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 15601664 vsize: 0 resident: 39260160 share: 0 rss: 39260160 rss_rlim: 0
CPU usage: start_time: 580 rtime: 0 utime: 1159451319 stime: 0 cutime:238 cstime: 0 timeout: 229 it_real_value: 0 frequency: 9

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 805535632 (LWP 6080)]
0x0ec52334 in __waitpid_nocancel () from /lib/libpthread.so.0

+ Trace 73498

Thread 1 (Thread 805535632 (LWP 6080))

#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-28 20:35:45 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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