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 369237 - crash in Time and Date: I've been trying to adju...
crash in Time and Date: I've been trying to adju...
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-11-02 04:47 UTC by stevevbjr
Modified: 2006-11-02 10:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description stevevbjr 2006-11-02 04:47:46 UTC
Version: 2.15.5

What were you doing when the application crashed?
I've been trying to adjust date and time by right clicking on the time in the upper left.  I'm using gnome, have tried kde once but default is gnome.  I am able to change the date and time through administration but not by clicking on the date and time in the corner.


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

Memory status: size: 60858368 vsize: 0 resident: 60858368 share: 0 rss: 10862592 rss_rlim: 0
CPU usage: start_time: 1162442762 rtime: 0 utime: 16 stime: 0 cutime:10 cstime: 0 timeout: 6 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 -1225210192 (LWP 5618)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225210192 (LWP 5618))

  • #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-11-02 10:44:14 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 ***