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 361410 - crash in Time and Date: selected austria/vienna ...
crash in Time and Date: selected austria/vienna ...
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-11 12:03 UTC by Christian Gonzalez
Modified: 2006-10-11 17:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Christian Gonzalez 2006-10-11 12:03:58 UTC
Version: 2.15.4

What were you doing when the application crashed?
selected austria/vienna on the map, clicked on button "zeit einstellen..." and the on "Zeitzone auswählen" (select time zone)


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

Memory status: size: 37318656 vsize: 0 resident: 37318656 share: 0 rss: 14745600 rss_rlim: 0
CPU usage: start_time: 1160567953 rtime: 0 utime: 67 stime: 0 cutime:63 cstime: 0 timeout: 4 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 -1225967952 (LWP 6925)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225967952 (LWP 6925))

  • #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 Fabio Bonelli 2006-10-11 13:39:57 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-10-11 17:17:58 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 ***