Compiz Put plugin does not allow setting keyboard actions in Gutsy

Bug #151556 reported by Per B. Sederberg
8
Affects Status Importance Assigned to Milestone
compizconfig-settings-manager
Invalid
Undecided
Unassigned
metacity (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: compiz-fusion-plugins-main

Hi Folks:

Although I can set the keyboard shortcuts for most of the compiz plugins with the Advanced Desktop Effects Settings manager, the settings I enter for the Put plugin to not take effect. I am on a T61 laptop running the latest updates of Gutsy and do not have the KP keys, so I'd really like to remap so that I can place windows with the keyboard.

What happens is that I enter the new keyboard shortcut under the Bindings heading in the Actions tab of the Put plugin and they show up for a split second, then the Bindings hierarchical menu closes and the setting is erased.

What is the actual file that holds these settings? Perhaps I can try setting it manually there to see if it works.

Thanks for any help,
Per

Revision history for this message
Per B. Sederberg (psederberg) wrote :

I think I've found a clue to help solve the problem.

I tried editing the setting using the gconf-editor and, although most plugins are listed and I can set them there, the Put plugin is not listed. So, it could be that the plugin is failing to write out its settings because there is no node specified there to use.

Hope this helps solve the problem,
Per

Revision history for this message
Per B. Sederberg (psederberg) wrote :

Indeed it did help locate the problem, which seemed to be in the metacity window-keybindings configuration in gconf-editor. As it turned out, all the settings for moving a window around the desktop/viewport, such as move_to_corner_ne, were set to be integers, but they needed to be strings. Once I changed them all to strings, the CompizConfig settings manager was able to set the keybindings.

I'm not sure what application creates the original settings for the metacity keybindings that you can see with gconf-editor, but that's where the bug is.

Hope this helps someone,
Per

Revision history for this message
kmmbvnr (kmmbvnr) wrote :

I found that key bindings cannot be assigned only if configuration stored in GConf.

With flat-file backend (Settings Manager -> Prefrences -> Backend) everything works.

Revision history for this message
Francois Rigaut (francois.rigaut) wrote :

Per B. Sederberg: thanks. Setting "move_to_" to string type as you described indeed worked ok. I had been stumbling on this bug for a while to, so your workaround is welcome.
I am using compiz 1:0.6.2+git20071119-0ubuntu1~gutsy1 (backport), but this bug was already present in the non-backport gutsy package (1:0.6.0+git20071008-0ubuntu1.1).

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10?

Changed in compiz-fusion-plugins-main:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Francois Rigaut (francois.rigaut) wrote :

not sure what you mean: do you mean is the bug still present in 8.10? Nope, it's been fixed (thanks). At least it's working for me. But I haven't tried the put plugin from a fresh install, so may be the patch got carried over with my account migration.

Revision history for this message
res (ionutbanc) wrote :

This still exists in 8.10. I've been trying it right now, and in CompizConfig the texts for the shortcut keys were written in blue. Anyway, I changed the values to string type in gconf-editor and the shortcuts worked. There still are some shortcuts set as integers in gconf, as far as I can see.

Revision history for this message
Travis Watkins (amaranth) wrote :

This was bug in metacity (move_to_corner_ne is a metacity setting) that appears to be resolved for me in karmic. If you can still reproduce in karmic feel free to reopen this bug.

Changed in compizconfig-settings-manager:
status: New → Invalid
affects: compiz-fusion-plugins-main (Ubuntu) → metacity (Ubuntu)
Changed in metacity (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.