The frustration was seeing the same non-solution many times (often more than ten times) without finding one that worked. In the poster’s defense, these may have worked at some point but have been superseded. There were lots of posts along the lines of “this will fix it” which often didn’t work at all.Not only was there a dearth of information, many of the posts quickly descended into ‘flame wars’ of epic proportions. This has been one of my most frustrating investigations. When the question is “how do I run as root?”, an answer of “use the command line tools, you noob” is not appropriate.Īfter a lot of research, I believe I have a better understanding of the issues, and a solution. While there were several suggested replacements (including mine ), these either did not cover all (or even many) of the use cases, or didn’t even work at all. The only explanation seemed to be “because of Wayland”. There didn’t seem to be a reason for its removal.There were a few reasons to be upset about this. The gksu command was removed with Ubuntu 17.10 ( ), which caused much angst to many people.
TL DR If you don’t need/want the background, I have packaged a script that implements my solution. I'm using 5.6.After upgrading Ubuntu to 20.04, I could not run GUIs as root and gksu is gone. 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. 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 your path is probably the problem, i could replicate the problem in 2 seconds 1st try.) (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? 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
GEDIT NO PROTOCOL SPECIFIED FULL
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 Gentoo Forums :: View topic - No protocol specified Cannot open display error