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 360349 - crash in Time and Date: trying to install to har...
crash in Time and Date: trying to install to har...
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-07 10:15 UTC by jvereijssen
Modified: 2006-10-07 14:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jvereijssen 2006-10-07 10:15:10 UTC 
Version: 2.15.4

What were you doing when the application crashed?
trying to install to harddisk


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

Memory status: size: 36888576 vsize: 0 resident: 36888576 share: 0 rss: 14516224 rss_rlim: 0
CPU usage: start_time: 1160216021 rtime: 0 utime: 67 stime: 0 cutime:63 cstime: 0 timeout: 4 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 -1225939280 (LWP 7083)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 75050

Thread 1 (Thread -1225939280 (LWP 7083))

  • #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-07 14:40:51 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.

We ask everybody to please update to the latest version provided by Ubuntu
which should contain this fix! Thanks in advance.

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