search

immense / Remotely

A remote control and remote scripting solution, built with .NET 8, Blazor, and SignalR.
GNU General Public License v3.0
4.55k stars 1.61k forks source link

Black Screen Connecting to Ubuntu 22.04 LTS VM #834

Open CMcNichol-GBSTP opened 8 months ago

CMcNichol-GBSTP commented 8 months ago

Describe the bug Connecting to Ubuntu VM from WebUI connects, but presents a black screen, moving the mouse / typing on keyboard does not interact with the Ubuntu machine - Windows machines are working fine.

When connecting, and seeing a black screen, Ubuntu VM does get prompt to say 'Remote Control Active'.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'List of devices in WebUI'
  2. Click on 'Ubuntu VM'
  3. Select Remote Control / View Only
  4. See a black screen

Remotely Version Server (can be found on about page): 2024.02.23.1927 Agent (can be found in device card): 2024.02.23.1927

Expected Behavior Screen should load and see desktop of logged in user account

Screenshots image image

Desktop (please complete the following information):

Additional Context LogFile_2024-03-04.log Remote Log.txt

mattish91 commented 7 months ago

Can confirm. Same issue, similar logs.

Found a thread on here from 2023 with the same symptoms, they apparently found a fix, but that was for .net 6 not current .net 8.

Not working as of right now. luckily i got SSH to my machine, but would be good to get the UI as this is a fully remote desktop base.

CMcNichol-GBSTP commented 7 months ago

@mattish91 Thanks for confirming it wasn't just me having the issue.

Out of pure coincidence, after your response, I started looking at alternatives for accessing the Ubuntu Desktops I have, and have been able to resolve the issue for myself.

On the Linux Desktop, edit the file located in /etc/gdm3/custom.conf and change the line WaylandEnable=true to WaylandEnable=false and reboot the device.

Once it boots back up, Remotely is then working correctly for me.

bitbound commented 7 months ago

If you're using Wayland (which is now the default for most distros), that would be the cause. Remotely only supports X11.

Unfortunately, there probably won't ever be Wayland support unless the community contributes it.

Darkking723 commented 7 months ago

Thank you @CMcNichol-GBSTP your suggestion worked!

JamesonRGrieve commented 1 month ago

Getting this issue on every Ubuntu box I try to connect to. Physical boxes, VMs, 22, 24...

Tried WaylandEnable=false, no dice. Same problem.