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 366618 - crash in Time and Date: Trying to adjust the dat...
crash in Time and Date: Trying to adjust the dat...
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-29 02:21 UTC by andreas.oppeboen
Modified: 2006-10-29 11:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description andreas.oppeboen 2006-10-29 02:21:50 UTC 
Version: 2.15.5

What were you doing when the application crashed?
Trying to adjust the date/time-settings via right-clicking on the date/time on the toolbar and selecting the "Adjust Date & Time"-option.

The clock was off because I set the time in windows (dual-boot)


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

Memory status: size: 32481280 vsize: 0 resident: 32481280 share: 0 rss: 10838016 rss_rlim: 0
CPU usage: start_time: 1162009169 rtime: 0 utime: 27 stime: 0 cutime:24 cstime: 0 timeout: 3 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 -1225860848 (LWP 5574)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79544

Thread 1 (Thread -1225860848 (LWP 5574))

  • #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-29 11:53:44 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 issue has been fixed already, please install any updates provided by Ubuntu.

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