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 356821 - crash in Time and Date: time and date selected ...
crash in Time and Date: time and date selected ...
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-20 01:06 UTC by ifennell
Modified: 2006-09-20 01:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description ifennell 2006-09-20 01:06:53 UTC
Version: 2.15.4

What were you doing when the application crashed?
time and date selected 
selected change time zone 
busy then bug window
just filed bug prior to this
this is more exact
using Unbutu 6.10 amd64  dual  opteron ,msi 9131 mb
can't find ver , but minted this week I think


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

Memory status: size: 123723776 vsize: 123723776 resident: 17920000 share: 10203136 rss: 17920000 rss_rlim: -1
CPU usage: start_time: 1158714170 rtime: 74 utime: 67 stime: 7 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 47078710491728 (LWP 11060)]
0x00002ad15c24ee65 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47078710491728 (LWP 11060))

  • #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-20 01:25:18 UTC
> this is more exact

Thanks for your love to details and being exact. :)  Same known issue, though.


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 ***