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 379619 - crash in Time and Date: I put the computer into ...
crash in Time and Date: I put the computer into ...
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: 2006-11-26 23:25 UTC by thetron
Modified: 2006-11-27 15:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description thetron 2006-11-26 23:25:56 UTC 
Version: 2.15.5

What were you doing when the application crashed?
I put the computer into hibination mode. Then this bug message appeared


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

Memory status: size: 37924864 vsize: 0 resident: 37924864 share: 0 rss: 15269888 rss_rlim: 0
CPU usage: start_time: 1164026652 rtime: 0 utime: 4781 stime: 0 cutime:4720 cstime: 0 timeout: 61 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 -1225288016 (LWP 25611)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 89611

Thread 1 (Thread -1225288016 (LWP 25611))

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


Damien Durand





          2006-11-27 15:52:47 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 ***