GNOME Bugzilla – Bug 443139
crash after adding a new user [gconf_client_get ()]
Last modified: 2011-06-10 12:24:39 UTC
Version: 2.17.4 What were you doing when the application crashed? I was adding a second user Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 34791424 vsize: 34791424 resident: 11186176 share: 8523776 rss: 11186176 rss_rlim: 4294967295 CPU usage: start_time: 1180757002 rtime: 46 utime: 36 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/fast-user-switch-applet' (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 -1208518944 (LWP 3042)] (no debugging symbols found) 0x00a6a402 in __kernel_vsyscall ()
+ Trace 137445
Thread 1 (Thread -1208518944 (LWP 3042))
----------- .xsession-errors (420 sec old) --------------------- localuser:jonny being added to access control list SESSION_MANAGER=local/norna:/tmp/.ICE-unix/2827 error getting update info: Cannot open/read repomd.xml file for repository: fedora compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 error getting update info: Cannot open/read repomd.xml file for repository: fedora gtk-window-decorator: Could not acquire decoration manager selection on screen 0 display ":0.0" compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 gtk-window-decorator: Could not acquire decoration manager selection on screen 0 display ":0.0" compiz: No GLXFBConfig for default depth, this isn't going to work. compiz: Failed to manage screen: 0 compiz: No manageable screens found on display :0.0 --------------------------------------------------
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 and reopen this bug or report a new one. Thanks in advance!
*** Bug 452409 has been marked as a duplicate of this bug. ***
*** Bug 443632 has been marked as a duplicate of this bug. ***
I don't see a f-u-s debugging package.
@bc98kinney: on what distro? if you can compile it yourself that's often the easiest way, though I understand that's a formidable PITA for a lot of people. otherwise i/we/you can go talk to your distro people and find a debugging package. @Teppo: you are doing awesome work. thank you. i will (please gods) have debugging time to work on this later today.
(In reply to comment #4) I don't see a f-u-s debugging package for Fedora7, nor is there an exact match for glib2 (I installed glib2-devel, though), and nothing close for gtk2.
I've never used Fedora7 so I can't really comment, but I'll ask around.
*** Bug 461289 has been marked as a duplicate of this bug. ***
*** Bug 463625 has been marked as a duplicate of this bug. ***
*** Bug 464472 has been marked as a duplicate of this bug. ***
*** Bug 466324 has been marked as a duplicate of this bug. ***
*** Bug 460031 has been marked as a duplicate of this bug. ***
*** Bug 472842 has been marked as a duplicate of this bug. ***
*** Bug 481384 has been marked as a duplicate of this bug. ***
*** Bug 485819 has been marked as a duplicate of this bug. ***
*** Bug 480237 has been marked as a duplicate of this bug. ***
*** Bug 489955 has been marked as a duplicate of this bug. ***
*** Bug 510545 has been marked as a duplicate of this bug. ***
*** Bug 505898 has been marked as a duplicate of this bug. ***
*** Bug 504187 has been marked as a duplicate of this bug. ***
*** Bug 504169 has been marked as a duplicate of this bug. ***
Last duplicate had a great trace for this, setting as NEW. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 20:39:56 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 271204352 vsize: 271204352 resident: 16916480 share: 13807616 rss: 16916480 rss_rlim: 18446744073709551615 CPU usage: start_time: 1197689950 rtime: 15 utime: 10 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/fast-user-switch-applet' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496391776 (LWP 5354)] 0x0000003a40a0d945 in waitpid () from /lib64/libpthread.so.0
+ Trace 191148
Thread 1 (Thread 46912496391776 (LWP 5354))
fast-user-switch-applet development has been stalled and it has been unmaintained for a few years now. Maintainers don't have future development plan so i am closing the bugs as WONTFIX. Please feel free to reopen the bugs in future if anyone takes the responsibility of active development.