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 483577 - crash in Time and Date: installing a tool NTP to...
crash in Time and Date: installing a tool NTP to...
Status: RESOLVED DUPLICATE of bug 361175
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-10-05 03:21 UTC by johngeronilla
Modified: 2007-10-05 13:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description johngeronilla 2007-10-05 03:21:14 UTC 
Version: 2.15.5

What were you doing when the application crashed?
installing a tool NTP tool for sychronizing my local time to server time


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

Memory status: size: 39002112 vsize: 0 resident: 39002112 share: 0 rss: 16252928 rss_rlim: 0
CPU usage: start_time: 1191553181 rtime: 0 utime: 460 stime: 0 cutime:453 cstime: 0 timeout: 7 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 -1225414992 (LWP 6190)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 167874

Thread 1 (Thread -1225414992 (LWP 6190))

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






Comment 1


Carlos Garnacho





          2007-10-05 13:08:03 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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