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 363452 - crash in Time and Date: Trying to run Adjust Tim...
crash in Time and Date: Trying to run Adjust Tim...
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-19 16:27 UTC by rjhazlip
Modified: 2006-10-19 18:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description rjhazlip 2006-10-19 16:27:57 UTC
Version: 2.15.5

What were you doing when the application crashed?
Trying to run Adjust Time and Date


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 60768256 vsize: 0 resident: 60768256 share: 0 rss: 10846208 rss_rlim: 0
CPU usage: start_time: 1161317634 rtime: 0 utime: 19 stime: 0 cutime:10 cstime: 0 timeout: 9 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 -1225394512 (LWP 5346)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225394512 (LWP 5346))

  • #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 André Klapper 2006-10-19 18:02:59 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 has been fixed already, please install the latest gnome-system-tools/liboobs updates provided by Ubuntu.

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