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 363826 - crash in Time and Date: I simply attempted to ad...
crash in Time and Date: I simply attempted to ad...
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 03:14 UTC by u_cdavidson
Modified: 2006-10-21 14:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description u_cdavidson 2006-10-21 03:14:20 UTC 
Version: 2.15.5

What were you doing when the application crashed?
I simply attempted to adjust the time and date by right clicking on the gnome clock applet and selecting 'Adjust Date & Time' from the menu.  I can adjust the time and date fine if I use System > Administration > 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: 51961856 vsize: 0 resident: 51961856 share: 0 rss: 10858496 rss_rlim: 0
CPU usage: start_time: 1161400296 rtime: 0 utime: 15 stime: 0 cutime:12 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 -1225312592 (LWP 5854)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 77415

Thread 1 (Thread -1225312592 (LWP 5854))

  • #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-21 14:51: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.

Please update to the latest version and install the updates provided by
Ubuntu.

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