keybindings not remembered on reboot

Bug #430981 reported by NoahY
138
This bug affects 22 people
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
Fix Released
High
Sebastien Bacher
Karmic
Fix Released
High
Sebastien Bacher

Bug Description

Hi, after recent upgrades, changes to the keybindings in compiz or in System>Preferences>Keyboard Shortcuts are not remembered anymore after logging in.

I tried adding a shortcut key to open a terminal, and it works fine, but I expect it to be saved after I reboot, as it used to be. Now, upon reboot, the keyboard shortcut no longer works.

Same problem with CCSM; changing keybindings for Ring Switcher doesn't last after reboot.

Using Karmic AMD 64 with latest updates this morning.

tags: added: keybindings
tags: added: keyboard-propertie
affects: ubuntu → gnome-control-center (Ubuntu)
affects: gnome-control-center (Ubuntu) → compiz (Ubuntu)
Changed in compiz (Ubuntu):
importance: Undecided → Low
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

I can confirm this.

It wasn't a one-time loss, I set new keybindings (in ccsm) and they are lost when I reboot

Changed in compiz (Ubuntu):
status: New → Confirmed
Changed in compiz (Ubuntu):
importance: Low → High
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
tags: added: regression-potential
removed: keybindings keyboard-propertie
Changed in compiz (Ubuntu Karmic):
assignee: Canonical Desktop Team (canonical-desktop-team) → Robert Ancell (robert-ancell)
Revision history for this message
Lbird (lbird94) wrote :

It happen not only after reboot. When I log out and log in (without reboot) some of the keyboard shortcut settings are erased also.

Revision history for this message
Jonathan Lumb (jonolumb) wrote :

I too am experiencing this same bug - I used to have a shortcut key for opening a terminal (Super + T) which I now have to reconfigure each time I login. Likewise, other shortcut keys for some Compiz plugins are not working (such as the scale plugin and a few others).

This is a real pain and needs some urgent attention. Let me know if I can provide any information to help.

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

The code in compiz to work with gconf hasn't changed in 5 months and the code to handle settings in general hasn't changed significantly since the same time (just memleak fixes since). I am also not able to reproduce this anymore. Perhaps it is a gconf issue?

Revision history for this message
John B. (jbuncher) wrote :

I don't know if it's a gconf issue, but I'm still experiencing this.

Revision history for this message
Iain Lane (laney) wrote : Re: [Bug 430981] Re: keybindings not remembered on reboot

On Mon, Sep 21, 2009 at 01:43:47AM -0000, Travis Watkins wrote:
> The code in compiz to work with gconf hasn't changed in 5 months and the
> code to handle settings in general hasn't changed significantly since
> the same time (just memleak fixes since). I am also not able to
> reproduce this anymore. Perhaps it is a gconf issue?

They seem to be remembered for me now too. Is anyone else still seeing this?

Iain

Revision history for this message
Claudio Moretti (flyingstar16) wrote :

After going to System > Preferences > Appeareance > Visual Effects, setting
it to "None", rebooting and then restoring compiz effects, I am not
experiencing this anymore.

On Mon, Sep 21, 2009 at 10:03, Iain Lane <email address hidden>wrote:

> On Mon, Sep 21, 2009 at 01:43:47AM -0000, Travis Watkins wrote:
> > The code in compiz to work with gconf hasn't changed in 5 months and the
> > code to handle settings in general hasn't changed significantly since
> > the same time (just memleak fixes since). I am also not able to
> > reproduce this anymore. Perhaps it is a gconf issue?
>
> They seem to be remembered for me now too. Is anyone else still seeing
> this?
>
> Iain
>
> --
> keybindings not remembered on reboot
> https://bugs.launchpad.net/bugs/430981
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “compiz” package in Ubuntu: Confirmed
> Status in compiz in Ubuntu Karmic: Confirmed
>
> Bug description:
> Hi, after recent upgrades, changes to the keybindings in compiz or in
> System>Preferences>Keyboard Shortcuts are not remembered anymore after
> logging in.
>
> I tried adding a shortcut key to open a terminal, and it works fine, but I
> expect it to be saved after I reboot, as it used to be. Now, upon reboot,
> the keyboard shortcut no longer works.
>
> Same problem with CCSM; changing keybindings for Ring Switcher doesn't last
> after reboot.
>
> Using Karmic AMD 64 with latest updates this morning.
>

Revision history for this message
Lbird (lbird94) wrote :

Thanks, Claudio. It works for me.

Revision history for this message
Jonathan Lumb (jonolumb) wrote :

Thanks Claudio, my problem is now fixed aswell. I switched off Compiz Effects, rebooted and then re-enabled them and everything works as it should now.

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

If everyone does this we aren't going to be able to fix the bug. Could someone having this problem find me (Amaranth) on freenode IRC before using this workaround? We need to find a fix.

Revision history for this message
John B. (jbuncher) wrote :

Same here, following the steps (turn off compiz, set keybindings, reboot, re-enable compiz) has fixed the issue, my keybindings stay set after subsequent reboots, keeping compiz on. I just upgraded my desktop to alpha 6.x yesterday, so I'll check if it is affected as well. The machine I encountered the issue on had been upgraded to alpha 5, so it might be a setting that was messed up from an earlier package.

Revision history for this message
Claudio Moretti (flyingstar16) wrote :

Travis, this does NOT seem to be a bug, but something related to a bad
edited gconf value.
If (for example) one of Karmic compiz upgrades corrupted it, but resetting
it (by disabling and re-enabling visual effects) solves the problem (maybe
because compiz next upgrade does not touch that value), this becomes a
question, and stops being a bug.

On Mon, Sep 21, 2009 at 19:42, John B. <email address hidden> wrote:

> Same here, following the steps (turn off compiz, set keybindings,
> reboot, re-enable compiz) has fixed the issue, my keybindings stay set
> after subsequent reboots, keeping compiz on. I just upgraded my desktop
> to alpha 6.x yesterday, so I'll check if it is affected as well. The
> machine I encountered the issue on had been upgraded to alpha 5, so it
> might be a setting that was messed up from an earlier package.
>
> --
> keybindings not remembered on reboot
> https://bugs.launchpad.net/bugs/430981
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “compiz” package in Ubuntu: Confirmed
> Status in compiz in Ubuntu Karmic: Confirmed
>
> Bug description:
> Hi, after recent upgrades, changes to the keybindings in compiz or in
> System>Preferences>Keyboard Shortcuts are not remembered anymore after
> logging in.
>
> I tried adding a shortcut key to open a terminal, and it works fine, but I
> expect it to be saved after I reboot, as it used to be. Now, upon reboot,
> the keyboard shortcut no longer works.
>
> Same problem with CCSM; changing keybindings for Ring Switcher doesn't last
> after reboot.
>
> Using Karmic AMD 64 with latest updates this morning.
>

Revision history for this message
Daniel Lee (longinus00) wrote :

How is this not a bug? If an upgrade corrupted a gconf value I think that qualifies as a bug. If the user has to jump though hoops then he has not solved the bug, rather he has found a 'workaround'.

A more pertinent question to ask is, can the people who've disabled compiz temporarily to set the keybindings set NEW keybindings without having to quit compiz again?

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

With help from Longinus00 on IRC I have figured out what is happening here and why the workaround actually works.

The problem is the gconf plugin is getting loaded via command line. As of the first compiz 0.8.3 packages plugins loaded from command line cannot be disabled, ever. Since something is adding gconf to the command line and ccp is already there the two plugins fight and they both lose, neither one gets to save your settings. But what is adding gconf to the command line?

If you have every switched WMs in older versions of Ubuntu the key /desktop/gnome/session/required_components/windowmanager will still be set to "gnome-wm" since we can't change keys for users. gnome-wm does start compiz with gconf and thus we get this bug. This is why switching to metacity and back to compiz via Appearance Properties fixes the problem, it sets this key to "compiz" as it should be.

gnome-wm seems to have some code that is supposed to detect this case and update the key for you but for whatever reason it is obviously not working. Moving bug to gnome-session package since that is where gnome-wm is located.

affects: compiz (Ubuntu Karmic) → gnome-session (Ubuntu Karmic)
Changed in gnome-session (Ubuntu Karmic):
assignee: Robert Ancell (robert-ancell) → Sebastien Bacher (seb128)
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-session - 2.28.0-0ubuntu2

---------------
gnome-session (2.28.0-0ubuntu2) karmic; urgency=low

  * debian/patches/01_gnome-wm.patch:
    - don't add gconf to the compiz command line options since cpp is used now,
      having both loaded lead to keybindings issues for example (lp: #430981)

 -- Sebastien Bacher <email address hidden> Tue, 22 Sep 2009 23:00:28 +0200

Changed in gnome-session (Ubuntu Karmic):
status: Fix Committed → Fix Released
Revision history for this message
ddv (simon-dalsgaard) wrote :

I have gnome-session 2.28.0-0ubuntu4 and I still has to do the trick from #14, why?

Revision history for this message
David (davidarredondolopez) wrote :

Hi everyoner, where can i find the gnome-session version?
I'm having the same problem with Karmic of 29 October release Distribution.
Thank's

Revision history for this message
Rykel from Singapore (rykel98) wrote :

Hello everybody, I am using Karmic and the same thing happened after I turned on the "Ultimate" profile of Compiz... some of my keyboard shortcuts (such as Print Screen, Alt-Home to open Home folder, Alt-F1 to open Main Menu etc.) no longer works.

I will also use the workaround and hopefully Amarath finds a solution, as I need to use the Print Screen function right away.

Please let me know if you need any further help.

Revision history for this message
Rykel from Singapore (rykel98) wrote :

HI again,

The "disabled keyboard shortcuts" bug is still around... I disabled Compiz in Appearance, rebooted and the keyboard shortcuts worked.

I enabled Compiz (Custom --> "Ultimate" profile) and the keyboard shortcuts do NOT work again.

By the way, how do I reset the keyboard shortcuts to the default Ubuntu settings?

Revision history for this message
renegat (rozbujnik) wrote :

Recently I changed keyboard layout. Now some of keybindings are correct while the other does not work! Damn you dvorak layout!!

This is the issue on Lucid!

Revision history for this message
Sébastien Pierre (sebastien-type-z) wrote :

When configuring the keys to go to left/right workspace through System Preferences -> Keyboard -> Shortcuts, shortcuts are only functional for the current session. Logging out or rebooting resets the keyboard shortcuts to their default.

The bug is probably due to some conflict between Compiz's own config and Gnome's keyboard shortcuts .

Revision history for this message
Anatoliy Borisov (rednex) wrote :

Ubuntu 12.10 restores default keyboard shutcut settings after reboot

Revision history for this message
unwrecker (unwrecker) wrote :

Need fix for Quantal

Revision history for this message
Alexander Volfman (alexandervolfman) wrote :

Hello,
Would you be reopening the bug for 12.10?

Revision history for this message
Richard Hansen (rhansen) wrote :

@unwrecker and @alexandervolfman: This bug has been fixed and so this bug report won't be reopened. However, a regression with similar symptoms has appeared in 12.10 (Quantal). See bug #1063617.

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.