Autolaunch Error X11 Initialization Failed. Cannot Open Display
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
Gedit Cannot Open Display Ubuntu
Overflow the company Business Learn more about hiring developers or posting ads with us gedit cannot open display putty Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and
Sudo Gedit Cannot Open Display
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 Cannot connect to X gedit cannot open display ssh Server when running app with sudo up vote 11 down vote favorite 5 When I am running some software using sudo command it showing error like cannot connect to X server For example if I run the following command: $ sudo gedit /etc/profile I am getting following command (gedit:6758): WARNING **: Command line `dbus-launch --autolaunch=84b871d735f31ffe014dc9ba00000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed. Cannot open display: Run 'gedit sudo gedit /etc/hosts --help' to see a full list of available command line options. Or if I am running super-boot-manager I am getting following error buc: cannot connect to X server Please help. display sudo xserver share|improve this question edited Aug 14 '12 at 8:17 Peachy 4,08252637 asked Aug 14 '12 at 7:32 Apurba 5812720 Where do you run super-boot-manger from? –Thor Aug 15 '12 at 9:49 First I have tried to run super-boot-manager directly from unity luncher, it did not worked. Then I have tried it from terminal, then I got those error massage. –Apurba Aug 15 '12 at 13:21 As in a terminal within the graphical user environment? What does: echo $DISPLAY say? You should run it without sudo as super-boot-manager runs sudo internally. –Thor Aug 15 '12 at 15:23 echo $DISPLAY is giving :0.0. And I am not running super-boot-manager as sudo. I am running just using command super-boot-manager from terminal. –Apurba Aug 16 '12 at 19:36 1 Finally the problem is solved. I have just added the line: Defaults env_keep="DISPLAY XAUTHORITY" at the end of visudo. Thanks to all, specially @Thor for kind help. –Apurba Aug 17 '12 at 8:03 | show 4 more comments 2 Answers 2 active oldest votes up vote 18 down vote acc
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
Gedit No Protocol Specified
workings and policies of this site About Us Learn more about Stack gedit gtk warning cannot open display Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags
Sudo Gedit Command Not Found
Users Badges Unanswered Ask Question _ Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how http://askubuntu.com/questions/175611/cannot-connect-to-x-server-when-running-app-with-sudo it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Unable to launch gedit with sudo up vote 2 down vote favorite While trying to follow these instructions, I encountered the following error while attempting what seems like a simple sudo edit operation: $ sudo gedit /var/lib/dpkg/status ** (gedit:14898): WARNING http://askubuntu.com/questions/216671/unable-to-launch-gedit-with-sudo **: Command line `dbus-launch --autolaunch=0bd873023a78bdb34ca1b9650000000b --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n Cannot open display: Run 'gedit --help' to see a full list of available command line options. Running the same without sudo correctly launches gedit, but of course without editing ability. Does anyone have any idea what is going on? sudo gedit x11 share|improve this question asked Nov 13 '12 at 13:17 Bill Cheatham 3002919 A quick workaround would be to use a console-based editor such as nano or vim, which should work without complications. I'm unsure what is causing the error - I had assumed DISPLAY was unset but testing this gives me a different error. –chronitis Nov 13 '12 at 13:30 And moral of the story is to stick with documentation from known sources such as help.ubuntu.com/community –user25656 Nov 13 '12 at 14:15 @vasa1 how is that the moral of the story? Regardless of the merits of following random instructions from the internet, /var/lib/dpkg/status is a file which I should be able to edit with gedit
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and http://superuser.com/questions/310197/how-do-i-fix-a-cannot-open-display-error-when-opening-an-x-program-after-sshi policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered https://www.raspberrypi.org/forums/viewtopic.php?t=61175&p=455573 Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: cannot open Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How do I fix a “cannot open display” error when opening an X program after ssh'ing with X11 forwarding enabled? up vote 50 down vote favorite 22 After launching the X11 app (XQuartz 2.3.6, xorg-server 1.4.2-apple56) on my Mac (OS X 10.6.8), opening cannot open display an terminal in X11 and running xhost +, I then ssh -Y to my Ubuntu 10.04 VM (running on VMware Fusion). When I run gedit .bashrc (for example), I get: (gedit:9510): Gtk-WARNING **: cannot open display: set | grep DISPLAY returns nothing. But if I ssh -Y into my Ubuntu 11.04 machine, gedit .bashrc works. echo $DISPLAY returns "localhost:10.0". I tried export DISPLAY=localhost:10.0 while sshed into my VM and then running gedit .bashrc, but I get: (gedit:9625): Gtk-WARNING **: cannot open display: localhost:10.0 What could be different in the configuration of the two difference Ubuntu machines that would explain why one works and the other doesn't? Update: As suggested by Zoredache in the comment below, I ran sudo apt-get install xbase-clients, but I continue to have the same problem. ssh display xorg gtk share|improve this question edited Feb 9 '14 at 12:20 Pablo Saratxaga 1133 asked Jul 13 '11 at 18:13 Daryl Spitzer 2,91893236 migrated from serverfault.com Jul 13 '11 at 18:31 This question came from our site for system and network administrators. 2 Does the Ubuntu 10.04 box have the proper tools
reply 4 posts by morphy_richards » Mon Nov 18, 2013 12:36 pm This may just be a general misunderstanding on my part ... I'm still pretty much a noob in many respects.I have some raspberry pis on a network along with an Edubuntu server. My edubuntu server has some programs such as GIMP etc which are not on my raspberry pis.I had imagined I would be able to ssh to my server and run those applications from there...Trying to test it just using gedit... (gedit on server but not r-pi)eg.Code: Select allssh -x test1@lovelace.computing.lan
test1@lovelace:~$ gedit
** (gedit:20717): WARNING **: Command line `dbus-launch --autolaunch=53cabe170503663352e9802300000009 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n
Cannot open display:
Run 'gedit --help' to see a full list of available command line options.
test1@lovelace:~$
test1@lovelace:~$ xeyes
Error: Can't open display:
test1@lovelace:~$
I have set x11 forwarding to yes in the server /etc/ssh/ssh_config file. Posts: 1572Joined: Mon Mar 05, 2012 3:26 pmLocation: Epping Forest by DeeJay » Mon Nov 18, 2013 1:58 pm On the right track, but from reading man ssh: -x Disables X11 forwarding.Code: Select allssh -X test1@lovelace.computing.lan might be what you need? How To Ask Questions The Smart Way: http://www.catb.org/~esr/faqs/smart-questions.htmlHow to Report Bugs Effectively: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Posts: 2027Joined: Tue Jan 01, 2013 9:33 pmLocation: East Midlands, UK by Joe Schmoe » Mon Nov 18, 2013 2:26 pm (heh heh - of course I can't replicate it now...)(And note that this may not be directly related to OP's problem; the old tl;dr applies. But it sounds similar to what he was talking about...)I have noticed that when I do:Code: Select allssh -X pi@192.168.pi.IPaddr(on my Mac)Sometimes it works, but sometimes it generates an error message ab