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:or...
See more...
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
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...
See more...
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.
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 ...
See more...
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.
I think it is located in /usr/lib/systemd/user/dbus-broker.service on RHEL9 with the following command, systemctl --user status dbus
○ dbus-broker.service - D-Bus User Message Bus
Loaded:...
See more...
I think it is located in /usr/lib/systemd/user/dbus-broker.service on RHEL9 with the following command, systemctl --user status dbus
○ dbus-broker.service - D-Bus User Message Bus
Loaded: loaded (/usr/lib/systemd/user/dbus-broker.service; enabled; vendor preset: enabled)
Active: inactive (dead)
TriggeredBy: ● dbus.socket
Docs: man:dbus-broker-launch(1)
Hi @Juhana1 , According to the log, it cannot "chdir" to the user's home directory even if it has root user privileges. The user's home directory seems a link created by /etc/cubbli/hyad-pam-sessio...
See more...
Hi @Juhana1 , According to the log, it cannot "chdir" to the user's home directory even if it has root user privileges. The user's home directory seems a link created by /etc/cubbli/hyad-pam-session.sh Mar 24 09:42:04 vdi-cubic-016 /etc/cubbli/hyad-pam-session.sh: [3455] User <user> home directory is ./ad/lxhome/j/<user>/Linux
Mar 24 09:42:04 vdi-cubic-016 /etc/cubbli/hyad-pam-session.sh: [3455] Symlink /home/<user> -> ./ad/lxhome/j/<user>/Linux created. Can you check the user's home directory permission mode by commands 'stat', 'getfacl', etc? And check if user root can access it? BTW, seems the distribution is Cubbli Linux, please understand that we haven't officially tested on it and supported it. Thanks, - Hang Li
Hi @Juhana1, I cannot reproduce in my lab with the same version. It might be related to the user's shell prompt setting. So you can extract the PS1, PS2 and PWD by the following command, set...
See more...
Hi @Juhana1, I cannot reproduce in my lab with the same version. It might be related to the user's shell prompt setting. So you can extract the PS1, PS2 and PWD by the following command, set | egrep '(PS.*|PWD)' - Hang Li
Can you provide the full output of xandr in the case where the problem occurs? Another thing worth trying when the problem occurs is to exit fullscreen mode and then re-enter it.
v4l2loopback-ctl is a command line tool, but not a module. Error: Miss v4l2loopback-ctrl, it means installer cannot find it in PATH. Please check if the following command works, which v4l2lo...
See more...
v4l2loopback-ctl is a command line tool, but not a module. Error: Miss v4l2loopback-ctrl, it means installer cannot find it in PATH. Please check if the following command works, which v4l2loopback-ctrl If it works, please try installing again by using install_viewagent.sh instead of viewSetup.sh.
