No "@" in German keyboard, applett crashing when Turkey keyboards present

[Erdal Ronahi]

Binary package hint: kbd-chooser

In the standard German keyboard configuration, the "@" key has disappeared. I have this problem on two different computers both running Edgy.

The problem may be related to the fact that I use also Turkey keyboard configurations like "Alt Q" and "Kurdish, Latin Q". But even after removing them from the configuration, the "@" is still not there.

Also, if I try to add the keyboard applett to the panel, it crashes. I'll attach the bug-buddy output. However, these crashes can be circumvented by removing the Turkey keyboards.

[Erdal Ronahi (erdalronahi)]

This does not only affect the @, but all characters that need AltGR like ~, \, | and so on.

[Sergey V. Udaltsov (sergey-udaltsov)]

Erdal, could you please install dbg package so the stack trace would contain the line numbers? Thanks.

[Erdal Ronahi (erdalronahi)]

Sure, which dbg-package? Libxkbfile1-dbg?

[Erdal Ronahi (erdalronahi)]

Hi, I spotted out the problem: I had assigned the same key (right alt) to level switcher and compose key. So it was my fault.

BUT

1. I should have been warned that I should not assign two tasks to one key
2. This fault should not crash my GNOME-panel

[Timo Aaltonen (tjaalton)]

reassing to gnome-applets

(and it's gnome-applets-dbg you need in order to get a better stacktrace)

[Timo Aaltonen (tjaalton)]

oh, I reassigned to gnome-applets because of the crash. You could open a different bug about the fact that you should be warned if you try something silly.

[Sebastien Bacher (seb128)]

Upstream bug with a similar backtrace: http://bugzilla.gnome.org/show_bug.cgi?id=375461

[Daniel Holbach (dholbach)]

Upstream asks:

Which version of gnome-applets and libxklavier do you use? Could you please try
the latest versions? I think it was fixed... Also, I would appreciate more
debugging information - this stack trace does not contain the line numbers.

[Daniel Holbach (dholbach)]

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.