Bug 368957 – crash in Time and Date: Right clicked on the clo...

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 368957 - crash in Time and Date: Right clicked on the clo...


Summary:	crash in Time and Date: Right clicked on the clo...


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-11-01 17:21 UTC by yuri
Modified:	2006-11-01 17:32 UTC

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

Description yuri 2006-11-01 17:21:25 UTC

Version: 2.15.5

What were you doing when the application crashed?
Right clicked on the clock on my launchpanel and chose 'adjust date & time'.
Repeatable. Other functions in the same menu work well.


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

Memory status: size: 51843072 vsize: 0 resident: 51843072 share: 0 rss: 10866688 rss_rlim: 0
CPU usage: start_time: 1162401409 rtime: 0 utime: 15 stime: 0 cutime:13 cstime: 0 timeout: 2 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 -1225889520 (LWP 5447)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 81515

Thread 1 (Thread -1225889520 (LWP 5447))

#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 Karsten Bräckelmann 2006-11-01 17:32:29 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 ***