Anyone get Mint Linux working as a View pool?

[pricemc1]

I know its not supported, but I'm trying to get a VM that runs Mint Linux set up as a pool in View. I'm using View 2203. The View Linux agent seems to install just fine and everything seems fine in the View admin interface. It recognizes the Mint VM and the agent on it. I am able to create a pool for it. When I go to login to the Mint VM via the Horizon client it successfully brings up a session with the Mint GUI's login screen. As soon as I put in a set of valid credentials it immediately disconnects though. I didnt install the View agent with the SSO enabled  option but the Mint VM is AD joined and I know AD login works fine on it when I login from the console. It doesn't matter whether I use a local account or an AD account though at the login screen when I connect with the View client, I still get kicked off immediately. When I look in the View admin console events it pretty much just says that I logged off the same moment that I logged on. 

Anyone have any suggestions or ideas?

Thanks...

[Hangl]

If you see the login screen via Horizon Client, you are probably being kicked out by the OS.

One possible condition is that you already logged in with the same user from the console.

You can check the system log to see what happened when you logged in from the Horizon Client.

[pricemc1]

Thanks for replying. I'm not much of a Linux person. Can you point me to the specific log and its location in the file system where I should be able to find it? Also, is there Horizon client-side log that might have some information? if so, where would I find that?

Thanks... 

[Hangl]

The system log should be at /var/log/syslog

Have you checked if the same user already logged in? You can list the logged in session by the command

sudo loginctl list-sessions

I'm not familiar with Horizon Client, see https://kb.vmware.com/s/article/1027744 for the location of its logs.

[pricemc1]

I looked in the syslog file and it seems like it might be something to do with the desktop gui if I understand them correctly. I am attaching the parts I think are relevant out of the 2 log files I reviewed to see if you can come up with anything from them. 

[Hangl]

According to the syslog,  it seemed that lightdm quit the user session and the xserver once the user logged in.

Jul  9 13:56:21 wv01 lightdm[1054]: Error activating login1 session: GDBus.Error:org.freedesktop.DBus.Error.NotSupported: Operation not supported
Jul  9 13:56:21 wv01 kernel: [484381.398773] audit: type=1400 audit(1688925381.677:8532): apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" name="/proc/124010/cmdline" pid=1021 comm="sssd_nss" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
Jul  9 13:56:23 wv01 systemd[1]: session-c20.scope: Deactivated successfully.
Jul  9 13:56:23 wv01 systemd[1]: session-c20.scope: Consumed 1.209s CPU time.
Jul  9 13:56:23 wv01 org.a11y.Bus[172050]: X connection to :104 broken (explicit kill or server shutdown).

I found a similar question from stackoverflow, see https://askubuntu.com/questions/1139133/cant-login-via-lightdm, from its comments, I suggest you try the following things:

1. Add user-authority-in-system-dir=true to the LightDM config

2. Check whether the user's HOME directory is full with the command

df -h $HOME

[Hangl]

Another thing worth a try is to add the following line to the end of /usr/lib/vmware/viewagent/bin/PostConnection.sh

xhost local:lightdm