How to run gsettings for another user Ubuntu 18.04.2 LTSWhy should users never use normal sudo to start graphical applications?Graphical editor for GSettings/dconf?Permission denied error for running command on ubuntuHow to run “gsettings” command inside a kickstart file?gsettings and anacronWhy does 'sudo java' change the user home directory to /root?Changing gsettings for another user from an ansible script (started by vagrant)Run gsettings with crontab
How come the Russian cognate for the Czech word "čerstvý" (fresh) means entirely the opposite thing (stale)?
How to define the line style in advance of plot function
What’s the BrE for “shotgun wedding”?
Unicode-math and declaring symbol font
How to get a smooth, uniform ParametricPlot of a 2D Region?
Did the Soviet army intentionally send troops (e.g. penal battalions) running over minefields?
Determine the Winner of a Game of Australian Football
Did Joe Biden "stop the prosecution" of his son in Ukraine? And did he brag about stopping the prosecution?
How are characteristic classes morphisms of infinite loop spaces? (if they are)
How to accompany with piano in latin music when given only chords?
Can 35 mm film which went through a washing machine still be developed?
Today I am 20 but next year I will turn 22
Does SQL Server's serializable isolation level lock entire table
Maintaining distance
What are some ways to season that don't rely on garlic and onions?
In what sense is SL(2,q) "very far from abelian"?
Are starfighters a realistic evolution of space naval warfare?
Is negative resistance possible?
Was there an autocomplete utility in MS-DOS?
What makes a character irredeemable?
Advices to added homemade symbols
How is the speed of nucleons in the nucleus measured?
Scorched receptacle
Redirect output on-the-fly - looks not possible in Linux, why?
How to run gsettings for another user Ubuntu 18.04.2 LTS
Why should users never use normal sudo to start graphical applications?Graphical editor for GSettings/dconf?Permission denied error for running command on ubuntuHow to run “gsettings” command inside a kickstart file?gsettings and anacronWhy does 'sudo java' change the user home directory to /root?Changing gsettings for another user from an ansible script (started by vagrant)Run gsettings with crontab
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;
I am trying to run gsettings for another user in Ubuntu 18.04.2 LTS. Specifically, I am attempting to prevent the user's screen from locking. This will be run as part of a bash script. The commands I am using are:
su someuser
dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
Because this is run via ssh, I am opening with dbus-launch to start dbus then attempting a simple call to gsettings. However, I get the error:
dbus[22652]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/user/1000" is owned by uid 1000, not our uid 1001
(process:22650): dconf-CRITICAL **: 11:11:27.830: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
(process:22650): dconf-CRITICAL **: 11:11:27.830: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
(process:22650): dconf-CRITICAL **: 11:11:27.836: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
To confirm that the UIDs are being mismatched I checked the /run/user directory:
ls -lah /run/user
Which outputs:
total 0
drwxr-xr-x 4 root root 80 Apr 16 14:25 .
drwxr-xr-x 31 root root 900 Apr 16 14:25 ..
drwx------ 4 adminuser adminuser 100 Apr 16 14:25 1000
drwx------ 11 someuser someuser 260 Apr 16 12:26 1001
I also tried using sudo:
sudo -u "someuser" dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
Which gives the errors:
(process:22264): dconf-CRITICAL **: 14:33:41.124: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-CRITICAL **: 14:33:41.124: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-CRITICAL **: 14:33:41.135: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-WARNING **: 14:33:41.152: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Cannot open dconf database: Failed to open file “/home/adminuser/.config/dconf/user”: Permission denied
Which leads to the question, why is gsettings trying to run for adminuser instead of someuser and how can it be directed to run for someuser by adminuser over SSH?
command-line gsettings
edited Apr 16 at 18:44
terdon♦
74.5k14 gold badges151 silver badges235 bronze badges
asked Apr 16 at 18:40
user2395126user2395126
1485 bronze badges
add a comment
|
I am trying to run gsettings for another user in Ubuntu 18.04.2 LTS. Specifically, I am attempting to prevent the user's screen from locking. This will be run as part of a bash script. The commands I am using are:
su someuser
dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
Because this is run via ssh, I am opening with dbus-launch to start dbus then attempting a simple call to gsettings. However, I get the error:
dbus[22652]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/user/1000" is owned by uid 1000, not our uid 1001
(process:22650): dconf-CRITICAL **: 11:11:27.830: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
(process:22650): dconf-CRITICAL **: 11:11:27.830: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
(process:22650): dconf-CRITICAL **: 11:11:27.836: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
To confirm that the UIDs are being mismatched I checked the /run/user directory:
ls -lah /run/user
Which outputs:
total 0
drwxr-xr-x 4 root root 80 Apr 16 14:25 .
drwxr-xr-x 31 root root 900 Apr 16 14:25 ..
drwx------ 4 adminuser adminuser 100 Apr 16 14:25 1000
drwx------ 11 someuser someuser 260 Apr 16 12:26 1001
I also tried using sudo:
sudo -u "someuser" dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
Which gives the errors:
(process:22264): dconf-CRITICAL **: 14:33:41.124: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-CRITICAL **: 14:33:41.124: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-CRITICAL **: 14:33:41.135: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-WARNING **: 14:33:41.152: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Cannot open dconf database: Failed to open file “/home/adminuser/.config/dconf/user”: Permission denied
Which leads to the question, why is gsettings trying to run for adminuser instead of someuser and how can it be directed to run for someuser by adminuser over SSH?
command-line gsettings
edited Apr 16 at 18:44
terdon♦
74.5k14 gold badges151 silver badges235 bronze badges
asked Apr 16 at 18:40
user2395126user2395126
1485 bronze badges
2
Trysudo -Hu someuser dbus-launch ...
– steeldriver
Apr 16 at 18:44
It works! Post as an answer and I will accept it.
– user2395126
Apr 16 at 18:45
add a comment
|
I am trying to run gsettings for another user in Ubuntu 18.04.2 LTS. Specifically, I am attempting to prevent the user's screen from locking. This will be run as part of a bash script. The commands I am using are:
su someuser
dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
Because this is run via ssh, I am opening with dbus-launch to start dbus then attempting a simple call to gsettings. However, I get the error:
dbus[22652]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/user/1000" is owned by uid 1000, not our uid 1001
(process:22650): dconf-CRITICAL **: 11:11:27.830: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
(process:22650): dconf-CRITICAL **: 11:11:27.830: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
(process:22650): dconf-CRITICAL **: 11:11:27.836: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
To confirm that the UIDs are being mismatched I checked the /run/user directory:
ls -lah /run/user
Which outputs:
total 0
drwxr-xr-x 4 root root 80 Apr 16 14:25 .
drwxr-xr-x 31 root root 900 Apr 16 14:25 ..
drwx------ 4 adminuser adminuser 100 Apr 16 14:25 1000
drwx------ 11 someuser someuser 260 Apr 16 12:26 1001
I also tried using sudo:
sudo -u "someuser" dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
Which gives the errors:
(process:22264): dconf-CRITICAL **: 14:33:41.124: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-CRITICAL **: 14:33:41.124: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-CRITICAL **: 14:33:41.135: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-WARNING **: 14:33:41.152: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Cannot open dconf database: Failed to open file “/home/adminuser/.config/dconf/user”: Permission denied
Which leads to the question, why is gsettings trying to run for adminuser instead of someuser and how can it be directed to run for someuser by adminuser over SSH?
command-line gsettings
edited Apr 16 at 18:44
terdon♦
74.5k14 gold badges151 silver badges235 bronze badges
asked Apr 16 at 18:40
user2395126user2395126
1485 bronze badges
I am trying to run gsettings for another user in Ubuntu 18.04.2 LTS. Specifically, I am attempting to prevent the user's screen from locking. This will be run as part of a bash script. The commands I am using are:
su someuser
dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
Because this is run via ssh, I am opening with dbus-launch to start dbus then attempting a simple call to gsettings. However, I get the error:
dbus[22652]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/user/1000" is owned by uid 1000, not our uid 1001
(process:22650): dconf-CRITICAL **: 11:11:27.830: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
(process:22650): dconf-CRITICAL **: 11:11:27.830: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
(process:22650): dconf-CRITICAL **: 11:11:27.836: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.
To confirm that the UIDs are being mismatched I checked the /run/user directory:
ls -lah /run/user
Which outputs:
total 0
drwxr-xr-x 4 root root 80 Apr 16 14:25 .
drwxr-xr-x 31 root root 900 Apr 16 14:25 ..
drwx------ 4 adminuser adminuser 100 Apr 16 14:25 1000
drwx------ 11 someuser someuser 260 Apr 16 12:26 1001
I also tried using sudo:
sudo -u "someuser" dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
Which gives the errors:
(process:22264): dconf-CRITICAL **: 14:33:41.124: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-CRITICAL **: 14:33:41.124: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-CRITICAL **: 14:33:41.135: unable to create directory '/home/adminuser/.cache/dconf': Permission denied. dconf will not work properly.
(process:22264): dconf-WARNING **: 14:33:41.152: failed to commit changes to dconf: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2: Cannot open dconf database: Failed to open file “/home/adminuser/.config/dconf/user”: Permission denied
Which leads to the question, why is gsettings trying to run for adminuser instead of someuser and how can it be directed to run for someuser by adminuser over SSH?
command-line gsettings
command-line gsettings
edited Apr 16 at 18:44
terdon♦
74.5k14 gold badges151 silver badges235 bronze badges
asked Apr 16 at 18:40
user2395126user2395126
1485 bronze badges
edited Apr 16 at 18:44
terdon♦
74.5k14 gold badges151 silver badges235 bronze badges
asked Apr 16 at 18:40
user2395126user2395126
1485 bronze badges
edited Apr 16 at 18:44
terdon♦
74.5k14 gold badges151 silver badges235 bronze badges
edited Apr 16 at 18:44
terdon♦
74.5k14 gold badges151 silver badges235 bronze badges
edited Apr 16 at 18:44
terdon♦
74.5k14 gold badges151 silver badges235 bronze badges
74.5k14 gold badges151 silver badges235 bronze badges
asked Apr 16 at 18:40
user2395126user2395126
1485 bronze badges
asked Apr 16 at 18:40
user2395126user2395126
1485 bronze badges
asked Apr 16 at 18:40
user2395126user2395126
1485 bronze badges
1485 bronze badges
2
Trysudo -Hu someuser dbus-launch ...
– steeldriver
Apr 16 at 18:44
It works! Post as an answer and I will accept it.
– user2395126
Apr 16 at 18:45
add a comment
|
2
Trysudo -Hu someuser dbus-launch ...
– steeldriver
Apr 16 at 18:44
It works! Post as an answer and I will accept it.
– user2395126
Apr 16 at 18:45
2
2
Try
sudo -Hu someuser dbus-launch ...– steeldriver
Apr 16 at 18:44
Try
sudo -Hu someuser dbus-launch ...– steeldriver
Apr 16 at 18:44
It works! Post as an answer and I will accept it.
– user2395126
Apr 16 at 18:45
It works! Post as an answer and I will accept it.
– user2395126
Apr 16 at 18:45
add a comment
|
1 Answer
1
active
oldest
votes
The issue here is related to Why should users never use normal sudo to start graphical applications? i.e. that by default, sudo does not change $HOME to that of the target user.
You can change that using the -H (--set-home) option:
-H, --set-home
Request that the security policy set the HOME environment
variable to the home directory specified by the target user's
password database entry. Depending on the policy, this may
be the default behavior.
So
sudo -Hu someuser dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
answered Apr 16 at 18:50
steeldriversteeldriver
79.6k12 gold badges130 silver badges214 bronze badges
add a comment
|
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1134453%2fhow-to-run-gsettings-for-another-user-ubuntu-18-04-2-lts%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The issue here is related to Why should users never use normal sudo to start graphical applications? i.e. that by default, sudo does not change $HOME to that of the target user.
You can change that using the -H (--set-home) option:
-H, --set-home
Request that the security policy set the HOME environment
variable to the home directory specified by the target user's
password database entry. Depending on the policy, this may
be the default behavior.
So
sudo -Hu someuser dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
answered Apr 16 at 18:50
steeldriversteeldriver
79.6k12 gold badges130 silver badges214 bronze badges
add a comment
|
The issue here is related to Why should users never use normal sudo to start graphical applications? i.e. that by default, sudo does not change $HOME to that of the target user.
You can change that using the -H (--set-home) option:
-H, --set-home
Request that the security policy set the HOME environment
variable to the home directory specified by the target user's
password database entry. Depending on the policy, this may
be the default behavior.
So
sudo -Hu someuser dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
answered Apr 16 at 18:50
steeldriversteeldriver
79.6k12 gold badges130 silver badges214 bronze badges
add a comment
|
The issue here is related to Why should users never use normal sudo to start graphical applications? i.e. that by default, sudo does not change $HOME to that of the target user.
You can change that using the -H (--set-home) option:
-H, --set-home
Request that the security policy set the HOME environment
variable to the home directory specified by the target user's
password database entry. Depending on the policy, this may
be the default behavior.
So
sudo -Hu someuser dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
answered Apr 16 at 18:50
steeldriversteeldriver
79.6k12 gold badges130 silver badges214 bronze badges
The issue here is related to Why should users never use normal sudo to start graphical applications? i.e. that by default, sudo does not change $HOME to that of the target user.
You can change that using the -H (--set-home) option:
-H, --set-home
Request that the security policy set the HOME environment
variable to the home directory specified by the target user's
password database entry. Depending on the policy, this may
be the default behavior.
So
sudo -Hu someuser dbus-launch gsettings set org.gnome.desktop.screensaver lock-enabled false
answered Apr 16 at 18:50
steeldriversteeldriver
79.6k12 gold badges130 silver badges214 bronze badges
answered Apr 16 at 18:50
steeldriversteeldriver
79.6k12 gold badges130 silver badges214 bronze badges
answered Apr 16 at 18:50
steeldriversteeldriver
79.6k12 gold badges130 silver badges214 bronze badges
answered Apr 16 at 18:50
steeldriversteeldriver
79.6k12 gold badges130 silver badges214 bronze badges
79.6k12 gold badges130 silver badges214 bronze badges
add a comment
|
add a comment
|
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1134453%2fhow-to-run-gsettings-for-another-user-ubuntu-18-04-2-lts%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Try
sudo -Hu someuser dbus-launch ...– steeldriver
Apr 16 at 18:44
It works! Post as an answer and I will accept it.
– user2395126
Apr 16 at 18:45