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 358446 - crash in Time and Date: running the installer fr...
crash in Time and Date: running the installer fr...
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-09-30 07:39 UTC by paul.daniel
Modified: 2006-09-30 12:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description paul.daniel 2006-09-30 07:39:11 UTC
Version: 2.15.4

What were you doing when the application crashed?
running the installer from the daily build CD - picked time zone, clicked set time button then on the set time zone button in that window


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

Memory status: size: 35557376 vsize: 0 resident: 35557376 share: 0 rss: 14827520 rss_rlim: 0
CPU usage: start_time: 1159684641 rtime: 0 utime: 108 stime: 0 cutime:102 cstime: 0 timeout: 6 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 -1225341264 (LWP 6576)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225341264 (LWP 6576))

  • #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 André Klapper 2006-09-30 09:00:00 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Karsten Bräckelmann 2006-09-30 12:55:42 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 ***