vglserver-config disabled Ubuntu Greeter
97 views
Skip to first unread message
southern.cross
May 6, 2021, 6:17:42 PM5/6/21
to VirtualGL User Discussion/Support
Anyone ever seen the Ubuntu 20.04 local greeter come up blank after configuring vgl with,
/opt/Virtualgl/bin/vglserver-config
(1) w/ all defaults
then restart gdm3 and reboot.
Greeter never shows and the local screen is blank. I can ssh in remotely just fine but cannot log in locally.
*************************************
joehays@sedacs17lx:~$ uname -a
Linux sedacs17lx 5.8.0-50-generic #56~20.04.1-Ubuntu SMP Mon Apr 12 21:46:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
I'm using VirtualGL 2.6.5
And, wayland is disabled,
joehays@sedacs17lx:/etc/gdm3$ cat /etc/gdm3/custom.conf
...
[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=false
...
TurboVNC and VirtualGL work great but I lost local login abilities...
If I disable VGL using /opt/Virtualgl/bin/vglserver-config again things were still messed up. I then ran,
sudo apt install --reinstall ubuntu-gnome-desktop
and rebooted and it started working again.
Thoughts?
DRC
May 7, 2021, 7:43:07 PM5/7/21
to virtual...@googlegroups.com
I've never observed that issue, but if it started working again after
you ran
sudo apt install --reinstall ubuntu-gnome-desktop
then my next question would be whether running vglserver_config again
after that caused the problem to return.
In general, local login abilities will be limited once the VirtualGL GLX
back end is configured. Wayland will be disabled, as you already know,
but also, you won't be able to log in locally while anyone on the system
is using VirtualGL, or it will cause any applications running with
VirtualGL to freeze until you log out. VirtualGL 3.0 includes an EGL
back end that avoids these issues by eliminating the need for a 3D X
server entirely, but the EGL back end doesn't yet support all of the
features that the GLX back end supports (refer to
https://github.com/VirtualGL/virtualgl/issues/134 and
https://github.com/VirtualGL/virtualgl/issues/136), and it still has a
few bugs that I'm working through. Apart from those bugs, the EGL back
end should be suitable for most OpenGL applications-- especially
scientific applications (because those applications don't typically do
stupid things with GLX, whereas commercial applications often do.) You
can try it out in the dev/3.0 evolving pre-release build, if you want:
https://virtualgl.org/DeveloperInfo/PreReleases.
DRC
you ran
sudo apt install --reinstall ubuntu-gnome-desktop
after that caused the problem to return.
In general, local login abilities will be limited once the VirtualGL GLX
back end is configured. Wayland will be disabled, as you already know,
but also, you won't be able to log in locally while anyone on the system
is using VirtualGL, or it will cause any applications running with
VirtualGL to freeze until you log out. VirtualGL 3.0 includes an EGL
back end that avoids these issues by eliminating the need for a 3D X
server entirely, but the EGL back end doesn't yet support all of the
features that the GLX back end supports (refer to
https://github.com/VirtualGL/virtualgl/issues/134 and
https://github.com/VirtualGL/virtualgl/issues/136), and it still has a
few bugs that I'm working through. Apart from those bugs, the EGL back
end should be suitable for most OpenGL applications-- especially
scientific applications (because those applications don't typically do
stupid things with GLX, whereas commercial applications often do.) You
can try it out in the dev/3.0 evolving pre-release build, if you want:
https://virtualgl.org/DeveloperInfo/PreReleases.
DRC
Reply all
Reply to author
Forward
0 new messages