Firefox Cannot Open Display Error
Contents |
communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack error can't open display linux Overflow the company Business Learn more about hiring developers or posting ads with us error can't open display localhost Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and
Xhost Unable To Open Display Linux
developers. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top “Error: cannot open
Error Can't Open Display Localhost 10.0 Putty
display: :0.0” while starting remotelly Firefox up vote 0 down vote favorite On my ubuntu 14.04 remote server, when I try to start Mozilla Firefox 32.0 from terminal, it through error as follow: $ firefox (process:6397): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Error: cannot open display: :0.0 I have tried by changing display to 1, 10, 11, 99, however, no luck! Banging my head from a week. Any help will be cannot open display ubuntu appreciable. firefox ssh share|improve this question edited Sep 13 '14 at 21:30 Braiam 39k1693154 asked Sep 13 '14 at 20:04 RAJ ... 106127 2 When you say remote server, are you connected via ssh? Yre you forwarding X? –Jan Sep 13 '14 at 20:15 Yes, I have ssh to my server. Over there I am trying to start firefox in a same way as I am doing on my local machine i.e. from terminal type firefox and hit ENTER –RAJ ... Sep 13 '14 at 20:24 @Jan Do I need to forward X? I am using watir & headless and watir opening firefox instance programmatically –RAJ ... Sep 13 '14 at 20:41 Never heard of watir but you need to forward X. –Jan Sep 13 '14 at 20:43 how can I do this @Jan? And why I need it only on remote machine. Local machine works without it –RAJ ... Sep 13 '14 at 20:44 | show 1 more comment 1 Answer 1 active oldest votes up vote 2 down vote accepted X11 forwarding needs to be enabled on both the client side and the server side. On the client side, the -X (capital X) option to ssh enables X11 forwarding, and you can make this the defau
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack
Gtk Warning Cannot Open Display Ubuntu
Overflow the company Business Learn more about hiring developers or posting ads with us error can't open display xclock Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site gedit gtk-warning cannot open display for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted http://askubuntu.com/questions/523677/error-cannot-open-display-0-0-while-starting-remotelly-firefox up and rise to the top X “Can't open display: :0” while DISPLAY variable is correct [duplicate] up vote 3 down vote favorite 2 This question already has an answer here: Can I launch a graphical program on another user's desktop as root? 4 answers I'm not able to start any GUI applications as a root user: # pgrep -lf Xorg 1590 /usr/bin/Xorg -br -nolisten tcp :0 vt7 -auth /var/lib/xdm/authdir/authfiles/A:0-PNnJzp # echo $DISPLAY http://unix.stackexchange.com/questions/67111/x-cant-open-display-0-while-display-variable-is-correct :0 # xeyes No protocol specified Error: Can't open display: :0 # firefox No protocol specified No protocol specified Error: cannot open display: :0 # xcalc No protocol specified Error: Can't open display: :0 # Distribution is openSUSE 11.2(2.6.31.5-0.1-default) and X.Org X Server version is 1.6.5. My DISPLAY variable is set correctly, isn't it? Any ideas what might cause this problem? xorg display share|improve this question asked Mar 6 '13 at 8:30 Martin 23782970 migrated from serverfault.com Mar 6 '13 at 21:27 This question came from our site for system and network administrators. marked as duplicate by Gilles, warl0ck, n0pe, jasonwryan, Mat Mar 7 '13 at 5:39 This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question. This isn't really an SF question, and will probably get transferred soon, but you might want to look into the xauth command and see what you can learn about how the X server makes decisions about who should be allowed to perform operations through it. –MadHatter Mar 6 '13 at 8:38 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote :0 should work as should :0.0 (normal default) as also localhost:0 etc. Permissions are most likely prob
Architecture X display manager Reinstallation of X11 and Gnome Desktop in RHEL "init: Id "x" respawning too fast: disabled for 5 minutes." Configuration Fonts in X Exporting_display Xdefaults Using xauth Too high refresh rate ot too high resolution XDMCP vnc Cygwin/X http://www.softpanorama.org/Xwindows/Troubleshooting/can_not_open_display.shtml X11 security Tips History Humor Etc The X Window uses a client/server-architecture (and the server is your workstation to which you are exporting the session). It can use a number of transport protocols, including Unix sockets and TCP/IP sockets. Which mechanism is used, is determined by the format of the DISPLAY environment variable. When DISPLAY does not contain a hostname, e.g. it is set to :0, Unix sockets will be used. When it does contain open display a hostname, e.g. it is set to localhost:0.0, the X client application will try to connect to the server (even localhost as in the example) via TCP/IP sockets X has an authentication mechanism, which decides whether a client is allowed to connect to a server. As the Internet has become an increasingly hostile environment, it has become good practice to only open up services to the Internet when they are really needed. Recently in some cannot open display Linux distributions, X is by default configured to listen only to localhost. That means that default X settings become more and more defensive and thus without tuning there are more and more reasons why remote communications attempts using X initially will fail. That's why the first time you try to run a remote X application on modern Linux distributions, it usually does not work. The most common error message by far is "Can't open display". In this case an X client application, for example xterm, reports an error Can't open display on startup, for instance xterm Xt error: Can't open display: localhost:0.0 The first thing to try is to ensure that you used a correct sequence of commands. One typical mistake is you use like xhost + on the client instead of the server (your workstation). If you have problems the first thing to do is to see the value of the variable DISPLAY on the client. If it is not set at all or set incorrectly you need to fix that, for example export DISPLAY=10.10.10.1:0.0 The second step to check is whether X11 server itself is accessible from the client. If firewall on the server is enables it can block X11 session. You better exclude firewall from the possible causes first. You can see this by using nmap. If port 177 (UDP)