gksu: Gtk-WARNING **: cannot open display: :0
All of the sudden gksu stopped working for me:
~$ gksu gparted
(gpartedbin:24252): Gtk-WARNING **: cannot open display: :0
The same happens with gparted-pkexec:
~$ gparted-pkexec
No protocol specified
(gpartedbin:25454): Gtk-WARNING **: cannot open display: :0
What could possibly be causing this?
I am not running this through SSH or VNC. This is localhost in a normal terminal window.
xorg sudo gtk gksu pkexec
edited Apr 27 '15 at 4:55
Mark Paskal
2,65411827
asked Apr 26 '15 at 16:39
d_inevitabled_inevitable
1,15421635
|
show 3 more comments
All of the sudden gksu stopped working for me:
~$ gksu gparted
(gpartedbin:24252): Gtk-WARNING **: cannot open display: :0
The same happens with gparted-pkexec:
~$ gparted-pkexec
No protocol specified
(gpartedbin:25454): Gtk-WARNING **: cannot open display: :0
What could possibly be causing this?
I am not running this through SSH or VNC. This is localhost in a normal terminal window.
xorg sudo gtk gksu pkexec
edited Apr 27 '15 at 4:55
Mark Paskal
2,65411827
asked Apr 26 '15 at 16:39
d_inevitabled_inevitable
1,15421635
You do not work in a graphical user interface or trying to run a program on a system (eg. via ssh) that no graphical interface provides.
– A.B.
Apr 26 '15 at 16:50
@A.B. I should clarify that this is not via ssh. It's on local host in a very normal terminal window. Infact opening gparted from the application menu has the same result.
– d_inevitable
Apr 26 '15 at 16:53
You shouldn't have to usegksuto run GParted.gparteduses polkit to get elevated privileges.
– muru
Apr 26 '15 at 16:59
@muru when I rungpartedwithoutgksuI getRoot privileges are required for running gparted.
– d_inevitable
Apr 26 '15 at 17:17
Ok, trygparted-pkexec(withoutgksu) orgksu gpartedbin.
– muru
Apr 26 '15 at 17:39
|
show 3 more comments
All of the sudden gksu stopped working for me:
~$ gksu gparted
(gpartedbin:24252): Gtk-WARNING **: cannot open display: :0
The same happens with gparted-pkexec:
~$ gparted-pkexec
No protocol specified
(gpartedbin:25454): Gtk-WARNING **: cannot open display: :0
What could possibly be causing this?
I am not running this through SSH or VNC. This is localhost in a normal terminal window.
xorg sudo gtk gksu pkexec
edited Apr 27 '15 at 4:55
Mark Paskal
2,65411827
asked Apr 26 '15 at 16:39
d_inevitabled_inevitable
1,15421635
All of the sudden gksu stopped working for me:
~$ gksu gparted
(gpartedbin:24252): Gtk-WARNING **: cannot open display: :0
The same happens with gparted-pkexec:
~$ gparted-pkexec
No protocol specified
(gpartedbin:25454): Gtk-WARNING **: cannot open display: :0
What could possibly be causing this?
I am not running this through SSH or VNC. This is localhost in a normal terminal window.
xorg sudo gtk gksu pkexec
xorg sudo gtk gksu pkexec
edited Apr 27 '15 at 4:55
Mark Paskal
2,65411827
asked Apr 26 '15 at 16:39
d_inevitabled_inevitable
1,15421635
edited Apr 27 '15 at 4:55
Mark Paskal
2,65411827
asked Apr 26 '15 at 16:39
d_inevitabled_inevitable
1,15421635
edited Apr 27 '15 at 4:55
Mark Paskal
2,65411827
edited Apr 27 '15 at 4:55
Mark Paskal
2,65411827
edited Apr 27 '15 at 4:55
Mark Paskal
2,65411827
2,65411827
asked Apr 26 '15 at 16:39
d_inevitabled_inevitable
1,15421635
asked Apr 26 '15 at 16:39
d_inevitabled_inevitable
1,15421635
asked Apr 26 '15 at 16:39
d_inevitabled_inevitable
1,15421635
1,15421635
You do not work in a graphical user interface or trying to run a program on a system (eg. via ssh) that no graphical interface provides.
– A.B.
Apr 26 '15 at 16:50
@A.B. I should clarify that this is not via ssh. It's on local host in a very normal terminal window. Infact opening gparted from the application menu has the same result.
– d_inevitable
Apr 26 '15 at 16:53
You shouldn't have to usegksuto run GParted.gparteduses polkit to get elevated privileges.
– muru
Apr 26 '15 at 16:59
@muru when I rungpartedwithoutgksuI getRoot privileges are required for running gparted.
– d_inevitable
Apr 26 '15 at 17:17
Ok, trygparted-pkexec(withoutgksu) orgksu gpartedbin.
– muru
Apr 26 '15 at 17:39
|
show 3 more comments
You do not work in a graphical user interface or trying to run a program on a system (eg. via ssh) that no graphical interface provides.
– A.B.
Apr 26 '15 at 16:50
@A.B. I should clarify that this is not via ssh. It's on local host in a very normal terminal window. Infact opening gparted from the application menu has the same result.
– d_inevitable
Apr 26 '15 at 16:53
You shouldn't have to usegksuto run GParted.gparteduses polkit to get elevated privileges.
– muru
Apr 26 '15 at 16:59
@muru when I rungpartedwithoutgksuI getRoot privileges are required for running gparted.
– d_inevitable
Apr 26 '15 at 17:17
Ok, trygparted-pkexec(withoutgksu) orgksu gpartedbin.
– muru
Apr 26 '15 at 17:39
You do not work in a graphical user interface or trying to run a program on a system (eg. via ssh) that no graphical interface provides.
– A.B.
Apr 26 '15 at 16:50
You do not work in a graphical user interface or trying to run a program on a system (eg. via ssh) that no graphical interface provides.
– A.B.
Apr 26 '15 at 16:50
@A.B. I should clarify that this is not via ssh. It's on local host in a very normal terminal window. Infact opening gparted from the application menu has the same result.
– d_inevitable
Apr 26 '15 at 16:53
@A.B. I should clarify that this is not via ssh. It's on local host in a very normal terminal window. Infact opening gparted from the application menu has the same result.
– d_inevitable
Apr 26 '15 at 16:53
You shouldn't have to use
gksu to run GParted. gparted uses polkit to get elevated privileges.– muru
Apr 26 '15 at 16:59
You shouldn't have to use
gksu to run GParted. gparted uses polkit to get elevated privileges.– muru
Apr 26 '15 at 16:59
@muru when I run
gparted without gksu I get Root privileges are required for running gparted.– d_inevitable
Apr 26 '15 at 17:17
@muru when I run
gparted without gksu I get Root privileges are required for running gparted.– d_inevitable
Apr 26 '15 at 17:17
Ok, try
gparted-pkexec (without gksu) or gksu gpartedbin.– muru
Apr 26 '15 at 17:39
Ok, try
gparted-pkexec (without gksu) or gksu gpartedbin.– muru
Apr 26 '15 at 17:39
|
show 3 more comments
3 Answers
3
active
oldest
votes
If running Ubuntu 17.10 or newer, this issue can arise when an application has not been updated with full support for Wayland. As a workaround until the application is updated, you can run
xhost +SI:localuser:root
which will allow the root user to display applications on your desktop. Also see this Q&A for other possible workarounds: Why don't gksu/gksudo or launching a graphical application with sudo work with Wayland?
source
edited Feb 21 '18 at 0:19
pomsky
31.3k1194127
answered Nov 29 '17 at 15:59
Cutton EyeCutton Eye
666310
@MDMower Thx for editing, learned something new =)!
– Cutton Eye
Dec 15 '17 at 7:46
@pomsky Thx for adding the link ;)!
– Cutton Eye
Feb 26 '18 at 10:49
In 18.04 X-Org will be used again as default. So this problem should vanis then. see
– Cutton Eye
Mar 7 '18 at 13:25
add a comment |
Try running xhost +localhost in your terminal, and then running the command again. This lets all users on your system (i.e. root) open windows on your screen. Make sure to use +localhost and not simply +, as it's more secure to allow connections from only localhost than from anywhere.
To make this permanent, edit the ~/.xinitrc file like this:
Run gedit ~/.xinitrc
Edit the file to look like this (it should be empty at the start):
#! /bin/bash
xhost +localhost &
Now save the file, log out and log in. Now everything should run just fine with sudo.
I can't reproduce your problem on 14.04, but this has worked for me in the past when sudo / gksu threw this error.
Sources:
- http://www.nikhef.nl/~mjg/xhost_plus.html
- https://forums.opensuse.org/showthread.php/405624-sudo-doesnt-open-X-programs
- https://wiki.ubuntu.com/CustomXSession
edited Feb 19 '17 at 4:26
wjandrea
9,23342563
answered Apr 26 '15 at 23:08
Mark PaskalMark Paskal
2,65411827
1
This does work indeed. So does that mean its an access control restriction? Any ideas what the cause of this could be?
– d_inevitable
Apr 27 '15 at 22:21
Yes, it's a security feature of X. It allows only connections from your user to the xserver until told otherwise, I think. I'm not super sure why it's required for some apps and not others, and I don't have a clue why it would be doing it for gparted of all things. Perhaps you were tinkering and tightened security somewhere?
– Mark Paskal
May 4 '15 at 0:16
2
This yields an error: xhost: unable to open display ""
– IgorGanapolsky
Jan 30 '17 at 18:33
5
On redis, it was suggested to usexhost +local:. After that I was able to launch gparted from the terminal, but usingxhost +localhostdidn't work.
– rmin
Sep 6 '17 at 1:40
1
Indeed!xhost +local:fixed mine! It yieldsnon-network local connections being added to access control listwhich is what is needed.
– lobner
Nov 10 '17 at 8:16
|
show 5 more comments
Execute the following in your terminal:
nano /home/user/.bashrc # user = name of your user
Add the following line at the end.
export XAUTHORITY=$HOME/.Xauthority
edited Aug 26 '18 at 8:00
Ben Creasy
1249
answered Apr 23 '18 at 2:05
Wilder Hernández GarcíaWilder Hernández García
411
1
Would be useful if you could add some explanation of how this solves the problem, and whether it has any adverse side effects?
– Geoff
Jan 1 at 23:25
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/3.0/"u003ecc by-sa 3.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%2f614387%2fgksu-gtk-warning-cannot-open-display-0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
If running Ubuntu 17.10 or newer, this issue can arise when an application has not been updated with full support for Wayland. As a workaround until the application is updated, you can run
xhost +SI:localuser:root
which will allow the root user to display applications on your desktop. Also see this Q&A for other possible workarounds: Why don't gksu/gksudo or launching a graphical application with sudo work with Wayland?
source
edited Feb 21 '18 at 0:19
pomsky
31.3k1194127
answered Nov 29 '17 at 15:59
Cutton EyeCutton Eye
666310
@MDMower Thx for editing, learned something new =)!
– Cutton Eye
Dec 15 '17 at 7:46
@pomsky Thx for adding the link ;)!
– Cutton Eye
Feb 26 '18 at 10:49
In 18.04 X-Org will be used again as default. So this problem should vanis then. see
– Cutton Eye
Mar 7 '18 at 13:25
add a comment |
If running Ubuntu 17.10 or newer, this issue can arise when an application has not been updated with full support for Wayland. As a workaround until the application is updated, you can run
xhost +SI:localuser:root
which will allow the root user to display applications on your desktop. Also see this Q&A for other possible workarounds: Why don't gksu/gksudo or launching a graphical application with sudo work with Wayland?
source
edited Feb 21 '18 at 0:19
pomsky
31.3k1194127
answered Nov 29 '17 at 15:59
Cutton EyeCutton Eye
666310
@MDMower Thx for editing, learned something new =)!
– Cutton Eye
Dec 15 '17 at 7:46
@pomsky Thx for adding the link ;)!
– Cutton Eye
Feb 26 '18 at 10:49
In 18.04 X-Org will be used again as default. So this problem should vanis then. see
– Cutton Eye
Mar 7 '18 at 13:25
add a comment |
If running Ubuntu 17.10 or newer, this issue can arise when an application has not been updated with full support for Wayland. As a workaround until the application is updated, you can run
xhost +SI:localuser:root
which will allow the root user to display applications on your desktop. Also see this Q&A for other possible workarounds: Why don't gksu/gksudo or launching a graphical application with sudo work with Wayland?
source
edited Feb 21 '18 at 0:19
pomsky
31.3k1194127
answered Nov 29 '17 at 15:59
Cutton EyeCutton Eye
666310
If running Ubuntu 17.10 or newer, this issue can arise when an application has not been updated with full support for Wayland. As a workaround until the application is updated, you can run
xhost +SI:localuser:root
which will allow the root user to display applications on your desktop. Also see this Q&A for other possible workarounds: Why don't gksu/gksudo or launching a graphical application with sudo work with Wayland?
source
edited Feb 21 '18 at 0:19
pomsky
31.3k1194127
answered Nov 29 '17 at 15:59
Cutton EyeCutton Eye
666310
edited Feb 21 '18 at 0:19
pomsky
31.3k1194127
edited Feb 21 '18 at 0:19
pomsky
31.3k1194127
edited Feb 21 '18 at 0:19
pomsky
31.3k1194127
31.3k1194127
answered Nov 29 '17 at 15:59
Cutton EyeCutton Eye
666310
answered Nov 29 '17 at 15:59
Cutton EyeCutton Eye
666310
answered Nov 29 '17 at 15:59
Cutton EyeCutton Eye
666310
666310
@MDMower Thx for editing, learned something new =)!
– Cutton Eye
Dec 15 '17 at 7:46
@pomsky Thx for adding the link ;)!
– Cutton Eye
Feb 26 '18 at 10:49
In 18.04 X-Org will be used again as default. So this problem should vanis then. see
– Cutton Eye
Mar 7 '18 at 13:25
add a comment |
@MDMower Thx for editing, learned something new =)!
– Cutton Eye
Dec 15 '17 at 7:46
@pomsky Thx for adding the link ;)!
– Cutton Eye
Feb 26 '18 at 10:49
In 18.04 X-Org will be used again as default. So this problem should vanis then. see
– Cutton Eye
Mar 7 '18 at 13:25
@MDMower Thx for editing, learned something new =)!
– Cutton Eye
Dec 15 '17 at 7:46
@MDMower Thx for editing, learned something new =)!
– Cutton Eye
Dec 15 '17 at 7:46
@pomsky Thx for adding the link ;)!
– Cutton Eye
Feb 26 '18 at 10:49
@pomsky Thx for adding the link ;)!
– Cutton Eye
Feb 26 '18 at 10:49
In 18.04 X-Org will be used again as default. So this problem should vanis then. see
– Cutton Eye
Mar 7 '18 at 13:25
In 18.04 X-Org will be used again as default. So this problem should vanis then. see
– Cutton Eye
Mar 7 '18 at 13:25
add a comment |
Try running xhost +localhost in your terminal, and then running the command again. This lets all users on your system (i.e. root) open windows on your screen. Make sure to use +localhost and not simply +, as it's more secure to allow connections from only localhost than from anywhere.
To make this permanent, edit the ~/.xinitrc file like this:
Run gedit ~/.xinitrc
Edit the file to look like this (it should be empty at the start):
#! /bin/bash
xhost +localhost &
Now save the file, log out and log in. Now everything should run just fine with sudo.
I can't reproduce your problem on 14.04, but this has worked for me in the past when sudo / gksu threw this error.
Sources:
- http://www.nikhef.nl/~mjg/xhost_plus.html
- https://forums.opensuse.org/showthread.php/405624-sudo-doesnt-open-X-programs
- https://wiki.ubuntu.com/CustomXSession
edited Feb 19 '17 at 4:26
wjandrea
9,23342563
answered Apr 26 '15 at 23:08
Mark PaskalMark Paskal
2,65411827
1
This does work indeed. So does that mean its an access control restriction? Any ideas what the cause of this could be?
– d_inevitable
Apr 27 '15 at 22:21
Yes, it's a security feature of X. It allows only connections from your user to the xserver until told otherwise, I think. I'm not super sure why it's required for some apps and not others, and I don't have a clue why it would be doing it for gparted of all things. Perhaps you were tinkering and tightened security somewhere?
– Mark Paskal
May 4 '15 at 0:16
2
This yields an error: xhost: unable to open display ""
– IgorGanapolsky
Jan 30 '17 at 18:33
5
On redis, it was suggested to usexhost +local:. After that I was able to launch gparted from the terminal, but usingxhost +localhostdidn't work.
– rmin
Sep 6 '17 at 1:40
1
Indeed!xhost +local:fixed mine! It yieldsnon-network local connections being added to access control listwhich is what is needed.
– lobner
Nov 10 '17 at 8:16
|
show 5 more comments
Try running xhost +localhost in your terminal, and then running the command again. This lets all users on your system (i.e. root) open windows on your screen. Make sure to use +localhost and not simply +, as it's more secure to allow connections from only localhost than from anywhere.
To make this permanent, edit the ~/.xinitrc file like this:
Run gedit ~/.xinitrc
Edit the file to look like this (it should be empty at the start):
#! /bin/bash
xhost +localhost &
Now save the file, log out and log in. Now everything should run just fine with sudo.
I can't reproduce your problem on 14.04, but this has worked for me in the past when sudo / gksu threw this error.
Sources:
- http://www.nikhef.nl/~mjg/xhost_plus.html
- https://forums.opensuse.org/showthread.php/405624-sudo-doesnt-open-X-programs
- https://wiki.ubuntu.com/CustomXSession
edited Feb 19 '17 at 4:26
wjandrea
9,23342563
answered Apr 26 '15 at 23:08
Mark PaskalMark Paskal
2,65411827
1
This does work indeed. So does that mean its an access control restriction? Any ideas what the cause of this could be?
– d_inevitable
Apr 27 '15 at 22:21
Yes, it's a security feature of X. It allows only connections from your user to the xserver until told otherwise, I think. I'm not super sure why it's required for some apps and not others, and I don't have a clue why it would be doing it for gparted of all things. Perhaps you were tinkering and tightened security somewhere?
– Mark Paskal
May 4 '15 at 0:16
2
This yields an error: xhost: unable to open display ""
– IgorGanapolsky
Jan 30 '17 at 18:33
5
On redis, it was suggested to usexhost +local:. After that I was able to launch gparted from the terminal, but usingxhost +localhostdidn't work.
– rmin
Sep 6 '17 at 1:40
1
Indeed!xhost +local:fixed mine! It yieldsnon-network local connections being added to access control listwhich is what is needed.
– lobner
Nov 10 '17 at 8:16
|
show 5 more comments
Try running xhost +localhost in your terminal, and then running the command again. This lets all users on your system (i.e. root) open windows on your screen. Make sure to use +localhost and not simply +, as it's more secure to allow connections from only localhost than from anywhere.
To make this permanent, edit the ~/.xinitrc file like this:
Run gedit ~/.xinitrc
Edit the file to look like this (it should be empty at the start):
#! /bin/bash
xhost +localhost &
Now save the file, log out and log in. Now everything should run just fine with sudo.
I can't reproduce your problem on 14.04, but this has worked for me in the past when sudo / gksu threw this error.
Sources:
- http://www.nikhef.nl/~mjg/xhost_plus.html
- https://forums.opensuse.org/showthread.php/405624-sudo-doesnt-open-X-programs
- https://wiki.ubuntu.com/CustomXSession
edited Feb 19 '17 at 4:26
wjandrea
9,23342563
answered Apr 26 '15 at 23:08
Mark PaskalMark Paskal
2,65411827
Try running xhost +localhost in your terminal, and then running the command again. This lets all users on your system (i.e. root) open windows on your screen. Make sure to use +localhost and not simply +, as it's more secure to allow connections from only localhost than from anywhere.
To make this permanent, edit the ~/.xinitrc file like this:
Run gedit ~/.xinitrc
Edit the file to look like this (it should be empty at the start):
#! /bin/bash
xhost +localhost &
Now save the file, log out and log in. Now everything should run just fine with sudo.
I can't reproduce your problem on 14.04, but this has worked for me in the past when sudo / gksu threw this error.
Sources:
- http://www.nikhef.nl/~mjg/xhost_plus.html
- https://forums.opensuse.org/showthread.php/405624-sudo-doesnt-open-X-programs
- https://wiki.ubuntu.com/CustomXSession
edited Feb 19 '17 at 4:26
wjandrea
9,23342563
answered Apr 26 '15 at 23:08
Mark PaskalMark Paskal
2,65411827
edited Feb 19 '17 at 4:26
wjandrea
9,23342563
edited Feb 19 '17 at 4:26
wjandrea
9,23342563
edited Feb 19 '17 at 4:26
wjandrea
9,23342563
9,23342563
answered Apr 26 '15 at 23:08
Mark PaskalMark Paskal
2,65411827
answered Apr 26 '15 at 23:08
Mark PaskalMark Paskal
2,65411827
answered Apr 26 '15 at 23:08
Mark PaskalMark Paskal
2,65411827
2,65411827
1
This does work indeed. So does that mean its an access control restriction? Any ideas what the cause of this could be?
– d_inevitable
Apr 27 '15 at 22:21
Yes, it's a security feature of X. It allows only connections from your user to the xserver until told otherwise, I think. I'm not super sure why it's required for some apps and not others, and I don't have a clue why it would be doing it for gparted of all things. Perhaps you were tinkering and tightened security somewhere?
– Mark Paskal
May 4 '15 at 0:16
2
This yields an error: xhost: unable to open display ""
– IgorGanapolsky
Jan 30 '17 at 18:33
5
On redis, it was suggested to usexhost +local:. After that I was able to launch gparted from the terminal, but usingxhost +localhostdidn't work.
– rmin
Sep 6 '17 at 1:40
1
Indeed!xhost +local:fixed mine! It yieldsnon-network local connections being added to access control listwhich is what is needed.
– lobner
Nov 10 '17 at 8:16
|
show 5 more comments
1
This does work indeed. So does that mean its an access control restriction? Any ideas what the cause of this could be?
– d_inevitable
Apr 27 '15 at 22:21
Yes, it's a security feature of X. It allows only connections from your user to the xserver until told otherwise, I think. I'm not super sure why it's required for some apps and not others, and I don't have a clue why it would be doing it for gparted of all things. Perhaps you were tinkering and tightened security somewhere?
– Mark Paskal
May 4 '15 at 0:16
2
This yields an error: xhost: unable to open display ""
– IgorGanapolsky
Jan 30 '17 at 18:33
5
On redis, it was suggested to usexhost +local:. After that I was able to launch gparted from the terminal, but usingxhost +localhostdidn't work.
– rmin
Sep 6 '17 at 1:40
1
Indeed!xhost +local:fixed mine! It yieldsnon-network local connections being added to access control listwhich is what is needed.
– lobner
Nov 10 '17 at 8:16
1
1
This does work indeed. So does that mean its an access control restriction? Any ideas what the cause of this could be?
– d_inevitable
Apr 27 '15 at 22:21
This does work indeed. So does that mean its an access control restriction? Any ideas what the cause of this could be?
– d_inevitable
Apr 27 '15 at 22:21
Yes, it's a security feature of X. It allows only connections from your user to the xserver until told otherwise, I think. I'm not super sure why it's required for some apps and not others, and I don't have a clue why it would be doing it for gparted of all things. Perhaps you were tinkering and tightened security somewhere?
– Mark Paskal
May 4 '15 at 0:16
Yes, it's a security feature of X. It allows only connections from your user to the xserver until told otherwise, I think. I'm not super sure why it's required for some apps and not others, and I don't have a clue why it would be doing it for gparted of all things. Perhaps you were tinkering and tightened security somewhere?
– Mark Paskal
May 4 '15 at 0:16
2
2
This yields an error: xhost: unable to open display ""
– IgorGanapolsky
Jan 30 '17 at 18:33
This yields an error: xhost: unable to open display ""
– IgorGanapolsky
Jan 30 '17 at 18:33
5
5
On redis, it was suggested to use
xhost +local:. After that I was able to launch gparted from the terminal, but using xhost +localhost didn't work.– rmin
Sep 6 '17 at 1:40
On redis, it was suggested to use
xhost +local:. After that I was able to launch gparted from the terminal, but using xhost +localhost didn't work.– rmin
Sep 6 '17 at 1:40
1
1
Indeed!
xhost +local: fixed mine! It yields non-network local connections being added to access control list which is what is needed.– lobner
Nov 10 '17 at 8:16
Indeed!
xhost +local: fixed mine! It yields non-network local connections being added to access control list which is what is needed.– lobner
Nov 10 '17 at 8:16
|
show 5 more comments
Execute the following in your terminal:
nano /home/user/.bashrc # user = name of your user
Add the following line at the end.
export XAUTHORITY=$HOME/.Xauthority
edited Aug 26 '18 at 8:00
Ben Creasy
1249
answered Apr 23 '18 at 2:05
Wilder Hernández GarcíaWilder Hernández García
411
1
Would be useful if you could add some explanation of how this solves the problem, and whether it has any adverse side effects?
– Geoff
Jan 1 at 23:25
add a comment |
Execute the following in your terminal:
nano /home/user/.bashrc # user = name of your user
Add the following line at the end.
export XAUTHORITY=$HOME/.Xauthority
edited Aug 26 '18 at 8:00
Ben Creasy
1249
answered Apr 23 '18 at 2:05
Wilder Hernández GarcíaWilder Hernández García
411
1
Would be useful if you could add some explanation of how this solves the problem, and whether it has any adverse side effects?
– Geoff
Jan 1 at 23:25
add a comment |
Execute the following in your terminal:
nano /home/user/.bashrc # user = name of your user
Add the following line at the end.
export XAUTHORITY=$HOME/.Xauthority
edited Aug 26 '18 at 8:00
Ben Creasy
1249
answered Apr 23 '18 at 2:05
Wilder Hernández GarcíaWilder Hernández García
411
Execute the following in your terminal:
nano /home/user/.bashrc # user = name of your user
Add the following line at the end.
export XAUTHORITY=$HOME/.Xauthority
edited Aug 26 '18 at 8:00
Ben Creasy
1249
answered Apr 23 '18 at 2:05
Wilder Hernández GarcíaWilder Hernández García
411
edited Aug 26 '18 at 8:00
Ben Creasy
1249
edited Aug 26 '18 at 8:00
Ben Creasy
1249
edited Aug 26 '18 at 8:00
Ben Creasy
1249
1249
answered Apr 23 '18 at 2:05
Wilder Hernández GarcíaWilder Hernández García
411
answered Apr 23 '18 at 2:05
Wilder Hernández GarcíaWilder Hernández García
411
answered Apr 23 '18 at 2:05
Wilder Hernández GarcíaWilder Hernández García
411
411
1
Would be useful if you could add some explanation of how this solves the problem, and whether it has any adverse side effects?
– Geoff
Jan 1 at 23:25
add a comment |
1
Would be useful if you could add some explanation of how this solves the problem, and whether it has any adverse side effects?
– Geoff
Jan 1 at 23:25
1
1
Would be useful if you could add some explanation of how this solves the problem, and whether it has any adverse side effects?
– Geoff
Jan 1 at 23:25
Would be useful if you could add some explanation of how this solves the problem, and whether it has any adverse side effects?
– Geoff
Jan 1 at 23:25
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%2f614387%2fgksu-gtk-warning-cannot-open-display-0%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
You do not work in a graphical user interface or trying to run a program on a system (eg. via ssh) that no graphical interface provides.
– A.B.
Apr 26 '15 at 16:50
@A.B. I should clarify that this is not via ssh. It's on local host in a very normal terminal window. Infact opening gparted from the application menu has the same result.
– d_inevitable
Apr 26 '15 at 16:53
You shouldn't have to use
gksuto run GParted.gparteduses polkit to get elevated privileges.– muru
Apr 26 '15 at 16:59
@muru when I run
gpartedwithoutgksuI getRoot privileges are required for running gparted.– d_inevitable
Apr 26 '15 at 17:17
Ok, try
gparted-pkexec(withoutgksu) orgksu gpartedbin.– muru
Apr 26 '15 at 17:39