Suse 12 Enterprise Server - Second VNC session gracefully closes after logon.

[Michael Nash]

I have a fresh install of Suse 12 Enterprise server. Gnome 3.10.2.  The VNC server automatically starts at IPL time.
I start a VNC session and turn on sharing. When I attempt to log onto a second session the session gracefully closes when the password is entered. If I edit the /etc/xinetd.d/vnc file and add AlwaysShared = Yes I am able to manually start the VNC server and start a second session but logout does not work.
Anyway, here is the output from the automatic start of the VNC server.  After the first session is logged in and output after the second session closes. Where would the configuration file be for the VNC server that starts at IPL time? What else can I do to debug this problem. Thanks again.
linux140:~ # systemctl status display-manager -l
display-manager.service - X Display Manager
Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled)
Active: active (running) since Sun 2015-01-25 16:09:19 EST; 3min 10s ago
Process: 605 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)
Main PID: 662 (gdm)
CGroup: /system.slice/display-manager.service
├─ 662 /usr/sbin/gdm --no-console
└─1382 /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Displays/__1_2

Jan 25 16:09:19 linux140 display-manager[605]: Failed to execute child process "/usr/bin/X" (No such file or directory)
Jan 25 16:09:19 linux140 display-manager[605]: Could not start the X server (your graphical environment) due to an internal error. Please contact your system administrator or check your syslog to diagnose. In the meantime this display will be disabled. Please restart GDM when the problem is corrected.
Jan 25 16:09:19 linux140 display-manager[605]: GdmDisplay: display lasted 0.011153 seconds
Jan 25 16:09:19 linux140 display-manager[605]: Failed to execute child process "/usr/bin/X" (No such file or directory)
Jan 25 16:09:19 linux140 display-manager[605]: Could not start the X server (your graphical environment) due to an internal error. Please contact your system administrator or check your syslog to diagnose. In the meantime this display will be disabled. Please restart GDM when the problem is corrected.
Jan 25 16:09:19 linux140 display-manager[605]: GdmDisplay: display lasted 0.011674 seconds
Jan 25 16:09:19 linux140 display-manager[605]: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
Jan 25 16:11:55 linux140 gdm-launch-environment][1393]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Jan 25 16:12:16 linux140 gdm-password][1502]: pam_unix(gdm-password:session): session opened for user root by (unknown)(uid=0)
Jan 25 16:12:17 linux140 display-manager[605]: Failed to remove slave program access to the display. Trying to proceed.
linux140:~ # systemctl status display-manager -l
display-manager.service - X Display Manager
Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled)
Active: active (running) since Sun 2015-01-25 16:09:19 EST; 4min 29s ago
Process: 605 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)
Main PID: 662 (gdm)
CGroup: /system.slice/display-manager.service
├─ 662 /usr/sbin/gdm --no-console
└─1382 /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Displays/__1_2
Jan 25 16:09:19 linux140 display-manager[605]: GdmDisplay: display lasted 0.011674 seconds
Jan 25 16:09:19 linux140 display-manager[605]: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
Jan 25 16:11:55 linux140 gdm-launch-environment][1393]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Jan 25 16:12:16 linux140 gdm-password][1502]: pam_unix(gdm-password:session): session opened for user root by (unknown)(uid=0)
Jan 25 16:12:17 linux140 display-manager[605]: Failed to remove slave program access to the display. Trying to proceed.
Jan 25 16:13:14 linux140 gdm-launch-environment][1763]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Jan 25 16:13:37 linux140 gdm-password][1841]: pam_unix(gdm-password:session): session opened for user root by (unknown)(uid=0)
Jan 25 16:13:38 linux140 display-manager[605]: Failed to remove slave program access to the display. Trying to proceed.
Jan 25 16:13:38 linux140 display-manager[605]: GLib-GObject: g_object_ref: assertion 'object->ref_count > 0' failed
Jan 25 16:13:38 linux140 display-manager[605]: GLib-GObject: g_object_unref: assertion 'object->ref_count > 0' failed

[Brian Hinz]

On Wed, Feb 4, 2015 at 8:59 AM, Michael Nash wrote:

I start a VNC session and turn on sharing. When I attempt to log onto a second session the session gracefully closes when the password is entered. If I edit the /etc/xinetd.d/vnc file and add AlwaysShared = Yes I am able to manually start the VNC server and start a second session but logout does not work.

Have you tried adding the '-once' parameter?  I don't know about the rest of the systemctl errors as I've never used it, but I would start by looking into this file:

Process: 605 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)

HTH,

-brian

[Michael Nash]

The VNC server automatically starts at IPL time with 3 VNC connections and 3 http connection.  The parameters are -noreset -inetd -once -query localhost -geometry 1024 x 768 -securitytypes none.  With the VNC session menus I set sharing on and I am able to verify thru the menus that sharing is set.  If I edit the /etc/inetd.d/vnc configuration file by adding the AlwayShared options I am able to start and share two sessions but logout does not work and maybe other stuff.  So why are the two VNC servers different.  I searched unsuccessfully to find another vnc configuration file that would be used by the VNC server at IPL time.  It does not seem to exist but if it did then where?  I also tried systemctl set-default multi-user.target I execute this and peformed a reboot. It got me in trouble. When I start a new VNC session I receive a black screen. I set it back to graphical mode.  This may be the correct setting but how do I configure the multi-user.target  screen settings? 

[Pierre Ossman]

On Wed, 4 Feb 2015 05:59:55 -0800 (PST),
Michael Nash wrote:

> I have a fresh install of Suse 12 Enterprise server. Gnome 3.10.2. The VNC
> server automatically starts at IPL time.
> I start a VNC session and turn on sharing. When I attempt to log onto a
> second session the session gracefully closes when the password is entered.
> If I edit the /etc/xinetd.d/vnc file and add AlwaysShared = Yes I am able
> to manually start the VNC server and start a second session but logout does
> not work.

Ok, I'm not really following you completely here so let's try to clear
things up first. :)

GDM (your display manager) handles your local session. It is not used
for any pure VNC sessions (like those started from xinetd). So you
should look at your xinetd service to see what's going on with the VNC
session.

The session sharing setting in Gnome activates Vino, a completely
different VNC server than TigerVNC. It is only for local sessions and
behaves different in many areas compared to ours.

When you are using multiple sessions, are those as the same user? This
is generally unsupported by most software (like Gnome) these days and I
doubt you'll get anything stable running unless you carefully pick your
software.

When you say that log out doesn't work, do you mean that it does
nothing? Or that you are disconnected but the session is still alive?
If it's the latter then it might simply have restarted.

Rgds
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600 https://plus.google.com/+CendioThinLinc

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?