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 356465 - crash in Time and Date: Etch AMD_64 Trying a cle...
crash in Time and Date: Etch AMD_64 Trying a cle...
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-17 22:42 UTC by maury0324
Modified: 2006-09-17 22:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description maury0324 2006-09-17 22:42:00 UTC
Version: 2.15.4

What were you doing when the application crashed?
Etch AMD_64 Trying a clean install to hard disk. It boots to live CD OK and it hangs at step 2 You can set the time and date but then it hangs and will not go to step 3 of the install. 


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

Memory status: size: 123727872 vsize: 123727872 resident: 17883136 share: 10162176 rss: 17883136 rss_rlim: -1
CPU usage: start_time: 1158518310 rtime: 114 utime: 106 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/time-admin'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47353884060240 (LWP 7165)]
0x00002b116dc45e65 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47353884060240 (LWP 7165))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 ??
  • #0 waitpid
    from /lib/libpthread.so.0

Comment 1 Karsten Bräckelmann 2006-09-17 22:51:09 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 ***