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 362671 - crash in Time and Date: Running the live cd inst...
crash in Time and Date: Running the live cd 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-10-16 18:19 UTC by Duncan Lithgow
Modified: 2006-10-16 19:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Duncan Lithgow 2006-10-16 18:19:50 UTC 
Version: 2.15.4

What were you doing when the application crashed?
Running the live cd installer of edgy beta. Selected city to base local time on and then attempted to click 'Set Time...'. This caused the crash you are seeing.

(I will file a seperate bug about the fact that my keyboard hasn't been set correctly so it's rather awkward writing this message)


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

Memory status: size: 36913152 vsize: 0 resident: 36913152 share: 0 rss: 14417920 rss_rlim: 0
CPU usage: start_time: 1161029690 rtime: 0 utime: 88 stime: 0 cutime:83 cstime: 0 timeout: 5 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 -1224989008 (LWP 6769)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 76650

Thread 1 (Thread -1224989008 (LWP 6769))

  • #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-10-16 19:57:25 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 ***