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 366211 - crash in Time and Date: I've done update from da...
crash in Time and Date: I've done update from da...
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-28 10:47 UTC by suontausta
Modified: 2006-10-28 22:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description suontausta 2006-10-28 10:47:12 UTC
Version: 2.15.5

What were you doing when the application crashed?
I've done update from dapper->edgy and now some items in system-adminstration menu don't work. I get error "The configuration could not be loaded. You are not allowed to access the system configuration". I tried to launch time-admin from terminal and got this bug reporting tool after it crashed. If I try to launch time-admin without gksudo it gives me same error dialog when launching it from menu.

$ gksudo time-admin

(time-admin:4088): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

(bug-buddy:4097): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

** (bug-buddy:4097): WARNING **: Couldn't load icon for Open Folder



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

Memory status: size: 59383808 vsize: 0 resident: 59383808 share: 0 rss: 10829824 rss_rlim: 0
CPU usage: start_time: 1162032003 rtime: 0 utime: 22 stime: 0 cutime:19 cstime: 0 timeout: 3 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 -1225701104 (LWP 4088)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225701104 (LWP 4088))

  • #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 Baptiste Mille-Mathias 2006-10-28 15:08:06 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Karsten Bräckelmann 2006-10-28 22:59:13 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 ***