Unable to make hotkey for launchy..

[OleWilly]

Hi

Every time I choose another key combination in launchy I get this:

The hotkey you have chosen is already in use. Please select another from Launchy's preferences.

I am using PCLinuxOS 2010 with Gnome desktop.

And if I start launchy from a terminal I get this:

[ole@localhost ~]$ launchy
/usr/share/themes/Darklooks/gtk-2.0/gtkrc:181: Invalid symbolic color 'tooltip_bg_color'
/usr/share/themes/Darklooks/gtk-2.0/gtkrc:181: error: invalid identifier `tooltip_bg_color', expected valid identifier
failed to grab key
failed to grab key
failed to grab key
failed to grab key

OW 

[djohnston]

Hi

Every time I choose another key combination in launchy I get this:

The hotkey you have chosen is already in use. Please select another from Launchy's preferences.

I am using PCLinuxOS 2010 with Gnome desktop.

And if I start launchy from a terminal I get this:

[ole@localhost ~]$ launchy
/usr/share/themes/Darklooks/gtk-2.0/gtkrc:181: Invalid symbolic color 'tooltip_bg_color'
/usr/share/themes/Darklooks/gtk-2.0/gtkrc:181: error: invalid identifier `tooltip_bg_color', expected valid identifier
failed to grab key
failed to grab key
failed to grab key
failed to grab key

OW  

Since you are running the Gnome edition, you will probably get more responses at the PCLOS Gnome site:

http://linuxgator.org/forums/index.php

I did a quick search on the home page for "failed to grab key", but got only one hit, which doesn't seem to apply.

I use PCLOS e17 and PCLOS LXDE on different computers, but I get some weird gtk2 errors with some fairly generic programs. In your case, it looks like the error is being caused by an installed theme, Darklooks, that gtkrc is having issues with. gtkrc is a theme engine. There are 3 overriding configuration files for gtkrc-driven themes, but the only one you should be concerned with is:

/home/(your-username)/.gtkrc-2.0

The file is only a few lines, but I don't know enough about the configuration to make any recommendations. Mine looks like this:

Code: [Select]

# This file was written by PCLinuxOS
include "/usr/share/themes/Oxygen-Molecule/gtk-2.0/gtkrc"
style "user-font"
{
} widget_class "*" style "user-font"
gtk-theme-name="Oxygen-Molecule"
gtk-font-name="DejaVu Sans 10"
EDIT: If you are using the Darklooks theme, try switching to another theme. Try one of the generic ones. If that doesn't work, then you might try this: see if you have a Darklooks theme installed, see if you can live without said theme, then see if deleting the theme solves the problem. If deleting or uninstalling the theme will uninstall additional packages, then STOP and DO NOT do it.

[OleWilly]

Hi djohnston

Thank You for the reply. I have transferred my question to the Gnome forum. Before I did that I altered my theme to the default theme. When I did that I could not start launchy at all. Whether I tried from the menu or in a terminal. Exiting.

OW 

[djohnston]

olewilly,

I saw you marked this one as solved on the Gnome forum. How did you do it? Did an update correct the problem?

[longtom]

I tried to help somebody with a similar problem in the Gnome Forum.  If I was successful I don't know - never heard of him/her again.

Anyway - for the sake of completeness here it is as well:

While I - like everybody else - don't have a solution to the problem, I do have a neat workaround, which does the job. Here it goes:

- Open your run command (alt + F2):

- Type "gconf-editor"

- In gconf-editor go to apps > metacity > keybinding_commands

- in the right window right click on any of the unused commands and select "edit key"

- At "value" type your command. ( for example if you need a shortcut to open nautilus type "nautilus")

- On the left hand tab go to "global_keybindings"

- in the right tab use your run_command corresponding to your command you defined earlier.

- right click click on your "run command" and choose "edit key"

- fill in your desired keyboard shortcut using the same syntax as the other shortcuts you see there.

- click "ok and you are good to go.


This looks terribly complicated but is actually quite simple. I could remember it for 8 days - so there is the proof. 

Good Luck.

[djohnston]

I tried to help somebody with a similar problem in the Gnome Forum.  If I was successful I don't know - never heard of him/her again.

Anyway - for the sake of completeness here it is as well:

longtom,

Sorry I didn't reply sooner. I'm still trying to pinpoint an application problem and thought olewilly's solution might provide a clue. I had never used gconf-editor before. It's not even installed on an e17 or LXDE desktop. Anyway, I did install it on my e17 one. There were no dependencies, or they had already been met when I installed. In the metacity keybinding commands, I did change the two values for screenshots, but it didn't help my situation. But I thank you for posting because I learned something new from it.