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 354551 - crash in Time and Date: Inputing info befor inst...
crash in Time and Date: Inputing info befor inst...
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-06 02:00 UTC by John Hushagen
Modified: 2006-09-06 08:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description John Hushagen 2006-09-06 02:00:59 UTC
Version: 2.15.2

What were you doing when the application crashed?
Inputing info befor installing to HD


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

Memory status: size: 35323904 vsize: 0 resident: 35323904 share: 0 rss: 14503936 rss_rlim: 0
CPU usage: start_time: 1157482745 rtime: 0 utime: 366 stime: 0 cutime:332 cstime: 0 timeout: 34 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 -1224943952 (LWP 6697)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224943952 (LWP 6697))

  • #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 Karsten Bräckelmann 2006-09-06 08:18:46 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.


Another duplicate of bug 352786, which is a duplicate of bug 351603.

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