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 367004 - crash in Time and Date: In light to the first bu...
crash in Time and Date: In light to the first bu...
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 16:55 UTC by hassanelmi85
Modified: 2006-10-29 17:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description hassanelmi85 2006-10-29 16:55:16 UTC 
Version: 2.15.5

What were you doing when the application crashed?
In light to the first bug report I sent, I then right clicked on the time at the bottom of the screen and selected Adjust Date/Time.

Thats what caused the crashed and not the Double clicking on the Time as I have mentioned in the first bug report.


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

Memory status: size: 52260864 vsize: 0 resident: 52260864 share: 0 rss: 10866688 rss_rlim: 0
CPU usage: start_time: 1162140832 rtime: 0 utime: 14 stime: 0 cutime:12 cstime: 0 timeout: 2 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 -1225599312 (LWP 10890)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79873

Thread 1 (Thread -1225599312 (LWP 10890))

  • #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


Karsten Bräckelmann





          2006-10-29 17:01:46 UTC
        



Thanks for your love to details, Hassan. :)  Understood your description in the first place.


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