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 367055 - crash in Time and Date: versucht uhrzeitserver a...
crash in Time and Date: versucht uhrzeitserver a...
Status: RESOLVED INCOMPLETE
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 18:13 UTC by einer
Modified: 2006-11-29 00:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description einer 2006-10-29 18:13:09 UTC 
Version: 2.15.5

What were you doing when the application crashed?
versucht uhrzeitserver anzuwählen


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

Memory status: size: 38621184 vsize: 0 resident: 38621184 share: 0 rss: 15958016 rss_rlim: 0
CPU usage: start_time: 1162148846 rtime: 0 utime: 401 stime: 0 cutime:388 cstime: 0 timeout: 13 it_real_value: 0 frequency: 537

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 -1225492816 (LWP 6809)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79924

Thread 1 (Thread -1225492816 (LWP 6809))

  • #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 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall 






Comment 1


Sebastien Bacher





          2006-10-31 15:48:36 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


André Klapper





          2006-11-29 00:44:32 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!