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 362360 - crash in Time and Date: click to adjust time
crash in Time and Date: click to adjust time
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-15 13:03 UTC by sassa_mutema2002
Modified: 2006-10-15 15:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description sassa_mutema2002 2006-10-15 13:03:42 UTC 
Version: 2.15.5

What were you doing when the application crashed?
click to adjust time


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

Memory status: size: 51945472 vsize: 0 resident: 51945472 share: 0 rss: 10866688 rss_rlim: 0
CPU usage: start_time: 1160917403 rtime: 0 utime: 21 stime: 0 cutime:18 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 -1225099600 (LWP 26831)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 76447

Thread 1 (Thread -1225099600 (LWP 26831))

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


ebbywiselyn





          2006-10-15 13:36:40 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.






Comment 2


ebbywiselyn





          2006-10-15 14:13:18 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.






Comment 3


Karsten Bräckelmann





          2006-10-15 15:05:19 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 ***