![]() The Ubuntu box has X11Forwarding enabled, and I've tried both the ssh options -X and -Y… Nothing seems to work. The Mac is named powerbook, and the Ubuntu box is named lucid. On the Mac, $DISPLAY says /tmp/launch-FG8ND0/:0, and this is the debug log from ssh. The Mac is OS X 10.7 running XQuartz 2.7.2 (xorg-server 1.12.2) Ubuntu is 10.04. I'm using ssh to connect from my Mac to an Ubuntu box, trying to open xterm. But eh, it's a single user laptop I guess.X11 forwarding doesn't seem to work properly. Though even +LOCAL isn't ideal (it still allows all local UIDs), +SI:localuser:$(whoami) would be better. If you put the space in the middle, you actually end up granting access to literally everyone (that's what a lone + means). The "LOCAL" has to be in caps, and most importantly don't put the space in the middle. Your version looks like it got chewed up by Google Translate. from your Xinitrc before you mess with $XAUTHORITY.īeware that the second command is spelled xhost +LOCAL. But to do that, it needs to be run while Xauth is still working, so e.g. The second command can be useful, as it removes the need for Xauth at all. The first command is mostly useless – if you can run it, you already have a valid cookie anyway. You can't just grant yourself access if you don't have access. Yes, because those commands themselves need to have access to the X server to do their job. The same error appears when running xauth generate :0. X mostly doesn't care, it's a network protocol at heart. I don't require remote access at this point. ![]() If you look at Xorg's command line, there's a -serverauth parameter pointing to a similar file this tells Xorg what cookie to accept from your apps. It just contains a "cookie" (a random password) that LightDM generates and gives to both the Xserver and your Xsession. Every time you log in, you get a new xauth file, and it has to be moved again – the old one won't be accepted by the new Xserver. If that's absolutely not possible, then your Xsession script (not the zshrc, as that runs too late and too deep down, but the Xsession or Xinitrc) should set the environment variable and move DM-provided file to the new location. 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: #. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |