xfwm4 started by x-window-manager alternative symlink doesnt start a functional desktop.

Asked by D Demmin

On a new 18.04 LTS installation with vnc4server and xfce4 installed.

/usr/bin/vncserver configures the default .xstartup to point to /usr/bin/x-window-manager. When alternatives is configured to xfwm4 a functional desktop is not seen. Manual fix seems to be to edit the default xstartup to point to x-session-manager which points to startxfce4.

Is there something I am missing about the purpose of starting xfwm4 instead of startxfce4 in the default configuration?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu vnc4 Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

What are you wanting to do on the remote system? There may be a sleeker solution to what you want to do.

Revision history for this message
D Demmin (d0ubled) said :
#2

The desired functionality is new users to have a vnc session with working XFCE desktop environment. Currently each new user must edit their ~/.vnc/xstartup file since the default version doesnt appear to start the full desktop environment.

I did find another (better in my opinion) workaround by following the xstartup comment to uncomment 2 lines:
# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

This leads to a working XFCE desktop but still requires each user to do this step. Is there a reason those lines are commented in the default state?

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#3

But what will they be doing on the system once connected via VNC (once it is working)?

Revision history for this message
D Demmin (d0ubled) said :
#4

Users will be using various GUI based engineering tools as well as a web browser for downloading required tools and information. We have also explored using x11 tunneling over SSH but many of these tools need to run for hours at a time and disconnecting the X11 session when the connecting laptops sleep or reboot it restarts the effort.

Revision history for this message
actionparsnip (andrew-woodhead666) said :
#5

I getcha. Loads of people think anything remote accessing needs VNC. One guy even wanted it so he could run updates. I always ask.
https://youtu.be/iPAAY3rSoPo

Something like that?

Revision history for this message
D Demmin (d0ubled) said :
#6

Sadly no.

I have no issue getting vnc to work. The issue is it requires a manual step for each user since the default configuration doesn't provide a functional vnc session.

It seems like:
* The default xstartup script should point to x-session-manager rather than x-window-manager
 or
* The two commented lines for a normal desktop should be uncommented by default (note: in further testing the vncconfig must be run first otherwise cut and paste will not be available).

Either one of these changes to the vnc4 package would make it so each new user doesnt have to edit their xstartup file to get a usable desktop.

Is there a method I am missing, or is this a bug, or are there other reasons this is not the default for the vnc4 package?

Revision history for this message
Launchpad Janitor (janitor) said :
#7

This question was expired because it remained in the 'Open' state without activity for the last 15 days.