This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1063617
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: compiz
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
** Changed in: compiz/0.9.11
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings
** Changed in: compiz/0.9.11
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings
This bug was fixed in the package compiz -
1:0.9.11.1+14.04.20140701-0ubuntu1
---
compiz (1:0.9.11.1+14.04.20140701-0ubuntu1) trusty; urgency=medium
[ Chris Townsend ]
* Bump version to 0.9.11.1.
[ Ubuntu daily release ]
* New rebuild forced
-- Ubuntu daily release
Hello Martin, or anyone else affected,
Accepted compiz into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/compiz/1:0.9.11.1+14.04.20140623-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys
I also confirm that it works and I also tested with disabling click to
focus. Several reboots later and this setting remains unset and focus
follows mouse is in use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This doesn't seem to fix the bug for me. :(
I tested changing the Refresh rate in Composite plugin from 50 to 60,
but when I restart Unity the refresh rate return to 50, maybe I'm
missing something.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this
@Manglasape,
I take it you have an Nvidia graphics card. There seems to be a
separate bug where Nvidia graphics somehow defaults to 50Hz after
reboots. I've tried fixing that bug, but it seems it's still not fixed.
I don't have Nvidia, so it's hard for me to actually dig deep and try to
fix it.
@townsend
Oops, yes, I have an Nvidia graphics card, so I tested it again
unchecking the Clic to focus option in Focus Raise Behavior in
General options and after restarting Unity the Clic to focus remains
unchecked so it seems to work properly.
Sorry for my bad choice! :)
--
You received
Ok, cool, thanks for confirming. Based on your response, I'm going to
set this verification-done.
Thanks again!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This works for me on a fully updated system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
To
** Description changed:
[Impact]
Many users set custom shortcuts in Compiz for various functionality.
When this issue hits, many, if not all, of these custom shortcuts get
reset to the defaults which can cause much frustration in the user. It
is a very bad user experience.
Hello Martin, or anyone else affected,
Accepted compiz into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/compiz/1:0.9.11.1+14.04.20140623-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Great. Thanks Chris!
On Thu, Jun 19, 2014 at 4:59 PM, Launchpad Bug Tracker
1063...@bugs.launchpad.net wrote:
** Branch linked: lp:ubuntu/trusty-proposed/compiz
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1063617
I checked the Test Case from bug description.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
** Also affects: compiz (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting
Hello Martin, or anyone else affected,
Accepted compiz into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/compiz/1:0.9.11.1+14.04.20140617-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Branch linked: lp:ubuntu/trusty-proposed/compiz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
** Description changed:
+ [Impact]
+
+ Many users set custom shortcuts in Compiz for various functionality.
+ When this issue hits, many, if not all, of these custom shortcuts get
+ reset to the defaults which can cause much frustration in the user. It
+ is a very bad user experience.
+
+
** Description changed:
[Impact]
Many users set custom shortcuts in Compiz for various functionality.
When this issue hits, many, if not all, of these custom shortcuts get
reset to the defaults which can cause much frustration in the user. It
is a very bad user experience.
Just curious ... any ETA for this fix hitting 14.04?
On Wed, Jun 11, 2014 at 5:45 PM, Launchpad Bug Tracker
1063...@bugs.launchpad.net wrote:
** Branch linked: lp:~townsend/compiz/0.9.11.1
--
You received this bug notification because you are subscribed to the bug
report.
Hi Lukas,
We are preparing the 14.04 Compiz SRU that includes this fix now. I'm
guessing it will be in -proposed early next week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
** Branch linked: lp:~townsend/compiz/0.9.11.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
To
** Changed in: compiz
Status: In Progress = Fix Committed
** Changed in: compiz
Milestone: 0.9.11.0 = 0.9.12.0
** Also affects: compiz/0.9.11
Importance: Undecided
Status: New
** Changed in: compiz/0.9.11
Status: New = In Progress
** Changed in: compiz/0.9.11
Paul, the fix has been released only for Utopic for now, so if you're
using the development version of Ubuntu you'll get it automatically,
otherwise if you're running 14.04, the fix will be released soon as an
SRU update (you'll get instructions here).
--
You received this bug notification
Does this mean an upstream fix which would make it into Debian too? If
so what's the timescale?
Alternatively any way of getting a Wheezy-compatible backport sooner?
If so, I'd switch our 15 @ShrimpingIt studio laptops to LXDE if Compiz
Scale was stable once again (this bug reverted plugin
Will the fix be rolled out in automatic updates, or do we need to do
something manually to apply it?
Apologies, I'm not nearly tech saavy enough for this site.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:ubuntu/utopic-proposed/compiz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
This bug was fixed in the package compiz -
1:0.9.11+14.10.20140606-0ubuntu1
---
compiz (1:0.9.11+14.10.20140606-0ubuntu1) utopic; urgency=low
[ Chris Townsend ]
* Only ungrab the Mod2Mask modifier on buttons 4-7 to allow scrolling
in unfocused Gtk windows while still allowing
Thanks.
I tried on my other up to date Trusty box last night and I can't
reproduce the issue anymore (with the patch in), so a bit more info:
The issues found:
1) updateSetting (in gsettings/src/gsettings.c) always uses readOption
(even when integration is turned on). This function should use
** Branch linked: lp:~townsend/compiz/fix-lp1063617
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
** Changed in: compiz (Ubuntu)
Status: Confirmed = In Progress
** Changed in: compiz (Ubuntu)
Assignee: (unassigned) = Christopher Townsend (townsend)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~townsend/compiz/fix-lp1063617
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
14.04 :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
To manage notifications about this bug go
I can confirm the workaround using flat file configuration still works at
14.04. Steps to apply:
1. Install compizconfig-settings-manager
2. Open ccsm and go to Preferences Export and save your preferences
saved.profile
3. Change Backend to Flat-file Configuration Backend (here some people
Hey Folks,
Apologies for this bug and having let it sit for so long. It's
unfortunate that Sam left working on Compiz before having this bug
resolved. Based on his merge proposals linked to this bug, he seemed to
have an idea what was going on here, but he also said the fix is
complicated.
I'm
Thank you Christopher...
godspeed!
On 20 May 2014 15:58, Christopher Townsend
christopher.towns...@canonical.com wrote:
Hey Folks,
Apologies for this bug and having let it sit for so long. It's
unfortunate that Sam left working on Compiz before having this bug
resolved. Based on his
On Tue, May 20, 2014 at 6:58 AM, Christopher Townsend
christopher.towns...@canonical.com wrote:
I'm going to attempt to figure out what is going on here, but it may be
slow going. I'm going to make it a high priority to work on it and also
keep in mind that if I do find a fix, that I can try
Hey.
Yes. I have been looking into this bug over last few days.
Attaching a patch which works for me.
You can run following commands to try:
apt-src install compiz
(cd to compiz dir create0
(set your ~/.quiltrc as usual)
quilt push -a
quilt import /path/to/settings_reset_fix
dpkg-buildpackage
Hi Lukas,
Thank you so very much for your contribution! I'll begin testing this
out.
For anyone interested in testing this, I'm making a test PPA. It can be
found at https://launchpad.net/~townsend/+archive/compiz-settings-reset-
fix. As of this writing, I just uploaded the source package and
I enabled the PPA, upgraded, disabled the gsettings calls in my
session script (workaround for this bug) and restarted my session five
times. So far all of my keyboard and the auto-raise settings are still
working. Many thanks Lukas!
I'll report here if I see this happen again with this PPA
Confirming this bug exists on 14.04 (with ccsm installed). I set custom
shortcuts for navigating workspaces, and they are back to defualts after
reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I confirm that this bug is still affecting Compiz in 14.04LTS. Clean install +
no CCSM.
So, yet another new release (supposedly a stable, conservative and long-term
one) and still this has not been fixed !
It has now been a year and a half - across 4 releases - and still there is no
one
This still occurs randomly in 14.04. Seems to be happening no less (and
no more) often than in 13.10.
I'd still like to know whether there's a way to see which process is
actually changing the settings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Custom window management shortcuts set via the standard keyboard prefs
in Ubuntu Trusty 14.04 confirmed lost after logout/login. Clean
installation and no CCSM installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can confirm this bug on Trusty 14.04. Some keyboard shortcuts reset
every other reboot. ccsm installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1
Good to see that it's still being looked at.
I'm trying the dconf watch / thing now, but I see two problems with
it: The output of dconf is not timestamped nor does it show what process
caused the dconf change. Is there any way to obtain that information?
--
You received this bug notification
how come this bug is marked fix released when I'm still seeing it on
trusty..?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting
I agree, I still see it as well, just a bit less often.
** Changed in: compiz (Ubuntu)
Status: Fix Released = Confirmed
** Changed in: compiz
Status: Fix Released = Confirmed
** Changed in: compiz/0.9.9
Status: Fix Committed = Confirmed
--
You received this bug
I'm experiencing this daily both in my work machine and home machine.
Both are 13.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting
I also observe this behaviour in 13.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
To manage
Thank you Carl-Eric for your idea of monitoring what apps set gsettings and
what do they do exactly.
And also to Fred for indicating how to actually do this monitoring.
Now my question is: how could we execute a shell with the dconf watch command
early enough in the boot process so as to have
This bug is definitely not fixed. It still happens randomly on all of my
13.10 installations (all of them upgraded from 13.04, if that helps).
It's also only customized shortcuts that involve the Windows key
(super), at least those are the only ones that I notice. I can see no
pattern as to when
For me, it is not only Windows keys that are involved : I also use super,
but along with other regular keys. When I loose my custom shortcuts settings,
all of them are gone; reset to default values (Windows specific keys and
regular keys as well).
As for when this happens, that seems to be part
Is there a way to log what application sets gsettings and when? That
could help find the culprit.
Also, why is there anything that sets these shortcuts *at all*? That
should be a user setting and not something an application does on its
own.
--
You received this bug notification because you are
Carl-Eric Menzel,
Gsettings is a front-end for dconf.
You can watch when something gets written to dconf;
$ dconf watch /
or more specific
$ dconf watch /org/gnome/desktop/wm/keybindings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have this bug on 13.10 and it happens randomly. Sometimes it seems on
reboot, sometimes after updates, sometimes for no particular reason.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Just wanted to add my voice to the chorus -- this bug is a huge nuisance
for me as well. I have experienced it on multiple machines and on
12.10, 13.04, and 13.10. I'd be extremely grateful for a fix!
In case anyone gets around to working on this, FYI I experience the bug
on both the
This is just crazy. I've been having this problem since 12.04
12.10...13.04... and now 13.10. Each time, I hope for a resolution.
This means that for approaching two years, my keyboard settings have
been resetting on each computer I own. An old Thinkpad x41, a newer x61
and my desktop, a
This is very annoying that this bug was NEVER fixed since it appeared in
12.10...Every now and then there has been a fix released but that changed
nothing and it is generally not available for backport. Also once in a while
appears again in this thead the buggy solution to change CCSM
I am still seeing this in fully updated 13.04 installations. I can't
trigger it, it seems to happen at random, but feels like it's after
every other login. All window management and virtual desktop shortcuts
are reset to the unity/gnome defaults.
It happens both with Unity sessions as well as
This bug was never fixed.
In fact the GSettings integration breaks Compiz and its configuration in
various ways.
(lost and/or wrong settings on reboot, auto-change of settings,...)
The only good thing about it is that you can disable this integration
and use the old flat-file one instead.
--
@MC Return: Could you tell me how to disable the integration and use the old
flat-file?
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1
@Krister: CCSM preferences backend
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
To manage
Exactly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
To manage notifications about this bug go
Careful when doing this flatfile thing. It will nuke your settings to
the point that you can't open a window. I had to install icewm so
that I could reopen ccsm and enable the Unity plugin. After that, you
must reconfigure everything and many of the normal settings and those
in the Unity Tweak
Does fix commited mean that this should be in the 13.10 release? I
still have this problem in 13.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1
@Krister,
Fix commited means the patch has been sent and integrated in the source code.
But then it's not done, then the source code have to be compiled and packaged
and shipped, then its Fix released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK. So fix released indicates that I should not be seeing this bug
any longer. Let me know if I can give information about my setup.
On Sun, Nov 17, 2013 at 7:20 PM, Fred 1063...@bugs.launchpad.net wrote:
@Krister,
Fix commited means the patch has been sent and integrated in the source
(No longer working on compiz)
** Changed in: compiz/0.9.9
Assignee: Sam Spilsbury (smspillaz) = (unassigned)
** Changed in: compiz (Ubuntu)
Assignee: Sam Spilsbury (smspillaz) = (unassigned)
** Changed in: compiz
Assignee: Sam Spilsbury (smspillaz) = (unassigned)
--
You
I believe it may have something to do with the fact that alt goes to
that command unity thing. So each time we restart, it is reserved, but
not properly or something? Unlike say, ctrl, which if I use it in custom
shortcuts, it stays set.
--
You received this bug notification because you are a
Roman* Yep that's the exact issue I'm having.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
To
Same problem on 13.04 (clean installation, not an upgrade). I've set
Alt-F for Nautilus and Alt-P for Rhythmbox. After restart these
shortcuts are still present in keyboard settings but don't work until I
reassign them.
--
You received this bug notification because you are a member of Ubuntu
Hello,
I'm not sure if this is the same bug, but after setting custom shortcuts
on my system, they work until a reboot.
I'm on 13.04, and I'm wondering if this is a bug, or my own fault.
I have set custom shortcuts to do the following;
alt+w changes to next song (rhythmbox-client --next)
alt+q
** Changed in: compiz
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
I can confirm this problem still exists in 13.04: I issue the command
compiz --replace and then I cannot use window management keyboard
shortcuts like Alt+F4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
+1 Asking for backport to 12.10. This renders the keyboard shortcuts
dialog useless.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting
For information, the problem for me seems to have completely disappeared since
I upgraded to 13.04!
Nota Bene: it was not a clean install, but an upgrade of an existing 12.10.
Conditions where the problem does show up seem to be rather obscure...
--
You received this bug notification because
Gilles Tournier [2013-05-07 12:46 -]:
For information, the problem for me seems to have completely disappeared
since I upgraded to 13.04!
Nota Bene: it was not a clean install, but an upgrade of an existing 12.10.
Conditions where the problem does show up seem to be rather obscure...
It seems to be working fine here in a brand new installation of 13.04
(both gsettings and flat file).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1
Also confirming, this bug is not fixed in 13.04 (via upgrade route from
12.10, if it makes any difference).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1
Confirming in final and fully updated 13.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
To
This just happened on fully up2date 13.04. All settings for Compiz
Commands plugin lost for no apparent reason. Verified gone from dconf
database. Other settings made from ccsm seem ok. Is there a separate bug
filed for 13.04 ?
compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
unity
WM keybinding customizations also disappeared (CCSM - general options
- key bindings), along with commands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1
** Changed in: compiz
Milestone: 0.9.9.2 = 0.9.10.0
** Also affects: compiz/0.9.9
Importance: Undecided
Status: New
** Changed in: compiz/0.9.9
Importance: Undecided = High
** Changed in: compiz/0.9.9
Status: New = Fix Committed
** Changed in: compiz/0.9.9
Is there a work around that generally works and does not crash the
system for 12.10 users?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps
Can we update the description to describe this bug as Raring 13.04 only
and open a seperate linked bug for Quantal 12.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
** Branch linked: lp:ubuntu/compiz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
wrong values
To manage
André,
Thank you for your warning. I had also tried your fix, but Unity got completely
screwed up - same as described by the two other people that reported this
issue. I tried to play a little bit at recovering the situation - but to no
avail. Even trying to reinstall the packages involved
Stegard,
I have tried your autostart solution, but it didn't work for me...I will have
to investigate a little more to see if perhaps I have also a problem with Gnome
keyboard properties. Also: do I have to register the file as an app in some way?
--
You received this bug notification because
Now there is three people with problems in applying my advice at comment
24. I am very sorry. So be warned: it works for me maybe because my
configuration is far away from default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Gilles Tournier 1063...@bugs.launchpad.net writes:
Stegard,
I have tried your autostart solution, but it didn't work for me...I will have
to
investigate a little more to see if perhaps I have also a problem with Gnome
keyboard properties. Also: do I have to register the file as an app in
I am also begging for a backport to 12.10 !!!
Since upgrading to Quantal, this very annoying behavior of not remembering
shortcuts across logout/logins has forced me to revert to using 12.04LTS...I
have been using two shortcuts for a very long time: one for closing a window
and one for
Gilles Tournier 1063...@bugs.launchpad.net writes:
[...]
If backporting would unfortunately be impossible, does anybody know of a way
to
force the settings I want by using a script?
I have all my Compiz settings dumped to a text file which I load at
login ..
Created with command:
$ dconf
Although two people reported problems, what I said at comment 24 is still
working fine here. But I wouldn't try to do this if I didn't know how to
recover from a bad configuration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi all. I have the same problem (ubuntu 12.10, compiz 0.9.8.6). Now, the
weird thing is that the behaviour is unpredictable for me. I use mainly
5 shortcuts: Ctrl-Shift-T for new tab, and Ctrl-F1 ... F4 for switching
workspaces. What I observed... (1) the Ctrl-Shift-T is never washed out;
(2) the
I'm having what I think is this bug in 13.04 Raring, with Compiz
1:0.9.9~daily13.03.08-0ubuntu1 (from yesterday). Has this fix been
merged into the dailies yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: compiz
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063617
Title:
1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
1 - 100 of 152 matches
Mail list logo
