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 403731 - crash in Time and Date: Synchronizing the clock ...
crash in Time and Date: Synchronizing the clock ...
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: 2007-02-02 21:29 UTC by Matthew Whitworth
Modified: 2007-02-02 22:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Matthew Whitworth 2007-02-02 21:29:35 UTC 
Version: 2.15.5

What were you doing when the application crashed?
Synchronizing the clock once


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

Memory status: size: 40427520 vsize: 0 resident: 40427520 share: 0 rss: 16236544 rss_rlim: 0
CPU usage: start_time: 1170451529 rtime: 0 utime: 225 stime: 0 cutime:216 cstime: 0 timeout: 9 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/time-admin'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225521488 (LWP 5279)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 107504

Thread 1 (Thread -1225521488 (LWP 5279))

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





          2007-02-02 22:12:02 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 ***