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 364854 - crash in Time and Date: Just tried to start it t...
crash in Time and Date: Just tried to start it t...
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-25 00:11 UTC by kip
Modified: 2006-10-25 00:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description kip 2006-10-25 00:11:00 UTC 
Version: 2.15.5

What were you doing when the application crashed?
Just tried to start it to sync the time to the network.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 52834304 vsize: 0 resident: 52834304 share: 0 rss: 10858496 rss_rlim: 0
CPU usage: start_time: 1161720700 rtime: 0 utime: 29 stime: 0 cutime:26 cstime: 0 timeout: 3 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 -1226033488 (LWP 7372)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 78139

Thread 1 (Thread -1226033488 (LWP 7372))

  • #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-10-25 00:20:26 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 issue has been fixed already.

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