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 363550 - crash in Time and Date: Setting the local time.....
crash in Time and Date: Setting the local time.....
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-20 01:08 UTC by vijay.garimella
Modified: 2006-10-20 09:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description vijay.garimella 2006-10-20 01:08:40 UTC 
Version: 2.15.4

What were you doing when the application crashed?
Setting the local time...


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 36933632 vsize: 0 resident: 36933632 share: 0 rss: 14557184 rss_rlim: 0
CPU usage: start_time: 1161306390 rtime: 0 utime: 278 stime: 0 cutime:191 cstime: 0 timeout: 87 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 -1225017680 (LWP 6755)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 77248

Thread 1 (Thread -1225017680 (LWP 6755))

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


ebbywiselyn





          2006-10-20 05:32:36 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


André Klapper





          2006-10-20 09:03:48 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 crash has been already fixed, please install the latest gnome-system-tools/liboobs update provided by Ubuntu. Thanks.

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