GNOME Bugzilla – Bug 370038
crash in Keyboard: 1. I just navigated to S...
Last modified: 2007-04-18 13:06:03 UTC
Version: 2.16.0 What were you doing when the application crashed? 1. I just navigated to System->Preferences->Keyboard. And Bug-buddy popped up. 2. I'm running Fedora Core 6 (GNOME 2.16). 3. Other relevant packages are control-center-2.16.0-9.fc6, libxklavier-3.0-1.fc6 4. A similar crash was seen by me previously for the gnome-settings-daemon. Bug 370025 has been raised for it. This crash appears to be identical to it in that xkl_config_rec_dump() is the function causing the crash although the driving function is gswitchit_kbd_config_get_lv_descriptions() here. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- ** (eggcups:2634): WARNING **: IPP request failed with status 1280 Debug: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml Debug: Loading Beagle.Util.Conf+NetworkingConfig from networking.xml Debug: Loading Beagle.Util.Conf+WebServicesConfig from webservices.xml Introspect error: The name edu.duke.linux.yum was not provided by any .service files Unable to connect to yum-updatesd... ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Xlib: unexpected async reply (sequence 0xd)! Unable to connect to yum-updatesd... ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Unable to connect to yum-updatesd... ** (bug-buddy:2940): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 25645056 vsize: 0 resident: 25645056 share: 0 rss: 9928704 rss_rlim: 0 CPU usage: start_time: 1162564904 rtime: 0 utime: 36 stime: 0 cutime:30 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-keyboard-properties' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1209018144 (LWP 2938)] 0x00ef7402 in __kernel_vsyscall ()
+ Trace 82373
Thread 1 (Thread -1209018144 (LWP 2938))
Here is another trace - but this time with libxklavier-debuginfo installed. It appears slightly different though the usecase is exactly the same. ============================================================================== Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml Debug: Loading Beagle.Util.Conf+NetworkingConfig from networking.xml Debug: Loading Beagle.Util.Conf+WebServicesConfig from webservices.xml Introspect error: The name edu.duke.linux.yum was not provided by any .service files Unable to connect to yum-updatesd... ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Xlib: unexpected async reply (sequence 0xd)! Unable to connect to yum-updatesd... ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Unable to connect to yum-updatesd... ** (bug-buddy:2940): WARNING **: Couldn't load icon for Open Folder Unable to connect to yum-updatesd... ** (bug-buddy:3074): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 25649152 vsize: 0 resident: 25649152 share: 0 rss: 9928704 rss_rlim: 0 CPU usage: start_time: 1162565767 rtime: 0 utime: 38 stime: 0 cutime:32 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-keyboard-properties' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208358688 (LWP 3072)] 0x001d0402 in __kernel_vsyscall ()
+ Trace 82376
Thread 1 (Thread -1208358688 (LWP 3072))
Wow, this is more interesting and way more informative. What is your XKB configuration? Could you please do xprop -root | grep XKB and gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
I am getting suspicious there is something broking in libxml... Actually, looking at version 3.0 of libxklavier (http://webcvs.freedesktop.org/xklavier/libxklavier/libxklavier/xklavier_config.c?annotate=1.26&pathrev=v_3_00), I can see: 264 : if (nodes != NULL && nodes->nodeTab != NULL) { 265 : svu 1.22 rv = xkl_read_config_item(config, *nodes->nodeTab, pitem); It seems *nodes->nodeTab is NULL (I'll check libxml API whether it is correct or not). Could you please check one small fix: change line 264 to if (nodes != NULL && nodes->nodeTab != NULL && *nodes->nodeTab != NULL) {
Or even better: if (nodes != NULL && nodes->nodeTab != NULL && nodes->nodeNr > 0) {
*** Bug 368055 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > What is your XKB configuration? Could you please do > xprop -root | grep XKB > and > gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd Here are the results. ------------- $ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us", "dvorak", "" _XKB_RULES_NAMES(STRING) = "xorg", "pc105", "dvorak,us", ",", "grp:shifts_toggle,lv3:switch,grp_led:scroll,compose:ralt,eurosign:e" $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [dvorak,us] model = options = [grp grp:shifts_toggle,lv3 lv3:switch,grp_led grp_led:scroll,Compose key compose:ralt,eurosign eurosign:e] overrideSettings = true ------------- If I'm needed to try out the 'fix' in libxklavier, I'll need to acquire the appropriate expertise to do so. Alternatively, if somebody can spin a libxklavier rpm with the update you suggested I would be glad try it out immediately.
Here is my results [michel@localhost ~]$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "ca(fr)", "", "" _XKB_RULES_NAMES(STRING) = "xorg", "pc105", "ca(fr)", "", "" [michel@localhost ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [] model = overrideSettings = true options = [] [michel@localhost ~]$ I have not rebooted yet so this is still after the crash. I know that after I reboot the keyboard will be messed up again. I only get the right keyboard after the keyboard setup crashes. Michel Catudal
My results are: [jshadow@traveler ~]$ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us,ru(winkeys)", "", "grp:ctrl_shift_toggle,grp_led:scroll" _XKB_RULES_NAMES(STRING) = "xorg", "pc104", "us,ru(winkeys)", ",", "grp:ctrl_shift_toggle,grp_led:scroll" [jshadow@traveler ~]$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = us,ru(winkeys) model = pc104 overrideSettings = true options = (no value set) I don't have the knowlege of linux programming yet, so I am afraid I won't be able to track the problem myself, however I will be trying. Meanwhile, I will be happy to try the binary compiled by someone else.
*** Bug 351395 has been marked as a duplicate of this bug. ***
Since I do not have Fedora I'm afraid I would not be able to help you with RPM... Thanks for information though lads - I'll try to reproduce your problem (with unfixed code). But I'd really appreciate if anyone with that problem would be able to try this fix.
*** Bug 370025 has been marked as a duplicate of this bug. ***
Sergey- Your patch works perfectly. After making the change to xklavier_config.c you suggest above and recompiling, the keyboard indicator applet works perfectly for switching between two keyboards. Thanks! PS: I have the source rpms which I can send to people or post somewhere if there is interest.
(In reply to comment #12) > Sergey- > > Your patch works perfectly. After making the change to xklavier_config.c you > suggest above and recompiling, the keyboard indicator applet works perfectly > for switching between two keyboards. Thanks! > > PS: I have the source rpms which I can send to people or post somewhere if > there is interest. > I would be interested in the patch. Michel
Sergey, I've applied your patch - it worked perfectly for me. gnome-keyboard-properties applet is now working. Thanks! I am looking forward for this fixed libxklavier to appear at Fedora Core updates.
Okay, I uploaded the patched SRC RPM to my web server. Please be gentle! http://www.jandr.org/libxklavier-3.0-2.src.rpm Instructions: To build a binary RPM, you need to run: rpmbuild --rebuild libxklavier-3.0-2.src.rpm You will probably need to install a few devel packages to get this to work, hopefully the messages will be self explanatory. When it finishes, you will see something printed like this: Wrote: /usr/src/redhat/RPMS/i386/libxklavier-3.0-2.i386.rpm To install the binary, run this command: rpm -Uvh /usr/src/redhat/RPMS/i386/libxklavier-3.0-2.i386.rpm
Oh, one other thing. After updating, you need to log out and confirm that all the gnome processes that use libxkavier are no longer running. (I had a locked up gnome-keyboard-preferences running that I had to manually kill). Then log into gnome again.
(In reply to comment #15) > Okay, I uploaded the patched SRC RPM to my web server. Please be gentle! > http://www.jandr.org/libxklavier-3.0-2.src.rpm Thanks Jon for the src rpm & the instructions!! Sergey, I verified that Jon's rpm with your patch fixes my original problem of gnome-keyboard-properties crashing. It has also fixed Bug 370025 which I had encountered earlier (and which is now dup'ed to this). Thanks so much all.
*** Bug 370589 has been marked as a duplicate of this bug. ***
Jon, thank you very much for the src rpm! I've created binary RPMs for x86_64 if somebody needs them.
I think now we can close this one. Feel free to reopen if same stack trace happens to you again...
*** Bug 370959 has been marked as a duplicate of this bug. ***
*** Bug 370993 has been marked as a duplicate of this bug. ***
*** Bug 371058 has been marked as a duplicate of this bug. ***
*** Bug 371137 has been marked as a duplicate of this bug. ***
FYI: An updated libxklavier rpm for fc6 is in updates-testing.
Thank you, Matthias!
sergey, is bug 369256 a duplicate?
*** Bug 369256 has been marked as a duplicate of this bug. ***
*** Bug 371528 has been marked as a duplicate of this bug. ***
*** Bug 372085 has been marked as a duplicate of this bug. ***
*** Bug 372146 has been marked as a duplicate of this bug. ***
*** Bug 372217 has been marked as a duplicate of this bug. ***
*** Bug 372238 has been marked as a duplicate of this bug. ***
*** Bug 372421 has been marked as a duplicate of this bug. ***
*** Bug 372472 has been marked as a duplicate of this bug. ***
*** Bug 372576 has been marked as a duplicate of this bug. ***
*** Bug 372606 has been marked as a duplicate of this bug. ***
*** Bug 372991 has been marked as a duplicate of this bug. ***
*** Bug 370547 has been marked as a duplicate of this bug. ***
*** Bug 377035 has been marked as a duplicate of this bug. ***
*** Bug 379833 has been marked as a duplicate of this bug. ***
bug 382146 could be another duplicate
*** Bug 395929 has been marked as a duplicate of this bug. ***
*** Bug 398807 has been marked as a duplicate of this bug. ***
*** Bug 405402 has been marked as a duplicate of this bug. ***
*** Bug 408043 has been marked as a duplicate of this bug. ***
*** Bug 408166 has been marked as a duplicate of this bug. ***
*** Bug 408435 has been marked as a duplicate of this bug. ***
*** Bug 408555 has been marked as a duplicate of this bug. ***
*** Bug 410382 has been marked as a duplicate of this bug. ***
*** Bug 423858 has been marked as a duplicate of this bug. ***
*** Bug 420956 has been marked as a duplicate of this bug. ***
*** Bug 428961 has been marked as a duplicate of this bug. ***
*** Bug 430968 has been marked as a duplicate of this bug. ***