Please let me know if installing the dbus-x11 package fixed the issue.
On 11/20/23 3:44 PM, DRC wrote:
On 11/20/23 1:29 PM, 'Felix Natter' via TurboVNC User
Discussion/Support wrote:
the first problem was that by default, GDM3 is running with wayland.
If I set waylandEnable=false in [daemon] section
of /etc/gdm3/custom.conf and reboot (systemctl restart gdm3 is not
enough), then I can at least
create and connect to a localhost server :) Do you want to document
this in the 3.0 compatibility section?
TurboVNC should have no dependency on GDM unless you are trying to run
the window manager with VirtualGL. If you are trying to run the
window manager with VirtualGL (and the traditional GLX back end, as
opposed to the newer but less compatible EGL back end), then yes, the
need to disable Wayland in GDM is a known issue that vglserver_config
handles automatically when you configure the system as a VGL host.
However, GDM is irrelevant to TurboVNC otherwise. I just tested
TurboVNC 3.1 on an Ubuntu 22.04 virtual machine, and the default
configuration of TurboVNC starts GNOME with no issues.
Regarding VNC between the two VMs - these may be permission issues as
I don't have LDAP (just local users)
in these two (test-)VMs. I will investigate.
When I try to start gnome-terminal in the (localhost-)VNC Session, I
get:
# Error creating terminal: Object does not exist at path
"/org/gnome/Terminal/Factory0"
BUT this seems to be because of the localhost session [1]
[1] https://github.com/TigerVNC/tigervnc/issues/407
That is a limitation of TigerVNC, but TurboVNC should allow multiple
GNOME instances, including a simultaneous local and remote instance.
Before I officially list a window manager on this page:
https://turbovnc.org/Documentation/Compatibility30, I always test
whether I can successfully use one instance of it in a TurboVNC
session simultaneously with another instance of it running with VGL in
a TurboVNC session simultaneously with another instance of it running
locally.
However, your inability to launch multiple simultaneous sessions gave
me a clue, and I noticed in your TurboVNC Server log that
xstartup.turbovnc isn't creating a new D-Bus instance for the TurboVNC
session. Can you confirm whether /usr/bin/dbus-launch is installed on
your system? If not, install the dbus-x11 package. If that is the
issue, then I need to modify our .deb so that it automatically
requests installation of dbus-x11.
--
You received this message because you are subscribed to the Google Groups "TurboVNC
User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/turbovnc-users/03b8f3c4-b32d-0920-3e48-a905227b90ce%40virtualgl.org.
