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 362422 - crash in Time and Date: Pushed the button Zeit e...
crash in Time and Date: Pushed the button Zeit e...
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-15 17:07 UTC by Markus.Maeder
Modified: 2006-10-15 17:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Markus.Maeder 2006-10-15 17:07:59 UTC
Version: 2.15.4

What were you doing when the application crashed?
Pushed the button Zeit einstellen...


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

Memory status: size: 125640704 vsize: 125640704 resident: 17133568 share: 10280960 rss: 17133568 rss_rlim: -1
CPU usage: start_time: 1160939752 rtime: 48 utime: 36 stime: 12 cutime:0 cstime: 1 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 47140751147984 (LWP 6557)]
0x00002adfcde86eb5 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47140751147984 (LWP 6557))

  • #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 André Klapper 2006-10-15 17:15:48 UTC
Thanks for the bug report.
This has been fixed, please install the updates provided by Ubuntu.
Please feel free to report any further bugs you find.


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