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 378109 - crash in Time and Date: synchronized with timese...
crash in Time and Date: synchronized with timese...
Status: RESOLVED DUPLICATE of bug 355015
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-22 13:03 UTC by bugbuddy.10.chaecker
Modified: 2006-11-22 18:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description bugbuddy.10.chaecker 2006-11-22 13:03:37 UTC 
Version: 2.15.5

What were you doing when the application crashed?
synchronized with timeserver


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

Memory status: size: 66433024 vsize: 0 resident: 66433024 share: 0 rss: 15745024 rss_rlim: 0
CPU usage: start_time: 1164200311 rtime: 0 utime: 331 stime: 0 cutime:319 cstime: 0 timeout: 12 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 23926)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 88491

Thread 1 (Thread -1225099600 (LWP 23926))

  • #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 g_type_check_instance_is_a
    from /usr/lib/libgobject-2.0.so.0
  • #5 gtk_calendar_select_month
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall 






Comment 1


Damien Durand





          2006-11-22 18:53:34 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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