Gnome Keyboard Indicator Problem...

Hi,
I have installed gnome on my laptop and the gnome keyboard indicator to change between usa and greece in languages. I have se the combination alt-shift and everything works when pressing alt-shift the change happens and I can switch between greek and english to write.
The problem is that the indicator constantly shows USA on the gnome panel and does not follow the switching as it is supposed to.
Is it a bug or something?

Romashka wrote:
Gnome 2.16.2 is out.
This bug is fixed!
- Fixed keyboard indicator segfault (Sergey UDaltsov) (351395)
Oh, this fixed bug is another one.
Bug 355074 is still not fixed.

Similar Messages

Removing Gnome 2.30's keyboard indicator

Hi.
I've just upgraded to Gnome 2.30 and now there always is this annoying keyboard layout indicator in the tray. I use two layouts between which I switch using a keyboard shortcut. I can't find a way to remove the indicator and it's really getting on my nerves. As much as I like Gnome, presenting a tray icon to the user with no apparent way to remove it is not really user-friendly Does anyone have an idea how to get rid of it?
Thanks!

Quoting the Gnome 2.30 release notes:
The GNOME Keyboard Indicator has been removed from GNOME Applets. If you use more than one keyboard layout, the GNOME Keyboard Indicator will now automatically appear in your tray via gnome-system-daemon.

Arch Gnome - no keyboard indicator

Hi,
Tried to search over the forum and Google but I have not come with a solution. My problem is:
I have no keyboard indicator in the desktop,nor the login screen. I CAN however change languages without a problem. it's just that I cannot "see" on which language I am on...
It is a fresh installation with a minimal Gnome, so I assume I have missed a package.
Any ideas if I missed a package or just missed some configuration?
Thanks,

Romashka wrote:
Gnome 2.16.2 is out.
This bug is fixed!
- Fixed keyboard indicator segfault (Sergey UDaltsov) (351395)
Oh, this fixed bug is another one.
Bug 355074 is still not fixed.

Keyboard layout problems in Gnome

I'm not sure if it was a recent upgrade that did it or not, but in gnome my keyboard layout is only half right. I checked the keyboard manager in the gnome menu and it was set to Generic 105 key (INTEL).
In xorg.conf the keyboard is listed as pc105. In KDE the keyboard works normally.

bgodea wrote:I changed the Gnome keyboard layout to "104 key PC" and also tried changing my xorg.conf, but I still have the same problem. In non-graphical and KDE it works fine
You also have to setup a valid layout for this kind of keyboard. That is done in the same dialog field. Then, what do you mean with "tried"? First off, if Gnome and X disagree about keyboard layout, Gnome complains loudly. Thus KDE is unilaterally setting the layout to something it likes. Check your Kconfig to find out what it is. Then find the section named InputDevice in /etc/X11/xorg.conf that looks something like this:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
EndSection
Change it to resemble this example, if it doesn't. Check if your ServerLayout actually uses this InputDevice. Finally, is there anything else we should know about your keyboard? Do you run XGL/AIGLX?
Last edited by Captain Spaulding (2007-04-03 16:50:46)

Gnome Keyboard Properties invalid pointer

I keep getting
*** glibc detected *** free(): invalid pointer: 0xb74ae9a0 ***
everytime I try to run gnome-keyboard-properties.
On a side note, the weather report applet seems to only list North America and the Middle East as possible locations, and it seems that Alaska is the only state in the US.
Anyone else have these problems or is it only occuring on my computers?

I updated gnome-applets, so the weather applet should work indeed
The gnome-keyboard-properties thingy was a bug in libxklavier 1.0.4 which returns a static declared variable as a pointer, which breaks with the new glibc. Fixed that with a patch kindly grabbed from gentoo CVS

E70 Keyboard layout problems

I have a brand-new E70 bought from Expansys a week ago. I have the same problem reported by other here regarding incorrect keyboard layout (e.g. "(" key produces ")" and "/" produces ","). I have not upgraded the firmware, this is the way the phone was shipped.
I haven't found any solution in this forum or on the web yet. Any advice is appreciated. Thanks,
-- Terrence

bgodea wrote:I changed the Gnome keyboard layout to "104 key PC" and also tried changing my xorg.conf, but I still have the same problem. In non-graphical and KDE it works fine
You also have to setup a valid layout for this kind of keyboard. That is done in the same dialog field. Then, what do you mean with "tried"? First off, if Gnome and X disagree about keyboard layout, Gnome complains loudly. Thus KDE is unilaterally setting the layout to something it likes. Check your Kconfig to find out what it is. Then find the section named InputDevice in /etc/X11/xorg.conf that looks something like this:
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbLayout" "us"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
EndSection
Change it to resemble this example, if it doesn't. Check if your ServerLayout actually uses this InputDevice. Finally, is there anything else we should know about your keyboard? Do you run XGL/AIGLX?
Last edited by Captain Spaulding (2007-04-03 16:50:46)

Gnome 3::Touchpad problem

Hi,
I have a problem with gnome3. I have a new laptop Lenovo Thinkpad L420 (Intel Core
i5-2410M + Intel HD 3000) with OS Archlinux 64-bit + Gnome3.
When I disable touchpad, touchpad is off and I enable touchpad, touchpad is
still disable::touchpad toggle (Fn+F8). When I switch to some tty (Ctrl + Alt + F1-F6) and
back to Xserver (Ctrl + Alt + F7), so touchpad works.
And touchpad in gnome 2 works normally.
What can I do with this problem? Sorry for my bad english. Thanks for your help!

You should post some logs. Give us an output of "dmesg | tail" when this happen.
I have done bellow to get a working switch for my touchpad in X environment. This is a WORKAROUND not a solution to your problem. First of all type:
xinput list
You will see your touchpad. My touchpad is:
ETPS/2 Elantech Touchpad
I will use my touchpad as an example.
Now copy this text to blank file and make it executable:
#!/bin/bash
if
xinput --list-props "ETPS/2 Elantech Touchpad" | grep "Synaptics Off" | grep 1
then
xinput --set-prop 'ETPS/2 Elantech Touchpad' 'Synaptics Off' 0
else
xinput --set-prop 'ETPS/2 Elantech Touchpad' 'Synaptics Off' 1
fi
Again, my touchpad is examplary you have too put yours in.
Now you can use this script through gnome keyboard shortcut application and assign key combination.
Last edited by Shark (2011-08-23 13:35:06)

Qosmio Dx730 - virtual keyboard indicator issue

I have a Toshiba Qosmio Dx730.
I am not using the supplied wireless keyboard, but a standard D+ll wired keyboard as I prefer the keyboard layout.
However the keyboard indicator for the virtual keyboard is malfunctioning, and appears in the bottom left of the screen randomly (regardless of whether I hit caps lock or not).
It has now begun to randomly switch Caps Lock on and off, for no apparent reason.
Can I switch the keyboard indicator off somehow?
I never use the virtual keyboard, so I would be happy for that to be turned off as well.
Thanks for any assistance!
Lyn

Hi Joe, thanks for your reply.
I understand the function of the keyboard indicator and I think the problem that caused me to submit the previous post was due to my keyboard malfunctioning (embarassingly - grit under the caps lock key, causing the keyboard indicator to flash on and off randomly and switch to caps on)
However, as I am using a wired keyboard with its own keyboard indicators, (that is, *not* the wireless keyboard supplied with the PC) I would like to permanently switch off the virtual keyboard indicator.
Currently, even though I hide the keyboard indicator, it redisplays every time I hit the caps lock key, often in the middle of the screen.
Is there any way to permanently hide or switch off the virtual keyboard indicator?
Thanks again for any assistance,
Lyn

Gnome-keyboard-applet uses wrong background color

gnome-keyboard-applet always uses white color as a background, even when panel's color is not white.
(Or, maybe, not exactly white, but it's clearly different from panel's color)
WTF?

It seems that this is the problem with theme. I'm using gnome-human-theme from AUR.
With other murrine themes it's OK. Does somebody know where in gtkrc is the color value, which is responsible for that?

A possible solution for "foreight language keyboard shortcut" problem...

Hi(Bonjour)!
Everyone know the problem of losy keyboard layout when Final Cut is used with foreight language keyboard. We loose the COMMAND-Q shorcut.
As PieroF suggested in many posts in final cut express forum, there is a workaround:
"+I just installed Leopard and I ran into this keyboard shortcut problem.+
+I can confirm that:+
+a. the problem exists also with the Italian keyboard (in addition to other languages, as pointed by other posters)+
+b. the workaround I described in my previous answer works fine :+
+- close FCE (if open)+
+- open System Preferences/International/Language+
+- drag English to the first place on top of the other languages+
+- drag your own language (Italian in my case) again on top of English (at the end the window will show the same original settings, but something happened in the heart of Leopard...)+
+- close System Preferences+
+- open FCE: now all shortcuts work as expected, and are correctly listed with their corresponding menu commands+
+It's a workaround, it's not convenient (I'd better have this bug fixed), but apparently you have to apply it only once for each system startup.+
Piero "
As stated by Piero, you have to follow this procedure after each computer startup.
I found a way to restore the COMMAND-Q shortcut with the keyboard and mouse system pref panel.
Simply add Final Cut application and add a +custom shotcut+. Be careful to type exactly the "Quit Final Cut Express" menu.
This solution allows to restart the computer.
It's work with Final Cut Express and Final Cut Pro under Leopard 10.5.4.
Michel Boissonneault

Hi Michel,
I like your suggestion because the keyboard shortcuts defined in the system preferences do not require redefinition at each startup. So in theory we could define all missing/wrong shortcuts this way, and not only the cmd-Q as you suggested. Boring, but we could do it once for all.
The only problem is that I don't know how to define shortcuts for submenus, for example "Render Selection/Both": it seems system preferences allows only to define shortcuts for the menu ("Render Selection" - in this case absolutely useless) but not for the submenu.
Do you know a way ? (I looked in the help, which didn't... help).
Piero

Weird dreamweaver keyboard mapping problem

weird dreamweaver keyboard mapping problem:
Hope this solution helps someone out. If you have q's, ask
and I will try to help.
I was having a weird problem in dreamweaver... Whenever I was
in code view and typed "shift+i" to make a capital "I", instead it
would paste from the clipboard.
I finally figured out what was happening. I compared the
menu.xml in my app support folder in the user library to the
original menu.xml file that was in the application folder. I went
through until I came across the diff:
menu.xml in my library/app support folder:

<shortcut key="Cmd+Ins" name="Copy2" platform=""
command="if (dw.canClipCopy()) { dw.clipCopy() }"
domRequired="FALSE" id="DWShortcuts_HTMLSource_Copy2" />
<shortcut key="Shift+Ins" name="Paste2" platform=""
command="if (dw.canClipPaste()) { dw.clipPaste() }"
domRequired="FALSE" id="DWShortcuts_HTMLSource_Paste2" />
<shortcut key="Shift+Del" name="Cut2" platform=""
command="if (dw.canClipCut()) { dw.clipCut() }" domRequired="FALSE"
id="DWShortcuts_HTMLSource_Cut2" />
orig menu.xml file:

<shortcut key="Cmd+Ins" name="Copy2" platform=""
command="if (dw.canClipCopy()) { dw.clipCopy() }"
domRequired="FALSE" id="DWShortcuts_HTMLSource_Copy2" />
<shortcut key="Shift+Ins" name="Paste2" platform=""
command="if (dw.canClipPaste()) { dw.clipPaste() }"
domRequired="FALSE" id="DWShortcuts_HTMLSource_Paste2" />
<shortcut key="Shift+Del" name="Cut2" platform=""
command="if (dw.canClipCut()) { dw.clipCut() }" domRequired="FALSE"
id="DWShortcuts_HTMLSource_Cut2" />
There was a diff in the "platform=" tags. The orig stated
[platform="win"], my config stated [platform=""] (nothing in
between the ""'s). So, I reset the platform tag to be
[platform="win"] in my settings and then relaunched dreamweaver. It
fixed the problem.
Not sure how this occurred, but it works now.

Calling1.4.1 signed applet from Javascript causes keyboard/focus problems

Pretty sure there's a JRE bug here, but I'm posting to forums before I open one in case I'm missing something obvious :-)
This issue may be specific to IE, I haven't tested elsewhere yet. Our web application is centered around a signed applet that is initialized with XML data via Javascript. We first noticed the problem when our users started upgrading from the 1.3.x plug-in to the 1.4.x plug-in. The major symptom was that shortcut keys stopped working. I debugged the problem off and on for about a month before I boiled it down to a very simple program that demonstrates the issue (included below). Basically, the program has a function that adds a JButton to a JPanel and registers a keyboard listener (using the new DefaultKeyboardFocusManager class) that prints a message to the console. This function is called by the applet's init() method, as well as by a public method that can be called from Javascript (called callMeFromJavascript()). I also included a very simple HTML file that provides a button that calls the callMeFromJavascript() method. You can test this out yourself: To recreate, compile the class below, JAR it up, sign the JAR, and put in the same dir with the HTML file. Load the HTML file in IE 5.0 or greater, and bring the console up in a window right next to it. Now click the button that says init--you should see the small box appear inside the button that indicates it has the focus. Now press some keys on your keyboard. You should see "KEY PRESSED!!!" appearing in the console. This is proper behavior. Now click the Init Applet from Javascript button. It has removed the button called init, and added one called "javascript". Press this button. Notice there is no focus occurring. Now press your keyboard. No keyboard events are registered.
Where is gets interesting is that if you go back and make this an unsigned applet, and try it again, everything works fine. This bug only occurs if the applet is signed.
Furthermore, if you try it in 1.3, signed or unsigned, it also works. So this is almost certainly a 1.4 bug.
Anyone disagree? Better yet, anyone have a workaround? I've tried everything I could think of, including launching a thread from the init() method that sets up the components, and then just waits for the data to be set by Javascript. But it seems that ANY communication between the method called by Javascript and the code originating in init() corrupts something and we don't get keyboard events. This bug is killing my users who are very reliant on their shortcut keys for productivity, and we have a somewhat unique user interface that relies on Javascript for initialization. Any help or suggestions are appreciated.
================================================================
Java Applet (Put it in a signed JAR called mainapplet.jar)
================================================================
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
public class MainApplet extends JApplet implements KeyEventDispatcher
    JPanel test;
    public void init()
        System.out.println("init called");
        setUp("init");
    public void callMeFromJavascript()
        System.out.println("callMeFromJavascript called");
        setUp("javascript");
    private void setUp(String label)
        getContentPane().removeAll();
        test = new JPanel();
        getContentPane().add( test );
        JButton button = new JButton(label);
        test.add( button );
        test.updateUI();
        DefaultKeyboardFocusManager.getCurrentKeyboardFocusManager().addKeyEventDispatcher(this);
    public boolean dispatchKeyEvent(KeyEvent e)
        System.out.println("== KEY PRESSED!!! ==");
        return false;
}================================================================
HTML
================================================================
<form>
<APPLET code="MainApplet" archive="mainapplet.jar" align="baseline" id="blah"
     width="200" height="400">
     No Java 2 SDK, Standard Edition v 1.4.1 support for APPLET!!
</APPLET>
<p>
<input type="button" onClick="document.blah.callMeFromJavascript();" value="Init Applet via Javascript">
</form>

I tried adding the requestFocus() line you suggested... Same behavior.
A good thought, but as I mention in my description, the applet has no trouble gaining the focus initially (when init() is called). From what I have seen, it is only when the call stack has been touched by Javascript that I see problems. This is strange though: Your post gave me the idea of popping the whole panel into a JFrame... I tried it, and the keyboard/focus problem went away! It seems to happen only when the component hierarchy is descended from the JApplet's content pane. So that adds yet another variable: JRE 1.4 + Signed + Javascript + components descended from JApplet content pane.
And yes, signed or unsigned DOES seem to make a difference. Don't ask me to explain why, but I have run this little applet through quite a few single variable tests (change one variable and see what happens). The same JAR that can't receive keyboard events when signed, works just fine unsigned. Trust me, I'm just as baffled as you are.

Which part of the machine is related to the keyboard flex problem ?

Mine is T420s
And I got a keyboard flex problem.
Actually which part is related to this problem ?
Isn't it inclusive to fix this problem in the warranty ?
thx

Mine doesn't exhibit any keyboard flex and I don't think it's a common issue with T420s; anyway:
http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T420s-Keyboard-Flex/td-p/454851/highlight/t...
http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/t420s-keyboard-flex/m-p/755255/highlight/tr...
T420s i5-2520M HD3000 480GB Crucial M500 SSD 8GB RAM Ericsson F5521gw
T430 i5-3210M HD4000/NVIDIA 5400M 512GB Crucial MX100 SSD 12GB RAM Ericsson H5321gw

(foreign) keyboard mapping problems

Many people, myself included, have voiced problems with keyboard mappings since updating to Leopard. It appears to particularly afflict people with non-US keyboards, but I may be wrong.
Does anybody out there have a generic fix? Manually modifying the keyboard map as the Latvians did seems to address (some of) the symptoms, not the underlying problem. Accordingly, it doesn't appear to be a general fix, as reported here:
http://m10lmac.blogspot.com/2007/10/fixing-leopards-latvian-keyboard.html
Here are some of the other posts I saw/wrote that make me think this is a SIGNIFICANT PROBLEM IN LEOPARD:
http://discussions.apple.com/thread.jspa?messageID=5794935&#5794935
http://discussions.apple.com/thread.jspa?messageID=5644709&#5644709
http://discussions.apple.com/message.jspa?messageID=5688731#5688731
http://discussions.apple.com/thread.jspa?messageID=5854794
http://discussions.apple.com/thread.jspa?messageID=5788789

Does anybody out there have a generic fix?
There is no generic fix because the problems are unrelated, except to the extent they represent goofs in creating certain files and failure to find these before release.
The Latvian keyboard issue is caused by errors in a particular .keylayout file. I don't know of any other similar layout with the same problem (In Tiger it was Macedonian and Romanian which had such errors). The Hanin Chinese IM problem is caused by errors in a couple of files particular to it -- all the other Chinese input systems have correct mappings. The X11 keyboard mapping problem concerns a different part of OS X than the others. The issues of QWERTY/AZERTY/QWERTZ in Chinese input were present in a different fashion in Tiger and earlier and many people have switched to a different IM called QIM to solve it. Having a dead Apple key is not related to ordinary character mapping issues.
Your own issue with ViaVoice is not totally clear to me, will try to respond in that thread.

Gnome-keyboard-shortcut issue

Hi,
I've configured keyboard shortcuts in gnome-keyboard-shortcuts to launch firefox, evolution. They work fine when i configure them, however after a xorg restart they act wierd.... I have to press the button several time before it opens..
for example, i press the firefox key.. and start doing ps -ef | grep firefox but nothing...
after pressing the button 4 times (interval of 10 seconds in between) firefox finally opens.
same deal with evolution and rhythmbox.
its not that my system is slow because if i click on the icon it opens up in 1 second.
I just dont know how i should diagnose this. Thanks for the help

same issue here for another user in ubuntu
http://ubuntuforums.org/showthread.php?t=629990

Gnome Keyboard Indicator Problem...

Similar Messages

Maybe you are looking for