![]() password for I added xauth add to the value returned by xauth list $DISPLAY (given above) and ran it in the console xauth add arvind-Inspiron-1440/unix:0 MIT-MAGIC-COOKIE-1 bfa2e2b478a6ef3c362301170214c04e Here’s the command line with result to give myself the root sudo su. ![]() It results in switching the current user. Now, I promote myself to root by doing sudo su - (and entering the password). Which gives me the following value: arvind-Inspiron-1440/unix:0 MIT-MAGIC-COOKIE-1 bfa2e2b478a6ef3c362301170214c04e One way to do this is as follows:īefore you issue the su or sudo (but after having ssh'ed into the remote system if you are using ssh), request the cookie for the current DISPLAY that's connecting to your X server:Īs suggested I followed the steps given below and i was able to find a way to get rid of xauth error messages.įirst of all, to get the current COOKIE information, I do xauth list xauth list $DISPLAY So, you need to let the other user in on what your cookie is. X authentication is based on cookies - secret little pieces of random data that only you and the X server know. (gedit:4700): Gtk-WARNING **: cannot open display: :0.0Īfter doing some search I found the following reason: I'm using 5.6.After doing sudo su - (to give myself root privileges) when I tried editing a file using gedit info.txt it would show me the following error message: gedit info.txt 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 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
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |