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 356219 - crash in Time and Date: changing the time zone d...
crash in Time and Date: changing the time zone d...
Status: RESOLVED DUPLICATE of bug 351603
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-16 04:32 UTC by tobyglenn
Modified: 2006-09-17 13:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description tobyglenn 2006-09-16 04:32:39 UTC 
Version: 2.15.4

What were you doing when the application crashed?
changing the time zone during install 
I went to set time then selected chage time zone and it crashed


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 123719680 vsize: 123719680 resident: 17899520 share: 10199040 rss: 17899520 rss_rlim: -1
CPU usage: start_time: 1158366571 rtime: 138 utime: 117 stime: 21 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/time-admin'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47364293286480 (LWP 6521)]
0x00002b13da348e65 in waitpid () from /lib/libpthread.so.0

+ Trace 72460

Thread 1 (Thread 47364293286480 (LWP 6521))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Sergej Kotliar





          2006-09-17 13:04:57 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 ***