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 354370 - crash in Time and Date: During install, selected...
crash in Time and Date: During install, selected...
Status: RESOLVED DUPLICATE of bug 352786
Product: gnome-system-tools
Classification: Deprecated
Component: time-admin
2.15.x
Other All
: High critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
Depends on:
Blocks:
 
 
Reported: 2006-09-05 00:23 UTC by ryan
Modified: 2006-09-05 10:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description ryan 2006-09-05 00:23:05 UTC 
Version: 2.15.2

What were you doing when the application crashed?
During install, selected a location (Detroit), then noticed the current time was 4 hours fast, so clicked Set Time, then clicked the button to check Time Zone.  It immediately brought up the bug reporting tool at that point without showing me any time zone info.	


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 35319808 vsize: 0 resident: 35319808 share: 0 rss: 14491648 rss_rlim: 0
CPU usage: start_time: 1157415634 rtime: 0 utime: 107 stime: 0 cutime:96 cstime: 0 timeout: 11 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 -1225300304 (LWP 6827)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71604

Thread 1 (Thread -1225300304 (LWP 6827))

  • #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


Sergej Kotliar





          2006-09-05 10:02: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 352786 ***