** Changed in: gconf
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/290647
Title:
gconfd does not refresh cache when sudo-ing current user to modify
setting
To
** Changed in: gconf
Importance: Unknown = Medium
--
gconfd does not refresh cache when sudo-ing current user to modify setting
https://bugs.launchpad.net/bugs/290647
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
This is a bug in either su or sudo. When copying the user environment,
it fails to correctly copy the DBUS_SESSION_BUS_ADDRESS,
DBUS_SESSION_BUS_PID, and DBUS_SESSION_BUS_WINDOWID variables. This may
be working as intended, I'm not sure exactly how sudo/su function in
terms of copying transient
** Changed in: gconf
Status: Unknown = New
--
gconfd does not refresh cache when sudo-ing current user to modify setting
https://bugs.launchpad.net/bugs/290647
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
This bug did not have a package associated with it, which is important for
ensuring that it gets looked at by the proper developers. You can learn more
about finding the right package at
I have the same problem, though using gconftool-2 --shutdown doesnt
solve my problem.
I am trying to change the proxy settings of the main user depending on
the vpn state via a networkmanager dispatcher script.
More info about the things i found out about this bug can be read in the forum
that's not a bug as indicated on the upstream bug
** Changed in: gconf (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: New = Triaged
** Tags removed: gconf gconf-editor gconfd regression-release
--
gconfd does not refresh
Yes, I agree this isn't a bug so much as a feature change...
A workaround as recommended upstream is to export the
DBUS_SESSION_BUS_ADDRESS with the sudo command, i.e., sudo -u $USER
DBUS_SESSION_BUS_ADDRESS=$DBUS_SESSION_BUS_ADDRESS command
In the case that one is running a script that doesn't
The aforementioned workaround needs to have an appropriate XAUTHORITY
environment variable defined.
To sudo without doing this (e.g., from a command line process), try
something like the following:
# assumes the $USER and $HOME directories are defined somehow
DBUS_SESSION=$(grep -v ^#
