2

I have an Arch linux box that is almost running perfectly but when i connect to the vncserver and the sreensaver turns the screen black, i am forced to reenter the password on the loginscreen of gnome but! and here is the problem, this screen is constantly refreshed so i can't type more than two letters.

I keep every package updated with pacman -Syu. I use tigervnc in version 1.3.1.1. The connection is running over SSH. Gdm in version 3.12.0-1.

Can anyone help here?

~/.vnc/xstartup:

#!/bin/sh
export XKL_XMODMAP_DISABLE=1
exec gnome-session
|improve this question
  • How are you running vnc server? Did you exported flag export XKL_XMODMAP_DISABLE=1for example? – IBr Apr 15 '14 at 10:47
  • Yes. I have already exported it. – simonides Apr 15 '14 at 11:15
  • Then I don't know, I used tigervnc only for new sessions (ie. remote machine without running real xserver). When I needed to have a desktop shared with gdm I used x11vnc with gdm's Xauthority passed as argument and that worked like a charm. What else could be wrong with tigervnc I have no idea. – IBr Apr 16 '14 at 7:00
0

Even I searched a lot, but could not find a satisfactory answer on web. Here are possible workaround if you are unable to enter a password in vnc-client:-

  • Press any Key to reach password field
  • Use the Keyboard mouse to drag the locked screen from bottom to top direction
|improve this answer
  • well this question is some years old now. the problem wasn't that the password field was not there, the screwn was reloaded so fast the password field always got cleared before I could finish typing. – simonides Feb 16 at 9:11
0

I just started having this problem a week ago on ubuntu 18.04 (I use vnc on a daily basis), and haven't found a good answer for why it has suddenly started. Especially given that I didn't perform any updates and have auto updates turned off.

However, I seem to have found a workaround: if I start a second instance of vnc I can connect to it and the login screen behaves normally. The login screen continues to work normally on the second vnc instance after killing the 1st. I changed nothing in the 'xstartup' between the two instances. I have no idea why it works, but it does...

|improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.