Having another gsettings backend is possible I guess, but we would need to write that code and we might as well invest the effort on the proper solution/proxy...
Your comment made me think about it a bit more though and adding the dbus permissions isn't going to resolve the issue. It would let the application reach the service and write changes to the system db but the reads are done by mmaping the file so the applications wouldn't to read anything back. We could have a dconf db in the snap and tweak environment, but then we would need to have an another dbus session bus and private dconf instance inside the snap.... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576308 Title: gsettings doesn't work with snap confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1576308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
