When calling turbovnc with a window manager name, it will always start with TWM, regardless of the name provided.
Steps To Reproduce
Steps to reproduce the behavior:
install icewm or put it in the path
start turbovnc vncserver -wm icewm
connect client to vnc session
Expected behavior
The window manager used should be the one specified in the configuration or through the command line.
Screenshots
Additional context
The problem stems from the default startup script looking in /usr/share/xsessions/ for .desktop files in the format $wm-session.desktop. -wm can be passed a path to a .desktop file, but the default startup script promptly extracts the session name from the path and searches in /usr/share/xsessions/.
This applies to other VNC solutions as well.
A workaround is documented in the wiki by using -xstartup.
Notify maintainers
@nh2
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
Describe the bug
When calling turbovnc with a window manager name, it will always start with TWM, regardless of the name provided.
Steps To Reproduce
Steps to reproduce the behavior:
vncserver -wm icewm
Expected behavior
The window manager used should be the one specified in the configuration or through the command line.
Screenshots
Additional context
The problem stems from the default startup script looking in
/usr/share/xsessions/
for.desktop
files in the format$wm-session.desktop
.-wm
can be passed a path to a.desktop
file, but the default startup script promptly extracts the session name from the path and searches in/usr/share/xsessions/
.This applies to other VNC solutions as well.
A workaround is documented in the wiki by using
-xstartup
.Notify maintainers
@nh2
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.