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 362445 - crash in Time and Date: I right clicked on the d...
crash in Time and Date: I right clicked on the d...
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-15 19:27 UTC by belanger
Modified: 2006-10-15 19:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description belanger 2006-10-15 19:27:37 UTC 
Version: 2.15.5

What were you doing when the application crashed?
I right clicked on the date &time part of the top menu and selected "Adjust Date&Time".

We I installed I had to select New York instead of Montreal because if I chose Montreal and clicked "Next" it stayed there.

I just changed to Montreal, rebooted and now the adjustment craches...


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 52277248 vsize: 0 resident: 52277248 share: 0 rss: 10866688 rss_rlim: 0
CPU usage: start_time: 1160940325 rtime: 0 utime: 13 stime: 0 cutime:12 cstime: 0 timeout: 1 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 -1226000720 (LWP 5039)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 76504

Thread 1 (Thread -1226000720 (LWP 5039))

  • #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-15 19:30:26 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 ***