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 419096 - crash in Time and Date: adjusting time to intern...
crash in Time and Date: adjusting time to intern...
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-03-16 20:26 UTC by averschuuren
Modified: 2007-03-16 20:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description averschuuren 2007-03-16 20:26:32 UTC
Version: 2.15.5

What were you doing when the application crashed?
adjusting time to internet servers		


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

Memory status: size: 38002688 vsize: 0 resident: 38002688 share: 0 rss: 15413248 rss_rlim: 0
CPU usage: start_time: 1174076517 rtime: 0 utime: 177 stime: 0 cutime:170 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225689424 (LWP 5976)]
(no debugging symbols found)
0xb7315bfe in __waitpid_nocancel () from /lib/libpthread.so.0

Thread 1 (Thread -1225689424 (LWP 5976))

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_type_check_instance_is_a
    from /usr/lib/libgobject-2.0.so.0
  • #4 gtk_calendar_select_day
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0

Comment 1 Christian Kirbach 2007-03-16 20:30:46 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 361175 ***