GNOME Bugzilla – Bug 370547
Dialog window about bug
Last modified: 2006-11-09 20:04:14 UTC
Please describe the problem: When Gnome starts it shows that some bug appeared. It said that bug is in gnome-settings, I think. Installed bug-buddy and it cannot say where bug really is and for some reason can not report that bug to bugzilla. Everything works and I also don't know what the problem really is. Only that message and bug-buddy annoys every time gnome starts. Steps to reproduce: Gnome starts, panels start, panels are blank and then bug-buddy starts, then everything else starts just fine. Actual results: Expected results: Does this happen every time? Yes. Every time when Gnome starts. Other information: Bug-buddy details: System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:39:22 EDT 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Disabled ----------- .xsession-errors (9 sec old) --------------------- Window manager warning: Workarounds for broken applications disabled. Some applications may not behave properly. /usr/bin/info: /usr/bin/info: cannot execute binary file ** (gnome-session:2688): WARNING **: Host name lookup failure on localhost. evolution-alarm-notify-Message: Setting timeout for 23581 1162677600 1162654019 evolution-alarm-notify-Message: Sun Nov 5 00:00:00 2006 evolution-alarm-notify-Message: Sat Nov 4 17:26:59 2006 winscard_clnt.c:320:SCardEstablishContextTH() Cannot open public shared file: /var/run/pcscd.pub Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension seahorse nautilus module initialized Initializing nautilus-flac-converter extension Initializing nautilus-image-converter extension -------------------------------------------------- Memory status: size: 268083200 vsize: 268083200 resident: 10436608 share: 7839744 rss: 10436608 rss_rlim: -1 CPU usage: start_time: 1162654015 rtime: 14 utime: 10 stime: 4 cutime:12 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/gnome-settings-daemon' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912506568992 (LWP 2757)] [New Thread 1084229952 (LWP 2759)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x000000378240d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 82797
Thread 1 (Thread 46912506568992 (LWP 2757))
Tried to login as root and no errors. Then I understood that error appears when panels are loading. If i killed panels, they restart and error appears. Something in panels. By restarting all applets I found that it is in keyboard language indicator. If only I add Lithuanian, applet reloads and saying about bug in gnome-settings-daemon. Then everything looks good only instead of USA and LT applet shows usa and lt. Nothing tragic really because bug only is in applet not in keybord settings. I can change language by keyboard. Bug appears for all users when Lithuanian is added. I removed indicator and that is solution for some time...
This appears to be a direct duplicate of Bug 370038 based on xkl_config_rec_dump() in the stack trace. A near identical stack trace (viz. dbus_server_setup_with_g_main->...->gtk_main_quit->xkl_config_rec_dump) is in Bug 369256 which has already been dup'ed to Bug 370038. Further corroboration is from fuxialis' own effort in narrowing it down to the keyboard language indicator.
Could you try logging into a failsafe session, and then run "dbus-launch --exit-with-session gnome-session" and see if it works? GNOME will fail to run properly if dbus-launch isn't in the command. Do any useful messages get echoed to the terminal window when you run gnome-session in this way? Also, do Roshan's comments help you figure out the problem?
most probably a duplicate of bug 370038?
*** Bug 372899 has been marked as a duplicate of this bug. ***
indeed... sorry for the noise *** This bug has been marked as a duplicate of 370038 *** *** This bug has been marked as a duplicate of 370038 ***