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 361501 - crash in Time and Date: Attempting to enable NTP...
crash in Time and Date: Attempting to enable NTP...
Status: RESOLVED DUPLICATE of bug 361498
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-11 17:33 UTC by clay.berlo
Modified: 2006-10-11 17:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description clay.berlo 2006-10-11 17:33:15 UTC 
Version: 2.15.5

What were you doing when the application crashed?
Attempting to enable NTP synchronization again.


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

Memory status: size: 46673920 vsize: 0 resident: 46673920 share: 0 rss: 15691776 rss_rlim: 0
CPU usage: start_time: 1160587720 rtime: 0 utime: 338 stime: 0 cutime:326 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 -1225132368 (LWP 6399)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75855

Thread 1 (Thread -1225132368 (LWP 6399))

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






Comment 1


Karsten Bräckelmann





          2006-10-11 17:45:18 UTC
        




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