![]() The problem was in net-misc/dhcpcd-6.0.2, upgrading to net-misc/dhcpcd-6.0.3 fixes it. Last edited by sifosvaca on Sun 7:59 am edited 1 time in total I did 'sudo xhost +' 17 hours ago and the problem haven't reappeared so far, so I guess it works.ĮDIT: Just for the record, I typed 'xhost +' before the problem appeared. E233: cannot open displayE852: The child process failed to start the GUINo protocol specified. If the program works after that, we know its a security issue. This will reduce some security built in to the X Window system and allow any process to write to the display. ![]() The system should respond with: "access control disabled, clients can connect from any host" Please try typing "sudo xhost +" from the command line. Well I was logged on to a gnome session, and had a terminal open(Pseudo).Īlso I don't think there's a problem with the env variables, Ill check the path when the problem happens againīut right now(everything is working this ~ $ echo $XAUTHORITY This happens regardless of whether I am in KDE or GNOME. that kinda thing), they run fine as a normal user, but whenever i run them with sudo or in a root terminal, I get: No protocol specified (gedit:4769): Gtk-WARNING : cannot open display: :0. your path is probably the problem, i could replicate the problem in 2 seconds 1st try.) Hi, I have a problem whenever I try to run X applications in root (gedit etc. (i dont know the exact syntax to 'report' to merge threads so ill let it be, and link the answer. ![]() Have you started X-Windows (aka KDE, gnome) etc? Do you just have a command prompt, or are you entering these commands from a text window running inside a desktop? Now i dont understand why I cant run GUI applications like gedit.etc from a terminal. It sounds like you are trying to run a GUI program from the command line. The error is the same on a regular user and root Run 'eog -help' to see a full list of available command line ~ $ gedit Several applications refuse to run and I get this error: Posted: Fri 8:39 pm Post subject: No protocol specified Cannot open display error Gentoo Forums Forum Index Desktop Environments ![]() No protocol specified Cannot open display error I have searched in many forums and it seems a well known problem, but i have not been able to fix it with CentOS6. Gentoo Forums :: View topic - No protocol specified Cannot open display error No protocol specified (gedit:4266): Gtk-WARNING : cannot open display: :0.0 Thanks in advance for your help. If your program insists on the -display argument, make it use the environment variable. gui, your script doesn't do anything useful. Your program probably does look up the value of the DISPLAY environment variable, because that tends to happen automatically with xlib calls. The main exception is use of screen or tmux.) I'm guessing what sunnysigara said is relevant (sudden upstream break). If you were always running it in a GUI, then it's kinda strange that gedit is failing like that. Point is, you should have a graphical desktop environment turned on before starting Gedit. (Usually, if DISPLAY has the wrong value, it's because you've been messing with it. 'System Default' points to 'Gnome on Xorg'. The display to use is normally indicated by the DISPLAY environment variable, and that variable tends to be set correctly automatically. Even if it does, you lose the optimizations that local displays have. When you say under the root of the program run it sees that the Xserver under the users root are not running and informs you about this. Going through TCP may not work depending on whether the X server accepts TCP connections. First, the local X display should be :0, not 127.0.0.1:0, because including an IP address causes the traffic to go through TCP instead of local access. This is almost certainly wrong for two reasons. This is the first local X display, accessed over TCP. ![]() The meaning of the option -display 127.0.0.1:0.0 depends on that gui program, but it's highly likely that it means “display on the X display 127.0.0.1:0.0”. ![]()
0 Comments
Leave a Reply. |