Bug 370926 – crash in Time and Date: trying to adjust the tim...

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 370926 - crash in Time and Date: trying to adjust the tim...


Summary:	crash in Time and Date: trying to adjust the tim...


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-05 09:19 UTC by deuteriumoxide
Modified:	2006-11-05 12:42 UTC

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

Description deuteriumoxide 2006-11-05 09:19:46 UTC

Version: 2.15.5

What were you doing when the application crashed?
trying to adjust the time again. I am still moving files from one file system to another though, which could be the problem.


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

Memory status: size: 51744768 vsize: 0 resident: 51744768 share: 0 rss: 11001856 rss_rlim: 0
CPU usage: start_time: 1162757988 rtime: 0 utime: 18 stime: 0 cutime:14 cstime: 0 timeout: 4 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 -1225070928 (LWP 14912)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 83126

Thread 1 (Thread -1225070928 (LWP 14912))

#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 André Klapper 2006-11-05 12:42:04 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 ***