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 355184 - crash in Time and Date: Installing and I was set...
crash in Time and Date: Installing and I was set...
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-09 20:12 UTC by poolger
Modified: 2006-09-09 23:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description poolger 2006-09-09 20:12:49 UTC 
Version: 2.15.2

What were you doing when the application crashed?
Installing and I was setting the time


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

Memory status: size: 34160640 vsize: 0 resident: 34160640 share: 0 rss: 14491648 rss_rlim: 0
CPU usage: start_time: 1157839790 rtime: 0 utime: 107 stime: 0 cutime:103 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 -1224780112 (LWP 7035)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71996

Thread 1 (Thread -1224780112 (LWP 7035))

  • #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 dbus_error_has_name
    from /usr/lib/libdbus-1.so.3
  • #5 dbus_error_has_name
    from /usr/lib/libdbus-1.so.3
  • #6 dbus_message_iter_get_basic
    from /usr/lib/libdbus-1.so.3
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #0 __kernel_vsyscall 






Comment 1


Christian Kirbach





          2006-09-09 23:08:44 UTC
        



Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.
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 ***