The DM will then set $XAUTHORITY to match, and you still shouldn't need to change it manually. If you want to move the file elsewhere, configure the DM to put it elsewhere in the first place. The DM gives you the correct file that'll work with the Xserver it just started, so you should just use that. Xauthority file?īy not trying to "set it up". zshrc it still has the original working value and can still start apps. zshrc overwrites it with another path of the wrong file. Well, sounds like LightDM gives you one $XAUTHORITY pointing to the working file, and then your. Xresources.xinitrc attempts to read some resources that don't exist and otherwise consists of only exec i3. Xauthority file? And how exactly does it work anyway? I don't require remote access at this point. Whether this file is empty or doesn't exist doesn't appear to make any difference aside from xauth complaining about its absence when running it interactively. $XAUTHORITY points to ~/.config/x11/.Xauthority (because I set it in. I must have edited or deleted it at some point. I figured out that this probably has do do with a program called xauth and the contents of. or xhost + local BUT launching the same applications via my window manager works like a charm: #. The same error appears when running xauth generate :0. Whenever I try to run a GUI program (firefox, vlc, nemo) from the terminal (zsh in alacritty, but that shouldn't matter), I receive the following error: Authorization required, but no authorization protocol specifiedĪlong with various error messages that are obviously a consequence of this one. I'm using i3 with lightdm as display manager and have encountered a strange issue: I posted the same issue on /linuxquestions, feel free to remove this if it violates rule 1. Forcing me to always downgrade to WSL1 since browsing files without Nemo using just the terminal is a real pain in the. I probably should also add, that I am a Windows Insider (fast ring) and that I have this problem ever since I first tried WSL2 about half a year ago. I also tried to run both Vcxsrv and Ubuntu as administrator, just to rule out any permission problems on the Windows side of things. In case that is important: I did not create a UNIX account but use root (both before and after reinstalling Ubuntu so there should be no permission issues on the Ubuntu side). I have also uninstalled Ubuntu, manually deleted the remnants from AppData and made a clean reinstall of Ubuntu. When trying to run gedit, I get the following error: Unable to init server: Could not connect: Connection refused In the case of nemo, I get the following error: Unable to init server: Could not connect: Connection refusedĬould not parse arguments: Cannot open display: Then I also entered: export LIBGL_ALWAYS_INDIRECT=1Īfter having done that, I tried to execute some programs that used to work under WSL1.In Ubuntu, I entered: export DISPLAY=$(awk '/nameserver / ' /etc/nf 2>/dev/null):0.I started Vcxsrv with the following options: Multiple Windows, Display Number: -1, Start no client, Clipboard (with Primary Selection), Native OpenGL and Disable access control.I turned off the Firewall for home networks (just for testing). I am trying to get GUIs working with WSL2, but nothing I tried works.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |