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 386624 - crash in Time and Date: Stavo sincronizzando l'o...
crash in Time and Date: Stavo sincronizzando l'o...
Status: RESOLVED DUPLICATE of bug 358383
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-12-16 22:10 UTC by litiokekko
Modified: 2006-12-17 08:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description litiokekko 2006-12-16 22:10:24 UTC 
Version: 2.15.5

What were you doing when the application crashed?
Stavo sincronizzando l'ora da internet


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

Memory status: size: 38502400 vsize: 0 resident: 38502400 share: 0 rss: 15642624 rss_rlim: 0
CPU usage: start_time: 1166306303 rtime: 0 utime: 572 stime: 0 cutime:564 cstime: 0 timeout: 8 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 5121)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 94714

Thread 1 (Thread -1224989008 (LWP 5121))

  • #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 g_type_check_instance
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_signal_handlers_unblock_matched
    from /usr/lib/libgobject-2.0.so.0
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2006-12-17 08:00:49 UTC
        



Thanks for taking the time to report this bug.
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 in order to help the developers?


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