X11 connection rejected because of wrong authentication

Forums / NoMachine Terminal Server Products / X11 connection rejected because of wrong authentication

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #26741
    kk-ase-tcsgmail-com
    Participant

    Hi,

    Yesterday my NoMachine started giving errors when opening vim and git terminals.
    X11 connection rejected because of wrong authentication.

    Gvim exact error:
    X11 connection rejected because of wrong authentication.
    E233: cannot open display
    E852: The child process failed to start the GUIX11 connection rejected because of wrong authentication.Press ENTER or type command to continue

    Gitk exact error:
    11 connection rejected because of wrong authentication.
    X11 connection rejected because of wrong authentication.
    application-specific initialization failed: couldn’t connect to display “localhost:15.0”
    X11 connection rejected because of wrong authentication.
    X11 connection rejected because of wrong authentication.
    Error in startup script: couldn’t connect to display “localhost:15.0”
    while executing
    “load /usr/lib/x86_64-linux-gnu/libtk8.6.so Tk”
    (“package ifneeded Tk 8.6.5” script)
    invoked from within
    “package require Tk”
    (file “/usr/bin/gitk” line 10)

    After killing that session and creating a new one, I am getting issues with sourcing the .bashrc file. None of the bash commands like getting colored terminal, parsing git branch etc are working.

    The same commands are working when I tried WSL.

    Can you suggest what could be the issue?

    $ echo $DISPLAY localhost:44.0

    #26750
    graywolf
    Moderator

    Hello,

    localhost:15 and localhost:44 are not usual for NoMachine display. Display is usually :0 when sharing the server console and :1001, :1002, and so on for virtual desktop sessions. There could be something related. Do you how could that happen?

    About sourcing of commands in .bashrc, I don’t know how NoMachine is related with that. I guess the environment variables of the shell  are not correctly set.

Viewing 2 posts - 1 through 2 (of 2 total)

This topic was marked as solved, you can't post.