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 380264 - crash in Time and Date: Using internet, trying t...
crash in Time and Date: Using internet, trying t...
Status: RESOLVED DUPLICATE of bug 368150
Product: gnome-system-tools
Classification: Deprecated
Component: time-admin
2.15.x
Other All
: High critical
: ---
Assigned To: Carlos Garnacho
Carlos Garnacho
: 382047 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-28 20:12 UTC by ubuntu
Modified: 2006-12-04 04:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description ubuntu 2006-11-28 20:12:32 UTC
Version: 2.15.5

What were you doing when the application crashed?
Using internet, trying to change the colours on the date and time.


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

Memory status: size: 54382592 vsize: 0 resident: 54382592 share: 0 rss: 11501568 rss_rlim: 0
CPU usage: start_time: 1164744912 rtime: 0 utime: 19 stime: 0 cutime:16 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 -1226057328 (LWP 8786)]
(no debugging symbols found)
0xb7eec410 in ?? ()

Thread 1 (Thread -1226057328 (LWP 8786))

  • #0 ??
  • #1 ??
  • #2 ??
  • #0 ??

Comment 1 Damien Durand 2006-11-28 22:12:13 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 368150 ***
Comment 2 Damien Durand 2006-12-04 04:24:00 UTC
*** Bug 382047 has been marked as a duplicate of this bug. ***