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 363800 - crash in Time and Date: nothing
crash in Time and Date: nothing
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-10-21 00:20 UTC by raleighsfinest
Modified: 2006-10-21 00:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description raleighsfinest 2006-10-21 00:20:25 UTC 
Version: 2.15.4

What were you doing when the application crashed?
nothing


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

Memory status: size: 126824448 vsize: 126824448 resident: 17256448 share: 10330112 rss: 17256448 rss_rlim: -1
CPU usage: start_time: 1161389987 rtime: 37 utime: 35 stime: 2 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 47075472618448 (LWP 7788)]
0x00002ad09b011eb5 in waitpid () from /lib/libpthread.so.0

+ Trace 77402

Thread 1 (Thread 47075472618448 (LWP 7788))

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






Comment 1


Karsten Bräckelmann





          2006-10-21 00:29:34 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 ***