Public bug reported:
The gsettings plug don't give access to reading gsettings keys (others
than defaults).
gsettings is sending write values over dbus. The daemon then picks them
up, write the new value to ~/.config/dconf/user and then send another
dbus signal for the client to reread the mmaped file.
All the dbus mediation is fine and working well, however, as $HOME in
snap is different from $HOME from the user session, gsettings key are
never refreshed locally.
As a workaround, the desktop launcher is requiring the home plug in addition to
gsettings, and then, on first startup, symlink
$SNAP_USER_DATA/.config/dconf/user to user's ~/.config/dconf/user.
It would be good for the gsettings plug doing that. (until we can get full
gsettings key mediation ofc)
** Affects: snappy
Importance: Undecided
Status: New
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Tags: snap-desktop-issue
** Package changed: ubuntu => snapd (Ubuntu)
** Also affects: snappy
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/1600154
Title:
Reading gsettings key don't work locally (writing does)
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1600154/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
