Autolaunch Error X11 Initialization Failed. Vino
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 Overflow the company Business Learn more about hiring vino cannot open display developers or posting ads with us Ask Ubuntu Questions Tags Users Badges Unanswered Ask Question _ Ask
Restart Vino Server Command Line
Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute: Sign up Here's how it failed to commit changes to dconf: error spawning command line 'dbus-launch works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Remote Ubuntu 12.04 desktop cannot display X on local laptop up vote 0 down vote favorite I have an Ubuntu 13.04 laptop and an Ubuntu 12.04 desktop. I want to be able to open and see images, windows, and pdf files that are located on the desktop via remote access from my laptop. When I tried to follow instructions like those at hungry.com, I managed to sudo apt-get install telnetd, xhost +, then access into my desktop using telnet, set and export the DISPLAY variable, and then open a .png file using the eog image.png command, but the image would open up on the remote desktop's screen and NOT on my laptop's screen. I tried changing the DISPLAY variable to the ip address of my laptop followed by :0, but I could only get images to display on the remote desktop. In addition, when I tried to do it the other way around and to access my laptop from my desktop, I got the message WARNING **: Could not open X display. In addition, if I don't have DISPLAY set, xterm terminal says X11 initialization failed Finally I tried to use SSH. First I generated a public and private key, then when I tried to connect using PuTTY with the IP address of the remote desktop and default settings. When I clicked open, it said PuTTY Fatal Error Connection refused: OK. When I tried the terminal command ssh ###.###.##.### (remote desktop IP), ssh said the same thing: ssh: connect to host ###.###.##.### port 22: Connection refused. How do I get the pictures from my desktop to appear on my laptop? For my purposes, I don't care if anyone can intercept and view my homework files. I just want there to be as little lag as possible and to be able to see the remote desktop windows. SSH is too slow, VNC doesn't allow multiple users to view different images, and telnet just won't re-route my image back to the local machine. Look - Telnet only opens in the remote machine (not the local one) reg
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 Overflow the company Business Learn more about hiring developers or posting ads with us Ask Ubuntu Questions Tags 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 it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top gsettings not working over ssh http://askubuntu.com/questions/380503/remote-ubuntu-12-04-desktop-cannot-display-x-on-local-laptop [duplicate] up vote 9 down vote favorite This question already has an answer here: change gsettings without running X and Unity 2 answers I'm trying to change Unity Launcher icons on a remote computer with command: gsettings set com.canonical.Unity.Launcher favorites ... and it works perfectly But when I do ssh 127.0.0.1 gsettings set com.canonical.Unity.Launcher favorites ... I get this: (process:9616): dconf-WARNING **: failed to commit changes to dconf: Error spawning command line `dbus-launch http://askubuntu.com/questions/323776/gsettings-not-working-over-ssh --autolaunch=aaa5bb6eaa7cd50f2af1f10000000004 --binary-syntax --close-stderr': Child process exited with code 1 And that is for any gsettings calls from ssh. Where is the problem? ssh gsettings share|improve this question edited Jul 24 '13 at 9:34 asked Jul 24 '13 at 9:17 Sergey 2562313 marked as duplicate by Jorge Castro, Eric Carvalho, Kevin Bowen, Mitch♦, Radu Rădeanu Jul 31 '13 at 17:50 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. add a comment| 2 Answers 2 active oldest votes up vote 13 down vote accepted I don't think dbus is running in the remote ssh session. You need to start it yourself, but that's pretty easy to do: dbus-launch gsettings set com.canonical.Unity.Launcher favorites ... Also make sure that the user is correct, you can set settings for another user (if that's what you're doing) like this: sudo -u other dbus-launch gsettings set com.canonical.Unity.Launcher favorites ... The above assumes the user you're changing settings for is "other", change as appropriate. share|improve this answer answered Jul 31 '13 at 2:33 mfisch 2,36811536 add a comment| up vote 0 down vote If there is a running dbus / X session belonging to the user, it may be sufficient to set the DISPLAY variable e.g. $ gsettings set org.gnome.desktop.back
Architecture Configuration X display manager XDMCP Exporting_display "Can't open display" Error .Xresources xrdb Using xauth Xdefaults Fonts in X X11 security Xming Cygwin/X vnc vino Troubleshooting Diagnosing problems with remote X11 sessions via http://www.softpanorama.org/Xwindows/VNC/Vino/activating_vino_from_command_line.shtml SSH Installing X11 and Gnome Desktop in RHEL Tips Humor Etc Introduction You http://unix.stackexchange.com/questions/95855/dbus-launch-terminated-abnormally-with-the-following-error-no-protocol-specifie can export display and see X11 session on other machine or via DRAC or ILO interfaces You do not have access to X11 session Introduction Vino is the default VNC server in Gnome which provides the capability to view Gnome desktop via VNC client. To configure vino from within GNOME, go to System > Preferences command line > Remote Desktop To set vino to request access each time, tick Allow other users to view your desktop in the Remote Desktop configuration window To set a password, tick Require the user to enter this password: To put vino in view-only mode, untick Allow other users to control your desktop To only allow local connections: click on the tab marked Advanced, then tick Only allow local connections autolaunch error x11 To allow connections from anywhere: click on the tab marked Advanced, then untick Only allow local connections To change properties form command line run is more diffucult. There are two situations here: You can export display and see X11 session on other machine or via DRAC or ILO interfaces. You do not have access to X11 session You can export display and see X11 session on other machine or via DRAC or ILO interfaces In this case it is easy. Login using ssh or other method to remotebox, export display to the box where you can view X11 session and run vino-preferences # export DISPLAY=:0.0 # xhost 10.20.30.40 vino-preferences & Check "Allow other users to view your desktop" Uncheck "You must conform each access to this machine" Check "Require the user to enter this password" and enter the password Clock close Start vino-sever manually # /usr/libexec/vino-server & # to start the vino server Check the port on which vino server is listening (ports 5900-5909)root@remotebox:~# netstat -nl | grep 590[0-9] # check to make sure vino server is listening on port 590x Shutdown firewall and disable SE (you can open firewall port later, and try to enable SE if you succeed) Attempt
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 Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site 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 up and rise to the top dbus-launch terminated abnormally with the following error: No protocol specified up vote 7 down vote favorite After a recent upgrade in my Arch Linux x64 system, I keep getting this warning message after installing or removing packages with pacman. (gconftool-2:5207): GConf-WARNING **: Client failed to connect to the D-BUS daemon: /usr/bin/dbus-launch terminated abnormally with the following error: No protocol specified Autolaunch error: X11 initialization failed. So, far I have not seen any ill effects from this (that I know of), but I would like to make this warning go away. EDIT I can consistently reproduce this by installing or uninstalling GNOME Do. Both of the following commands result in the output above. $ sudo pacman -S gnome-do $ sudo pacman -Rns gnome-do Running xhost + seems to temporarily alleviate the warning (at least until I reboot). I can run xhost - and the warning returns. UPDATE This problem went away after a few upgrades (i.e. pacman -Syu). arch-linux x11 d-bus share|improve this question edited Mar 2 '14 at 3:36 asked Oct 13 '13 at 12:29 druciferre 210211 Are you using XFCE? I found this thread: code.google.com/p/acpi-eeepc-generic/issues/detail?id=47 –slm♦ Oct 13 '13 at 13:22 @sim, before doing the update (pacman -Syu), I only had GNOME installed. I immediately began seeing the warning after the update. Sometime after the warning started appearing I did install XFCE, KDE, and Cinnamon as well. I am playing around with different desktop environments trying to decide which one I want to use (since I'm ever increasingly dislik