Cant open X server on local machine












0















I'm trying to open GUI installation from shell without success so I tried first to open just xclock but was unable as well. usually export to DISPLAY solved the problem. I have a haunch that it security related but I lack the right knowledge to debug it.



[grid@localhost grid122]$ export DISPLAY=:0
[grid@localhost grid122]$ xclock
No protocol specified
Error: Can't open display: :0
[grid@localhost grid122]$ export DISPLAY=localhost:0
[grid@localhost grid122]$ xclock
Error: Can't open display: localhost:0


Tried different addresses as well:



localhost:0.0
127.0.0.1:0
127.0.0.1:0.0


Also modify /etc/hosts.allow didn't work.



I'm using CentOS 7 with GNOME










share|improve this question




















  • 1





    are you logged in as the same user as the one who opened the GUI / Gnome?

    – Jeff Schaller
    Jun 4 '17 at 17:06






  • 1





    related: unix.stackexchange.com/questions/10121/…

    – Jeff Schaller
    Jun 4 '17 at 17:07











  • it is different user than the one I logged in. I'll check the authority you send and report back

    – Nir
    Jun 4 '17 at 23:13
















0















I'm trying to open GUI installation from shell without success so I tried first to open just xclock but was unable as well. usually export to DISPLAY solved the problem. I have a haunch that it security related but I lack the right knowledge to debug it.



[grid@localhost grid122]$ export DISPLAY=:0
[grid@localhost grid122]$ xclock
No protocol specified
Error: Can't open display: :0
[grid@localhost grid122]$ export DISPLAY=localhost:0
[grid@localhost grid122]$ xclock
Error: Can't open display: localhost:0


Tried different addresses as well:



localhost:0.0
127.0.0.1:0
127.0.0.1:0.0


Also modify /etc/hosts.allow didn't work.



I'm using CentOS 7 with GNOME










share|improve this question




















  • 1





    are you logged in as the same user as the one who opened the GUI / Gnome?

    – Jeff Schaller
    Jun 4 '17 at 17:06






  • 1





    related: unix.stackexchange.com/questions/10121/…

    – Jeff Schaller
    Jun 4 '17 at 17:07











  • it is different user than the one I logged in. I'll check the authority you send and report back

    – Nir
    Jun 4 '17 at 23:13














0












0








0








I'm trying to open GUI installation from shell without success so I tried first to open just xclock but was unable as well. usually export to DISPLAY solved the problem. I have a haunch that it security related but I lack the right knowledge to debug it.



[grid@localhost grid122]$ export DISPLAY=:0
[grid@localhost grid122]$ xclock
No protocol specified
Error: Can't open display: :0
[grid@localhost grid122]$ export DISPLAY=localhost:0
[grid@localhost grid122]$ xclock
Error: Can't open display: localhost:0


Tried different addresses as well:



localhost:0.0
127.0.0.1:0
127.0.0.1:0.0


Also modify /etc/hosts.allow didn't work.



I'm using CentOS 7 with GNOME










share|improve this question
















I'm trying to open GUI installation from shell without success so I tried first to open just xclock but was unable as well. usually export to DISPLAY solved the problem. I have a haunch that it security related but I lack the right knowledge to debug it.



[grid@localhost grid122]$ export DISPLAY=:0
[grid@localhost grid122]$ xclock
No protocol specified
Error: Can't open display: :0
[grid@localhost grid122]$ export DISPLAY=localhost:0
[grid@localhost grid122]$ xclock
Error: Can't open display: localhost:0


Tried different addresses as well:



localhost:0.0
127.0.0.1:0
127.0.0.1:0.0


Also modify /etc/hosts.allow didn't work.



I'm using CentOS 7 with GNOME







centos x11 x-server






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 4 '17 at 17:02









Jeff Schaller

39.3k1054125




39.3k1054125










asked Jun 4 '17 at 16:50









NirNir

44521020




44521020








  • 1





    are you logged in as the same user as the one who opened the GUI / Gnome?

    – Jeff Schaller
    Jun 4 '17 at 17:06






  • 1





    related: unix.stackexchange.com/questions/10121/…

    – Jeff Schaller
    Jun 4 '17 at 17:07











  • it is different user than the one I logged in. I'll check the authority you send and report back

    – Nir
    Jun 4 '17 at 23:13














  • 1





    are you logged in as the same user as the one who opened the GUI / Gnome?

    – Jeff Schaller
    Jun 4 '17 at 17:06






  • 1





    related: unix.stackexchange.com/questions/10121/…

    – Jeff Schaller
    Jun 4 '17 at 17:07











  • it is different user than the one I logged in. I'll check the authority you send and report back

    – Nir
    Jun 4 '17 at 23:13








1




1





are you logged in as the same user as the one who opened the GUI / Gnome?

– Jeff Schaller
Jun 4 '17 at 17:06





are you logged in as the same user as the one who opened the GUI / Gnome?

– Jeff Schaller
Jun 4 '17 at 17:06




1




1





related: unix.stackexchange.com/questions/10121/…

– Jeff Schaller
Jun 4 '17 at 17:07





related: unix.stackexchange.com/questions/10121/…

– Jeff Schaller
Jun 4 '17 at 17:07













it is different user than the one I logged in. I'll check the authority you send and report back

– Nir
Jun 4 '17 at 23:13





it is different user than the one I logged in. I'll check the authority you send and report back

– Nir
Jun 4 '17 at 23:13










1 Answer
1






active

oldest

votes


















-1














Answer found here once I understand the problem - I can start xclock from the user I logged in but not from other users.
Solution was running xhost + from the user I logged into.



Funny thing is I did xhost + numerous times before.






share|improve this answer
























  • That's a terrible solution unless you are absolutely totally sure your X Server can't be accessed remotely (directly on port 6000 or indirectly by someone logging in to your machine remotely).

    – roaima
    Jan 11 at 8:12













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f369169%2fcant-open-x-server-on-local-machine%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









-1














Answer found here once I understand the problem - I can start xclock from the user I logged in but not from other users.
Solution was running xhost + from the user I logged into.



Funny thing is I did xhost + numerous times before.






share|improve this answer
























  • That's a terrible solution unless you are absolutely totally sure your X Server can't be accessed remotely (directly on port 6000 or indirectly by someone logging in to your machine remotely).

    – roaima
    Jan 11 at 8:12


















-1














Answer found here once I understand the problem - I can start xclock from the user I logged in but not from other users.
Solution was running xhost + from the user I logged into.



Funny thing is I did xhost + numerous times before.






share|improve this answer
























  • That's a terrible solution unless you are absolutely totally sure your X Server can't be accessed remotely (directly on port 6000 or indirectly by someone logging in to your machine remotely).

    – roaima
    Jan 11 at 8:12
















-1












-1








-1







Answer found here once I understand the problem - I can start xclock from the user I logged in but not from other users.
Solution was running xhost + from the user I logged into.



Funny thing is I did xhost + numerous times before.






share|improve this answer













Answer found here once I understand the problem - I can start xclock from the user I logged in but not from other users.
Solution was running xhost + from the user I logged into.



Funny thing is I did xhost + numerous times before.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jun 5 '17 at 8:55









NirNir

44521020




44521020













  • That's a terrible solution unless you are absolutely totally sure your X Server can't be accessed remotely (directly on port 6000 or indirectly by someone logging in to your machine remotely).

    – roaima
    Jan 11 at 8:12





















  • That's a terrible solution unless you are absolutely totally sure your X Server can't be accessed remotely (directly on port 6000 or indirectly by someone logging in to your machine remotely).

    – roaima
    Jan 11 at 8:12



















That's a terrible solution unless you are absolutely totally sure your X Server can't be accessed remotely (directly on port 6000 or indirectly by someone logging in to your machine remotely).

– roaima
Jan 11 at 8:12







That's a terrible solution unless you are absolutely totally sure your X Server can't be accessed remotely (directly on port 6000 or indirectly by someone logging in to your machine remotely).

– roaima
Jan 11 at 8:12




















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f369169%2fcant-open-x-server-on-local-machine%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

How to make a Squid Proxy server?

第一次世界大戦

Touch on Surface Book