gdm/vino crash opening System Settings over VNC

Asked by Larry Irwin

I have a headless co-lo Ubuntu 18.04 server with gdm3 and vino-server running via auto-login and autostart.
I have an Ubuntu 18.04 laptop with gdm3 and Remmina.
I use ssh to create a tunnel: ssh -i /etc/ssh/dev/ssh_host_rsa_key -L 35900:127.0.0.1:5900 -N -p $TCPPORT -l root $IPADDRESS &
Using Remmina, I connect to 127.0.0.1:35900 and I'm able to login and get to the desktop on the server.
I left-click on the cog-wheel and choose System Settings and the dialog appears ... for about 2 seconds... and then the entire desktop and vino-server crash. The "w" command no longer shows the auto-login user as logged in.
Restarting gdm3 gets the desktop back up, running, logged in and vino-server listening on port 5900.
Is there something that needs to be set up to allow access to System Settings or is it a bug?
TIA,
Larry

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Larry Irwin (lrirwin) said :
#1

I just tested a bit more - everything else I executed from the desktop worked as expected.
It must either be something to do with the fact it is headless (xorg) or there is some issue with permissions (polkit).
My xorg,conf for headless operation:
===
Section "Monitor"
 Identifier "Monitor0"
 HorizSync 28.0-80.0
 VertRefresh 48.0-75.0
Modeline "1600x900_60.00" 119.00 1600 1696 1864 2128 900 901 904 932 -HSync +Vsync
EndSection
Section "Device"
 Identifier "Card0"
 Option "NoDDC" "true"
 Option "IgnoreEDID" "true"
 Driver "dummy"
EndSection
Section "Screen"
 DefaultDepth 16
 Identifier "Screen0"
 Device "Card0"
 Monitor "Monitor0"
  SubSection "Display"
  Depth 16
  Modes "1600x900"
  EndSubSection
EndSection
===

Revision history for this message
Larry Irwin (lrirwin) said :
#4

Spam answer

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

What are you doing on the system once you get connected using VNC to the Vino server? Maybe there is a sleeker solution to what you want to do.

Revision history for this message
Larry Irwin (lrirwin) said :
#7

This:
===
I left-click on the cog-wheel and choose System Settings and the dialog appears ... for about 2 seconds... and then the entire desktop and vino-server crash. The "w" command no longer shows the auto-login user as logged in.
===
And everything else works. - Only System Settings fails.

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

No, I meant why do you want to get on the system's desktop?

Revision history for this message
Larry Irwin (lrirwin) said :
#9

Some things, like expanding a logical volume, are much easier via GUI tools. Same thing goes for changing up system settings vs. handling via gsettings and other CLI configuration tools. So - I can use the GUI tools for expanding a basic logical volume, using a browser on localhost, etc., but can't work on system settings. - So - do I need to install a true VNC Server so I can get that functionality back? I was hoping not to have to do that...

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

Why not open the browser on the client and connect to the remote system...... Makes far more sense. You don't use vino to go to any other websites. Just type the server's IP in your browser (add port numbers as needed) and it'll connect.

Revision history for this message
Larry Irwin (lrirwin) said :
#11

And how does that get me into "System Settings" on the headless server in a remote CoLo? - It doesn't run in a broswer... Only from a desktop...

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

What system settings are you changing?

Revision history for this message
Larry Irwin (lrirwin) said :
#13

This report is not about what I'm changing, but about the fact that Systems Settings crashes in this environment. If you have suggestions on how to fix that, they are welcome. However, questioning my specific usage is not helping solve the issue that it crashes. I know there are many ways to do what I need done at any given point. This is not what I've reported here that needs addressing. Please stay on topic.

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

I don't use vino but if a workaround can be found until someone else posts so you can be productive, isn't that useful?

Revision history for this message
Larry Irwin (lrirwin) said :
#15

No - not really... I can figure workarounds. I have 33 years of *nix background for that. My support staff is technical, but they are not full *nix hacks, and they can navigate the GUI's better than find CLI methods. So I'm trying to make the desktop tools available for their use in whatever situation they may encounter.

Can you help with this problem?

Provide an answer of your own, or ask Larry Irwin for more information if necessary.

To post a message you must log in.