GNOME Bugzilla – Bug 368055
crash in Keyboard: J'ai accidentellement ch...
Last modified: 2007-02-01 20:15:32 UTC
Version: 2.16.0 What were you doing when the application crashed? J'ai accidentellement changé à Azerty et ai écrit quelque chose dans jstar dans un terminal. Ne connaissant pas ce clavier merdique j'ai fait un kill du terminal car il était impossible de sortir de jstar. ctrl K Q ne fonctionne pas avec ce clavier de cul. J'ai tenté de modifier le clavier cette fois avec le logiciel de gnome pour clavier. Il a alors planté. J'ai reloadé le clavier ca via l'autre logiciel qui me demande le mot de passe. J'ai réessayé le setup de gnome qui a à nouveau planté. Ce qui est amusant est que maintenant le clavier est correct. Le fait que le logiciel de gnome ait planté semble avoir réparé temporairement le bug qui fait que le clavier CF n'est pas du tout converti correctement. Probablement que quand je rebouterai je devrai faire planter ce logiciel à nouveau pour que le clavier fonctionne correctement. J'ai regardé la source et le fichier est correct mais il semble impossible de choisir (fr) qui est le clavier CF. Il est choisit seulement quand le logiciel plante. Bizarre!! Les seuls choix dans le menu sont les claviers soit disant multilingue, Dvorak et le soit disant traditionnel qui est en fait le clavier de con qu'on retrouve sur windows XP et qui n'est pas du tout le clavier traditionnel connu sous le terme CF. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 Memory status: size: 26255360 vsize: 0 resident: 26255360 share: 0 rss: 11575296 rss_rlim: 0 CPU usage: start_time: 1162263072 rtime: 0 utime: 9 stime: 0 cutime:9 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 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) [Thread debugging using libthread_db enabled] [New Thread -1208145072 (LWP 4733)] (no debugging symbols found) 0x00258402 in __kernel_vsyscall ()
+ Trace 80777
Thread 1 (Thread -1208145072 (LWP 4733))
I'm sorry, I do not understand French at all. Could you please provide your comments in English (or Russian, since I know it:)?
*** Bug 368257 has been marked as a duplicate of this bug. ***
"changing the keyboard layout" according to the duplicate. confirming.
(In reply to comment #1) > I'm sorry, I do not understand French at all. Could you please provide your > comments in English (or Russian, since I know it:)? > I installed Fedora Core 6 and chose the French Canadian Keyboard. I then found out that the keyboard that I wanted was not picked up correctly and it turned out that the keyboard looks just like the one that Microsoft thinks is the French Canadian keyboard. In other words a garbage keyboard. For example on the left below the escape key it is supposed to be |#\ but has ° instead. Over the 3 it has # instead of /. It is kind of a problem to type directories that way. On XP I have to switch to the multilingual keyboard to resolve the issues and get stuck with a keyboard that doesn't reflect the layout. Most of the dead keys don't work on that keyboard. I don't want this problem on Linux. As to what prompted the response in French. After the keyboard program from gnome crashed for the second time I responded to the question which was in French. The keyboard crashed after I switched to an azerty keyboard and killed jstar which I had opened in a terminal. It crashed when I ran the gnome keyboard setup program, not the one that asked for a password which was the one I used to change to azerty. I didn't realize I had picked that crappy keyboard until I notice that I was trapped in jstar with no way of quitting as it would not respond to ctrl kq. After the crash I switched the keyboard back to ca using the program that asks for a password. When I ran the gnome program it crashed. After loading gedit I realized that the crash fixed my keyboard. It is now perfect. The good keyboard is not in the gnome list. It looks like it picked the right keyboard which happens to be the first before it crashed. If I reboot I will likely lose my keyboard setting again. I looked at the code for the gnome keyboard config and the correct keyboard is there. It should be the exact same as the command line CF keyboard not some garbage microsoft keyboard. I am not sure where microsoft digged that keyboard but I have never seen a keyboard that reflects that layout. Michel (An Anerican from South Michigan) P.S. I don't speak Russian, only French and English.
The 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. Would be great if someone could 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 for any efforts!
*** Bug 367093 has been marked as a duplicate of this bug. ***
*** Bug 368381 has been marked as a duplicate of this bug. ***
*** Bug 368902 has been marked as a duplicate of this bug. ***
Michel, actually your bug consists of two parts: wrong layout and the crash itself. Regarding the layout, it is typical NOTGNOME. If you are not happy with the layouts, you're better off filing bugs in bugzilla.gnome.org against xkeyboard-config. Regarding the crash, as Andre already informed, the stack trace is not particularly useful.
*** Bug 369196 has been marked as a duplicate of this bug. ***
*** Bug 369309 has been marked as a duplicate of this bug. ***
*** Bug 370123 has been marked as a duplicate of this bug. ***
*** Bug 368517 has been marked as a duplicate of this bug. ***
*** Bug 370136 has been marked as a duplicate of this bug. ***
I've installed libxklavier-debuginfo-3.0-1.fc6.x86_64, reprodiced the bug and created a stack trace. For me the bug is occuring every time I start gnome-keyboard-config applet. At first the applet was working fine, but after I pressed "Reset to detaults" button it crashed for the very first time. --- Backtrace was generated from '/usr/bin/gnome-keyboard-properties' (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) (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 46912496316352 (LWP 3723)] 0x0000003107c0d935 in waitpid () from /lib64/libpthread.so.0
+ Trace 82551
Thread 1 (Thread 46912496316352 (LWP 3723))
Hurray! I know what it is. See #370038 *** This bug has been marked as a duplicate of 370038 ***
*** Bug 381221 has been marked as a duplicate of this bug. ***
*** Bug 384696 has been marked as a duplicate of this bug. ***
*** Bug 397849 has been marked as a duplicate of this bug. ***
*** Bug 397851 has been marked as a duplicate of this bug. ***
*** Bug 403092 has been marked as a duplicate of this bug. ***