Bug 352786 – crash on Time and Date -- setting timezone

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 352786 - crash on Time and Date -- setting timezone


Summary:	crash on Time and Date -- setting timezone


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:

Duplicates:	353279 353834 353938 353982 353989 354003 354050 354052 354098 354160 354176 354180 354343 354370 354607 354613 354729 355038 355059 (view as bug list)
Depends on:
Blocks:

Reported:	2006-08-25 05:03 UTC by bshotts
Modified:	2006-09-09 12:21 UTC

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

Description bshotts 2006-08-25 05:03:47 UTC

Version: 2.15.2

What were you doing when the application crashed?
trying to set timezone


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.91 2006-08-08 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 34910208 vsize: 0 resident: 34910208 share: 0 rss: 14389248 rss_rlim: 0
CPU usage: start_time: 1156482124 rtime: 0 utime: 532 stime: 0 cutime:502 cstime: 0 timeout: 30 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 -1224288592 (LWP 8479)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 70969

Thread 1 (Thread -1224288592 (LWP 8479))

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

Comment 1 Karsten Bräckelmann 2006-08-28 20:51:31 UTC

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

Comment 2 Karsten Bräckelmann 2006-08-28 20:52:31 UTC

Adjusted Summary.

Comment 3 Karsten Bräckelmann 2006-09-01 14:52:09 UTC

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

Comment 4 Karsten Bräckelmann 2006-09-01 14:55:13 UTC

Both duplicates happened during installation. Can you reproduce the crash after installtion as well?

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 5 Richard J. Korman 2006-09-01 21:45:34 UTC

The crash is not reproducible after installation. 
Tested by right clicking the date/time widget > adjsut date/time > select time zone. Shows up fine with no crash.

Comment 6 Sergej Kotliar 2006-09-03 13:40:31 UTC

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

Comment 7 Sergej Kotliar 2006-09-03 13:40:58 UTC

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

Comment 8 Sergej Kotliar 2006-09-03 13:41:29 UTC

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

Comment 9 Sergej Kotliar 2006-09-03 13:41:58 UTC

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

Comment 10 Sergej Kotliar 2006-09-03 13:42:15 UTC

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

Comment 11 Sergej Kotliar 2006-09-03 13:43:00 UTC

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

Comment 12 Sergej Kotliar 2006-09-03 13:45:23 UTC

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

Comment 13 Brent Smith (smitten) 2006-09-03 16:13:44 UTC

This stacktrace doesn't have enough debugging symbols to really show the problem, but based on the frequency of the crashs, I think this is really a duplicate of 351603

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

Comment 14 Sergej Kotliar 2006-09-03 20:20:42 UTC

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

Comment 15 Sergej Kotliar 2006-09-03 21:41:14 UTC

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

Comment 16 Sergej Kotliar 2006-09-03 21:41:24 UTC

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

Comment 17 Sergej Kotliar 2006-09-05 10:02:33 UTC

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

Comment 18 Sergej Kotliar 2006-09-05 10:02:43 UTC

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

Comment 19 Sergej Kotliar 2006-09-06 14:53:16 UTC

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

Comment 20 Sergej Kotliar 2006-09-06 14:53:35 UTC

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

Comment 21 Sergej Kotliar 2006-09-07 08:09:31 UTC

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

Comment 22 Sergej Kotliar 2006-09-09 11:12:16 UTC

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

Comment 23 Sergej Kotliar 2006-09-09 11:12:26 UTC

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

Comment 24 Scott 2006-09-09 12:21:09 UTC

(In reply to comment #4)
> 
> Thanks for the bug report. Unfortunately, that stack trace is not very useful
> in determining the cause of the crash. Can you get us one with debugging
> symbols? Please see http://live.gnome.org/GettingTraces for more information on
> how to do so.
> 

The stack trace was the best one could do under the circumstances.  Live CD, and Bug Buddy responded to the crash.  In turn, many of us responded to bug buddy.

And that's why you're reading this now. :-)