Keyboard and mouse not working after 'startx' command from terminal on Raspberry Pi 3

Hello,

First of all, sorry if this has already been addressed but i haven't found the topic regarding my issue.

After connecting to my headless Pi, my mouse and keyboard aren't working after launching the graphical interface with the 'startx' command. Is it even possible to make them work this way?

Or am i supposed to install teamviewer on the gui, connect via ssh before, start the gui from the terminal then connect via teamviewer? This is not very convenient.

Find more posts tagged with

Accepted answers

ChristianCay

Hi bakjoul,

Thank you for your post.

If you start X from a CUI TeamViewer is not able to grab the screen. That's why you're having this issue.

We recommend if you like to use the GUI to start Raspbian with autologin GUI. Switching from CUI to GUI, vice-versa is not supported by TeamViewer.

The following workaround can be used if you still anyways to switch from UIs:

Make sure you boot the system with Desktop Autologin under Boot Options (use the raspi-config command to set this). Reboot the system if you make any changes.
Connect to the device using TeamViewer. It will show the GUI and work as expected.
Switch to CUI by using CTRL-ALT-F1
Reconnect the TeamViewer session
Use the CLI as expected
If need to go back to GUI press CTRL-ALT-F7
Reconnect TeamViewer session
Use the GUI
Use the process as needed

Hope this solution works for you.

Best regards,

Christian

All comments

ChristianCay

Hi bakjoul,

Thank you for your post.

If you start X from a CUI TeamViewer is not able to grab the screen. That's why you're having this issue.

We recommend if you like to use the GUI to start Raspbian with autologin GUI. Switching from CUI to GUI, vice-versa is not supported by TeamViewer.

The following workaround can be used if you still anyways to switch from UIs:

Make sure you boot the system with Desktop Autologin under Boot Options (use the raspi-config command to set this). Reboot the system if you make any changes.
Connect to the device using TeamViewer. It will show the GUI and work as expected.
Switch to CUI by using CTRL-ALT-F1
Reconnect the TeamViewer session
Use the CLI as expected
If need to go back to GUI press CTRL-ALT-F7
Reconnect TeamViewer session
Use the GUI
Use the process as needed

Hope this solution works for you.

Best regards,

Christian

bakjoul

Hi Christian,

Thank you for your reply.

I didn't want to start Raspbian with autologin GUI to avoid using resources unnecessarily because i intended to run my RPi 99% of the time headless.The rest of the time would have been when it's moved and used with a screen for multimedia use.

So accessing the GUI, started from the terminal, via TeamViewer, would have been a way of managing the graphical desktop environment remotely. But i've dropped this idea anyway, i'll just use a different sd card for multimedia use, and use a screen to manage it now that i have the appropriate cable. (I had none at the time.)

However it's good to know that what i wanted to do is not possible. Thank you again for your answer.

Regards.

TulsaGrassFire

What do all those abbreviations mean? I have this problem and as far as I know, all windows versions I am on are up to date, registered and I have the latest TeamViewer software.

It was working fine until today or yesterday. Perhaps a windows patch broke it?

miguelp

I am starting x using xtartx in a embedded device. (vnc server is working OK)

but Teamviewer is waiting for something, and never goes online.

can be the same issue?

2016/11/03 18:35:59.240 8861 1822419296 GX0!! LinuxVT::GetActiveVT: error=25 consoleFD=-2, Errorcode=25
2016/11/03 18:35:59.240 8861 1822419296 GX0!! LinuxVT::GetActiveVTMode: error=25 fd=-2, Errorcode=25
2016/11/03 18:35:59.315 8840 1910499712 S!! LinuxVT::GetActiveVT: error=25 consoleFD=-2, Errorcode=25
2016/11/03 18:35:59.315 8840 1910499712 S!! LinuxVT::GetActiveVTMode: error=25 fd=-2, Errorcode=25