* information to be copied and set len to the number of bytes. Subject: parse_displayname: use FamilyWild for *:0Ģ files changed, 8 insertions(+), 0 deletions(-)ĭiff -git a/xauth/gethost.c b/xauth/gethost.c
#No protocol specified gedit Patch#
In ALT's xauth package, there has been applied a patch recently to support adding such FamilyWild entries via xauth directly with an *:0 argument: From bc78aa61cfbddaa27dee275f639ba40de6981b17 Mon Sep 17 00:00:00 2001įrom: George V. In this case, the string written after the family number (usually, a hostname etc.) does not matter for matching at all. xauth nlist :0 | sed -e 's/^./ffff/' | xauth nmerge. The value of FamilyWild is 65535 or 0xffff.
#No protocol specified gedit windows#
In WSL1, Linux uses the same IP addresses than the Windows host, then, you can access the applications using localhost or 127.0.0. You must consider the differences to access networking apps running on Windows and on Linux.
another example: Code: No protocol specified. The networking subsystem in WSL2 is different than the used in WSL1. E233: cannot open displayE852: The child process failed to start the GUINo protocol specified. We need to change the first 16 bits of the I can not open application as root user in terminal. I am not sure, if xauth has a proper command line to specify theĪuthentication Family, but I use sed to switch to Authenticationįamily 'FamilyWild'. The Xauthority file can be written in a way so that the hostname does
If you don't have a terminal emulator open at that time and you are unable to open one because of the authentication error, you could switch to the console (text mode), login there and execute the above command. Authorization required, but no authorization protocol specified (:75012): Gtk-WARNING : 08:40:24.020: cannot open display: :10.0 The accepted answer for the aforementioned question was typing DISPLAY:0.0 xhostNote also that the value of the cookie being added should match the value of the existing one. :ddd.0, then you should change the added host entry accordingly to "($hostname)/unix:ddd". $(hostname) expands to the result of the hostname command and unix:0 corresponds to your DISPLAY environment variable being set to :0.0. What you can do is to add a matching cookie using xauth: $ xauth add "$(hostname)/unix:0" MIT-MAGIC-COOKIE-1 bd988401cbf8xxxxxxxxxxxxxxxxxxxx If you change your host name, the X11 client library will no longer be able to find a matching cookie in the authentication database and the X11 server will reject the unauthenticated connection (unless configured otherwise). unix:1012 MIT-MAGIC-COOKIE-1 bd988401cbf8xxxxxxxxxxxxxxxxxxxx Localhost:1012 MIT-MAGIC-COOKIE-1 bd988401cbf8xxxxxxxxxxxxxxxxxxxx The list of cookies in your ~/.Xauthority file can be displayed using xauth list: $ xauth list That file is read by X11 clients and the cookies available there are used to authenticate the connections. When you login through some kind of a display manager, a MIT-MAGIC-COOKIE-1 authentication cookie is created and written into your ~/.Xauthority file. X11 uses the Xauth protocol to authenticate connecting clients. (gedit:3609): Gtk-WARNING **: 12:33:16.It's not only gedit that is going to fail but actually all programs that use the X11 protocol to talk to the graphics server. If I run export DISPLAY=:0 as a normal user, then the normal user can run GUI programs from the command line, however whenever I try the same with root it fails with the messages: No protocol specified I have tried running the following based on suggestions to no avail: export DISPLAY=:0 This happens with any user, not just root. Unable to init server: Could not connect: Connection refused When I open a terminal and try to run any GUI application, such as gedit, from the command line, it fails to open with the following messages: # gedit When I try to edit the sshdconfig file with the command: sudo gedit /etc/ssh/sshdconfig. I have a Debian 10 system with a desktop environment installed and running.
0 kommentar(er)
