Bug 366327 – crash in 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 366327 - crash in Time and Date:


Summary:	crash in Time and Date:


Status:	RESOLVED DUPLICATE of bug 351603

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-10-28 14:52 UTC by oleg_l
Modified:	2006-10-28 22:58 UTC

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

Description oleg_l 2006-10-28 14:52:09 UTC

Version: 2.15.5

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 60297216 vsize: 0 resident: 60297216 share: 0 rss: 10858496 rss_rlim: 0
CPU usage: start_time: 1162046984 rtime: 0 utime: 55 stime: 0 cutime:49 cstime: 0 timeout: 6 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 -1225484016 (LWP 7859)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79305

Thread 1 (Thread -1225484016 (LWP 7859))

#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 ??
#5 ??
#6 ??
#0 __kernel_vsyscall

Comment 1 Baptiste Mille-Mathias 2006-10-28 15:11:19 UTC

Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!

Comment 2 Karsten Bräckelmann 2006-10-28 22:58:43 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 351603 ***