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 366216 - crash in Time and Date: attempting to open date ...
crash in Time and Date: attempting to open date ...
Status: RESOLVED DUPLICATE of bug 351603
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-28 11:08 UTC by cgarrity
Modified: 2006-10-28 22:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description cgarrity 2006-10-28 11:08:37 UTC 
Version: 2.15.5

What were you doing when the application crashed?
attempting to open date and time


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

Memory status: size: 58966016 vsize: 0 resident: 58966016 share: 0 rss: 10862592 rss_rlim: 0
CPU usage: start_time: 1162033676 rtime: 0 utime: 24 stime: 0 cutime:23 cstime: 0 timeout: 1 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 -1225144048 (LWP 23199)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79215

Thread 1 (Thread -1225144048 (LWP 23199))

  • #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 ??
  • #5 ??
  • #6 ??
  • #0 __kernel_vsyscall 






Comment 1


Baptiste Mille-Mathias





          2006-10-28 15:08:30 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


cgarrity





          2006-10-28 17:47:05 UTC
        



I will give it a shot... don't be suprised if it takes me forever +1.  ;)

(In reply to comment #1)
> Thanks for taking the time to report this bug.
> Unfortunately, that stack trace is missing some elements that will help a lot
> to solve the problem, so it will be hard for the developers to fix that crash.
> Can you get us a stack trace with debugging symbols? Please see
> http://live.gnome.org/GettingTraces for more information on how to do so.
> Thanks in advance!
> 








Comment 3


Karsten Bräckelmann





          2006-10-28 22:59:31 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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