GNOME Bugzilla – Bug 311685
gnome-keyboard-properties crashes when adding new layout
Last modified: 2005-08-15 02:25:58 UTC
Distribution: Fedora Core release 4 (Stentz) Package: control-center Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: gnome-keyboard-properties crashes when adding new layout Bugzilla-Product: control-center Bugzilla-Component: keyboard Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Steps to reproduce the crash: 1. Start gnome-keyboard-properties 2. Try to add a new layout 3. crash Expected Results: success How often does this happen? every time Additional Information: if started on the commandline, the following error is emitted: ** (gnome-keyboard-properties:3966): WARNING **: key AE00: keycode = 4294967295; not in range 8..255 Debugging Information: Backtrace was generated from '/usr/bin/gnome-keyboard-properties' (no debugging symbols found) Using host libthread_db library "/lib/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) (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) [Thread debugging using libthread_db enabled] [New Thread -1208875328 (LWP 3890)] (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) 0x00935402 in ?? ()
+ Trace 62009
Thread 1 (Thread -1208875328 (LWP 3890))
------- Bug moved to this database by unknown@gnome.bugs 2005-07-27 07:53 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was enpontus@home.se.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see [WWW]http://live.gnome.org/GettingTraces for more information on how to do so.
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 -1208195392 (LWP 5650)] 0x00bfd402 in ?? ()
+ Trace 62424
Thread 1 (Thread -1208195392 (LWP 5650))
was this better ?
Well, it makes some sense now. It crashes in libkbdraw somehow. What we could do is to reproduce the situation, if possible, in 2.10 branch of g-c-c. What is the layout you were looking at? what is the keyboard model? Any layout options?
i had swedish layout and was trying to switch to swedish dvorak setting - but i have tried with empty setting and other settings as well, keyboard is a Microsoft Natural Keyboard Pro / Microsoft Internet Keyboard Pro. At one occasion though i managed to get another layout added besides the (normal) swedish layout, at that point i could without problems add the Dvorak layout. However at about 50% of the occasions the program crashes when i press the Add button (i.e. before choosing next layout) and the rest when clicking on the selected (new) layout. could it be that the (Normal) Swedish layout is somewhat flawed in combination with this keyboart type ?
yess! It seems I can reproduce it. Investigating the issue...
I fixed it in CVS. It was a very odd bug in libkbdraw. Thanks for giving me reproducable configuration.