You are not logged in.
I set up an Arch LXC container and I share the host's GPU with the container. I boot the container and I see the graphical login screen. However, when I enter the password, I get a black screen and the cursor.
the journal contains this:
Mar 02 16:49:10 test-desktop lightdm[102]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=974) by (uid=0)
Mar 02 16:49:10 test-desktop lightdm[102]: pam_systemd(lightdm-greeter:session): Failed to create session: Seat has no VTs but VT number not 0
Mar 02 16:49:10 test-desktop lightdm[66]: Error opening /dev/tty0: No such file or directory
Mar 02 16:49:10 test-desktop polkitd[77]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Mar 02 16:49:10 test-desktop polkitd[77]: <no filename>:4: subject=[Subject pid=105 user='lightdm' groups=lightdm seat=null session=null local=false active=false]
Mar 02 16:49:10 test-desktop polkitd[77]: <no filename>:3: action=[Action id='org.freedesktop.DisplayManager.AccountsService.ReadAny']
Mar 02 16:49:10 test-desktop polkitd[77]: <no filename>:4: subject=[Subject pid=105 user='lightdm' groups=lightdm seat=null session=null local=false active=false]
Mar 02 16:49:11 test-desktop systemd-networkd[53]: eth0: Gained IPv6LL
Mar 02 16:49:39 test-desktop systemd[1]: systemd-hostnamed.service: Succeeded.
Mar 02 16:49:43 test-desktop lightdm[123]: gkr-pam: unable to locate daemon control file
Mar 02 16:49:43 test-desktop lightdm[123]: gkr-pam: stashed password to try later in open session
Mar 02 16:49:43 test-desktop dbus-daemon[58]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.11' (uid=0 pid=123 comm="lightdm --session-child 15 20 " l>
Mar 02 16:49:43 test-desktop dbus-daemon[58]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
Mar 02 16:49:43 test-desktop lightdm[123]: pam_systemd_home(lightdm:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Mar 02 16:49:43 test-desktop lightdm[102]: pam_unix(lightdm-greeter:session): session closed for user lightdm
Mar 02 16:49:43 test-desktop lightdm[123]: pam_unix(lightdm:session): session opened for user test(uid=1000) by (uid=0)
Mar 02 16:49:43 test-desktop lightdm[123]: pam_systemd(lightdm:session): Failed to create session: Seat has no VTs but VT number not 0
Mar 02 16:49:43 test-desktop lightdm[123]: pam_env(lightdm:session): deprecated reading of user environment enabled
Mar 02 16:49:43 test-desktop lightdm[123]: gkr-pam: unable to locate daemon control file
Mar 02 16:49:43 test-desktop lightdm[123]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Mar 02 16:49:43 test-desktop lightdm[123]: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
Mar 02 16:49:43 test-desktop lightdm[66]: Error opening /dev/tty0: No such file or directory
Mar 02 16:49:43 test-desktop kapplymousetheme[139]: QStandardPaths: error creating runtime directory '/run/user/1000' (Permission denied)
Mar 02 16:49:44 test-desktop ksplashqml[144]: QStandardPaths: error creating runtime directory '/run/user/1000' (Permission denied)
Mar 02 16:49:44 test-desktop ksplashqml[144]: QStandardPaths: error creating runtime directory '/run/user/1000' (Permission denied)
Mar 02 16:49:44 test-desktop ksplashqml[144]: QStandardPaths: error creating runtime directory '/run/user/1000' (Permission denied)
Mar 02 16:49:44 test-desktop ksplashqml[144]: QStandardPaths: error creating runtime directory '/run/user/1000' (Permission denied)I checked the ~/.xsession-errors and it contained this error:
Failed to connect to bus: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)
dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead
I fixed this error by adding this to ~/.profile (which is probably a hack):
export XDG_RUNTIME_DIR=/run/user/$(id -u)
export DBUS_SESSION_BUS_ADDRESS="unix:path=$XDG_RUNTIME_DIR/bus"Now I get another error:
Failed to connect to bus: No such file or directory
dbus-update-activation-environment: error: unable to connect to D-Bus: Failed to connect to socket /run/user/1000/bus: No such file or directory
and indeed, directory /run/user is empty and I still get the black screen. Now if I first boot the container, see the login screen, then ssh into the container from another PC, and THEN login to plasma in the container - everything works!
It's not very convenient to ssh to a container before every login, so I would like to know how to fix it properly.
My DE is kde plasma and the login manager is the lightdm, since I never managed to make sddm work inside LXC.
At which stage is /run/user/ supposed to be populated for graphical logins? What is responsible for it?
Thank you in advance for your suggestions!
Last edited by burning daylight (2021-03-02 16:45:09)
Offline