quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as Won't Fix.
** Changed in: gnome-settings-daemon (Ubuntu Quantal)
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of
Any idea when the fix is going to be available in Quantal and if it's
already in Raring?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1071950
Title:
Thanks Sebastian, Steve, and everybody else involved in getting this
fixed in precise!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1071950
Title:
This bug was fixed in the package gnome-settings-daemon -
3.4.2-0ubuntu0.5
---
gnome-settings-daemon (3.4.2-0ubuntu0.5) precise-proposed; urgency=low
* debian/patches/dont_overwrite_gconf_keys.patch:
- don't trigger the gsettings-gconf keys conversion on dconf update
I can confirm that the new package does prevent settings in dconf from
propagating into gconf on a dconf update after the package is installed
and the user is logged out and back in. I haven't used the new package
long enough to identify if there are any regressions, but it does seem
to fix this
Hello Margarita, or anyone else affected,
Accepted gnome-settings-daemon into precise-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source/gnome-
settings-daemon/3.4.2-0ubuntu0.5 in a few hours, and then in the
-proposed repository.
Please help us by
** Branch linked: lp:ubuntu/precise-proposed/gnome-settings-daemon
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1071950
Title:
gnome-settings-daemon dconf to gconf
** Tags added: precise quantal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1071950
Title:
gnome-settings-daemon dconf to gconf plugin causes settings to be lost
Ready to go, imho.
Marga: one tiny point that I missed the first time around. GObject
signals are nominally written like signal-name rather than
signal_name. Your patch is fine as-is -- it's mostly a matter of
style in this case.
--
You received this bug notification because you are a member
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided = High
** Also affects: gnome-settings-daemon (Ubuntu Quantal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: gnome-settings-daemon (Ubuntu Quantal)
Importance: Undecided = High
** Changed in: gnome-settings-daemon (Ubuntu Quantal)
Status: New = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Description changed:
+ Impact:
+ Using dconf profiles can lead to gconf keys to be overwritten with wrong
values, it's especially impact some desktop settings and compiz
+
+ Test Case:
+
+ $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false
+ $ gconftool --get
I added my comments to bug 963125 regarding the dconf array keybindings
being converted to lists in gconf, where metacity expects strings.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
I'm pretty new to dconf, so I'm making some assumptions which may be
incorrect. When dconf update is run as root, that only updates settings
which are either mandatory or defaults system-wide. Neither of those
changes should result in a change in the users home directory, and if a
user wasn't
This also exposes something else, which might be better as a separate
bug. wm-schemas.convert tries to convert metacity keybindings from
dconf to gconf. Unfortunately the types are different, so anything
accepted by dconf probably won't actually work once it's written to
gconf. This was exposed
Hi,
I have prepared and tested a small patch that fixes this issue. What
the patch does is not update any keys when dconf emits the everything
changed signal. To do this, it connects to the event_change signal
and checks if the number of keys is 0, and returns TRUE in that case to
prevent the
Functionally, the patch looks pretty good to me. Thanks for the
attention to detail with respect to the signal disconnection.
One small detail is that the function you introduce should be marked
'static' (since it is not used outside of the current file). Otherwise,
everything else looks fine.
Joel, regarding the Alt-Tab thing, it's reported in:
https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/963125
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1071950
The attachment Patch to the plugin of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag 'patch'
I'm attaching a revised version, taking into account Ryan's comments.
** Patch added: Updated patch
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+attachment/3418204/+files/fix-g-s-d-gconf-plugin.diff
** Patch removed: Patch to the plugin
The issue specifically:
'dconf update' emits a signal that says everything has changed
Meanwhile, we have the configuration migration stuff watching for
changes and assuming that if there was a change in dconf it means that
we should sync it up to gconf.
The trouble comes that everything has
I've reduced the amount of files needed in order to reproduce the bug.
** Attachment added: Sample /etc/dconf configuration to reproduce the bug.
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+attachment/3414955/+files/etc-dconf-files-reduced.tar.gz
**
Sample configuration that allows to reproduce the bug.
** Attachment added: Sample /etc/dconf configuration to reproduce the bug.
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+attachment/3414956/+files/etc-dconf-files-reduced.tar.gz
** Attachment removed:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
Under what conditions would the gconf plugin for gsettings daemon
convert dconf settings into gconf? This is triggered by a dconf update
while a user is logged in, which seems a rare use case under normal
conditions. When is this plugin designed to operate normally, and could
that other normal
This is my take on the issue from what I spoke with dsert earlier today:
There's a signal that dconf update emits when there are changes, so that
monitoring stuff can find out about it. This plugin is one of the
monitoring stuff.
The plugin is supposed to sync up settings from dconf to gconf
26 matches
Mail list logo
