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 353938 - crash in Time and Date: attempting to set the co...
crash in Time and Date: attempting to set the co...
Status: RESOLVED DUPLICATE of bug 352786
Product: gnome-system-tools
Classification: Deprecated
Component: time-admin
2.15.x
Other All
: High critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
: 353931 353932 353933 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-02 07:25 UTC by eyeleica
Modified: 2006-09-03 13:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description eyeleica 2006-09-02 07:25:06 UTC 
Version: 2.15.2

What were you doing when the application crashed?
attempting to set the correct time for pacific time zone


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.92 2006-08-22 (Ubuntu)
BugBuddy Version: 2.15.92

Memory status: size: 35328000 vsize: 0 resident: 35328000 share: 0 rss: 14487552 rss_rlim: 0
CPU usage: start_time: 1157156634 rtime: 0 utime: 196 stime: 0 cutime:173 cstime: 0 timeout: 23 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 -1224776016 (LWP 6418)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71397

Thread 1 (Thread -1224776016 (LWP 6418))

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


Sergej Kotliar





          2006-09-02 14:36:36 UTC
        



*** Bug 353933 has been marked as a duplicate of this bug. ***






Comment 2


Sergej Kotliar





          2006-09-02 14:36:43 UTC
        



*** Bug 353932 has been marked as a duplicate of this bug. ***






Comment 3


Sergej Kotliar





          2006-09-02 14:36:51 UTC
        



*** Bug 353931 has been marked as a duplicate of this bug. ***






Comment 4


Sergej Kotliar





          2006-09-02 14:37:21 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 5


Sergej Kotliar





          2006-09-03 13:40:31 UTC
        




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