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 354081 - crash in Time and Date: Changing the date, then ...
crash in Time and Date: Changing the date, then ...
Status: RESOLVED DUPLICATE of bug 351368
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-03 07:52 UTC by willwm
Modified: 2006-09-03 11:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description willwm 2006-09-03 07:52:27 UTC
Version: 2.15.2

What were you doing when the application crashed?
Changing the date, then changing the hour.


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

Memory status: size: 35319808 vsize: 0 resident: 35319808 share: 0 rss: 13922304 rss_rlim: 0
CPU usage: start_time: 1157244686 rtime: 0 utime: 117 stime: 0 cutime:52 cstime: 0 timeout: 65 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 -1224526160 (LWP 6297)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224526160 (LWP 6297))

  • #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 dbus_error_has_name
    from /usr/lib/libdbus-1.so.3
  • #5 dbus_error_has_name
    from /usr/lib/libdbus-1.so.3
  • #6 dbus_message_iter_get_basic
    from /usr/lib/libdbus-1.so.3
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-09-03 11:13:04 UTC
most likely a duplicate

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report?


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