You are not logged in.
Ok, but there's only output of "ls -la" for one or the other of those? I gather that output was more likely from the root user's directory, but then why does it have all the directories that are only created when running a gui session with DE-type tools running? Are you running X as root (you shouldn't)?
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Online
Ok, but there's only output of "ls -la" for one or the other of those? I gather that output was more likely from the root user's directory, but then
Yes, the output was only for /root
Sorry for the confusion
why does it have all the directories that are only created when running a gui session with DE-type tools running? Are you running X as root (you shouldn't)?
That is a good question. I ran sddm under root to then log in as the kavex user. But I wouldn't be able to guarantee that I didn't startx as the root user. It might have happened when I was trying to get xorg to work. But yeah that was stupid of me
Offline
Sorry for the tangent then as this isn't relevant to the problem at hand - thanks for clarifying.
Last edited by Trilby (2022-05-15 18:26:50)
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Online
We should maybe still see the contents of ~kavex - less the more private stuff, but dotfiles (.*profile or .zshenv or stuff like that) because the only way I can explain the previous journal is if the session-wrapper doesn't get to actually executing plasma-session but ends in some "exec whatever" line.
Offline
Sorry for the tangent then as this isn't relevant to the problem at hand
Oh, it's okay, no worries!
We should maybe still see the contents of ~kavex - less the more private stuff, but dotfiles (.*profile or .zshenv or stuff like that)
Here they are
total 141
drwxr-xr-x 15 kavex root 18 May 15 17:06 .
drwxr-xr-x 3 root root 3 May 14 01:06 ..
-rw------- 1 kavex kavex 52 May 15 17:06 .Xauthority
-rw------- 1 kavex kavex 3817 May 15 19:37 .bash_history
drwxr-xr-x 9 kavex kavex 12 May 15 17:07 .cache
drwx------ 3 kavex kavex 10 May 14 04:47 .config
drwxr-xr-x 3 kavex kavex 10 May 14 01:38 .ddconfig
drwxr-xr-x 3 kavex kavex 3 May 14 01:12 .kde4
drwxr-xr-x 4 kavex kavex 4 May 14 04:47 .local
-rw-r--r-- 1 root root 739 May 14 21:38 .xinitrc
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Desktop
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Documents
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Downloads
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Music
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Pictures
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Public
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Templates
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Videos
Offline
drwxr-xr-x 15 kavex root 18 May 15 17:06 .
drwxr-xr-x 3 root root 3 May 14 01:06 ..
…
-rw-r--r-- 1 root root 739 May 14 21:38 .xinitrc
The ownership/permissions of .xinitrc and your $HOME are off.
sudo chown kavex:kavex ~kavex ~kavex/.xinitrc
sudo chmod 700 ~kavex
sudo chmod 640 ~kavex/.xinitrc
The bloated DEs will piss themselves when they can't write into your $HOME but that should actually work - no idea whether there're further restrictions that you might hit if there bogus access rights inside ~/.config and ~/.cache
=> Can you log into an openbox session (NOT! i tried gnome)
Offline
=> Can you log into an openbox session (NOT! i tried gnome)
Oh, sorry, I thought it does not matter as long as it is not kde. Openbox started through sddm starts fine. Grey background, black cursor. Menu opens at rightclick and even applications lile calculator start fine and open in a window.
The ownership/permissions of .xinitrc and your $HOME are off.
How do I fix them? Chown kavex everything in the home directory of kavex, that is not owned by the kavex user?
Edit: nvm, just saw that you gave me commands to fix it in the code box
Last edited by kavex (2022-05-16 09:51:09)
Offline
~kavex looks like this now
total 141
drwx------ 15 kavex kavex 18 May 16 10:00 .
drwxr-xr-x 3 root root 3 May 14 01:06 ..
-rw------- 1 kavex kavex 52 May 16 10:00 .Xauthority
-rw------- 1 kavex kavex 3916 May 16 10:01 .bash_history
drwxr-xr-x 11 kavex kavex 14 May 16 10:01 .cache
drwx------ 3 kavex kavex 10 May 14 04:47 .config
drwxr-xr-x 3 kavex kavex 10 May 14 01:38 .ddconfig
drwxr-xr-x 3 kavex kavex 3 May 14 01:12 .kde4
drwxr-xr-x 4 kavex kavex 4 May 14 04:47 .local
-rw-r----- 1 kavex kavex 739 May 14 21:38 .xinitrc
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Desktop
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Documents
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Downloads
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Music
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Pictures
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Public
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Templates
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Videos
Starting a plasma session through sddm still only results in a balckscreen and the kde cursor though
Offline
sudo chown -R kavex:kavex ~kavex
Offline
sudo chown -R kavex:kavex ~kavex
Done. ls -la of ~kavex
total 141
drwx------ 15 kavex kavex 18 May 16 14:00 .
drwxr-xr-x 3 root root 3 May 14 01:06 ..
-rw------- 1 kavex kavex 52 May 16 14:00 .Xauthority
-rw------- 1 kavex kavex 4192 May 16 13:58 .bash_history
drwxr-xr-x 11 kavex kavex 14 May 16 14:02 .cache
drwx------ 3 kavex kavex 10 May 14 04:47 .config
drwxr-xr-x 3 kavex kavex 10 May 14 01:38 .ddconfig
drwxr-xr-x 3 kavex kavex 3 May 14 01:12 .kde4
drwxr-xr-x 4 kavex kavex 4 May 14 04:47 .local
-rw-r----- 1 kavex kavex 739 May 14 21:38 .xinitrc
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Desktop
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Documents
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Downloads
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Music
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Pictures
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Public
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Templates
drwxr-xr-x 2 kavex kavex 2 May 14 01:38 Videos
Trying to start kde from sddm still results in the same like before
Offline
Log into an openbox session, start an xterm and try to run "startplasma-x11" and see whether that gets you either a plasma desktop or some useful error messages.
Offline
Log into an openbox session, start an xterm and try to run "startplasma-x11" and see whether that gets you either a plasma desktop or some useful error messages.
Doing that gets me a blackscreen for a few seconds and then a message on the xterm window
QStandardPaths: XDG_RUNTIME_DIR not set, default to '/tmp/runtime-kavex
QStandardPaths: XDG_RUNTIME_DIR not set, default to '/tmp/runtime-kavex
QStandardPaths: XDG_RUNTIME_DIR not set, default to '/tmp/runtime-kavex
QStandardPaths: XDG_RUNTIME_DIR not set, default to '/tmp/runtime-kavex
QObject: Cannot create children for a parent that is in a different thread.
(Parent is SplashApp(0x7ffca5250b80), parent's thread is QThread(0x55c5840f9c80), current thread is QThread(0x55c5842a5d40)
QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Offline
XDG_RUNTIME_DIR not set, default to '/tmp/runtime-kavex
wtf?
grep -r systemd /etc/pam.d/
stat /usr/lib/security/pam_systemd.so
pacman -Qkk systemd
Offline
grep -r systemd /etc/pam.d
etc/pam.d/sddm-greeter:session optional pam_systemd.so
/etc/pam.d/system-login:-session optional pam_systemd.so
/etc/pam.d/system-auth:-auth [success=2 default=ignore] pam_systemd_home.so
/etc/pam.d/system-auth:-account [success=1 default=ignore] pam_systemd_home.so
/etc/pam.d/system-auth:-password [success=1 default=ignore] pam_systemd_home.so
/etc/pam.d/system-auth:-session optional pam_systemd_home.so
/etc/pam.d/gdm-launch-environment:-session optional pam_systemd.so
/etc/pam.d/systemd-user:# Used by systemd --user instances.
stat /usr/lin/security/pam_systemd.so
File: /usr/lib/security/pam_systemd.so
Size: 508776 Blocks: 665 IO Block: 131072 regular file
Device: 0,27 Inode: 23312 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-05-16 09:54:25.187991283 +0200
Modify: 2022-04-28 21:36:58.000000000 +0200
Change: 2022-05-13 17:40:03.583439935 +0200
Birth: 2022-05-13 17:40:03.583439935 +0200
pacman -Qkk systemd
systemd: 2002 total files, 1 altered file
Just in case it matters somehow (idk, I feel it could be relevant)
zfs list
NAME USED AVAIL REFER MOUNTPOINT
zroot 9.63G 1.08T 192K none
zroot/ROOT 9.61G 1.08T 192K none
zroot/ROOT/arch 9.61G 1.08T 9.61G /
zroot/data 1.97M 1.08T 192K none
zroot/data/home 1.79M 1.08T 1.11M /home
zroot/data/home/root 696K 1.08T 696K /root
zroot/var 1.12M 1.08T 192K /var
zroot/var/lib 576K 1.08T 192K /var/lib
zroot/var/lib/docker 192K 1.08T 192K /var/lib/docker
zroot/var/lib/libvirt 192K 1.08T 192K /var/lib/libvirt
zroot/var/log 384K 1.08T 384K /var/log
Last edited by kavex (2022-05-16 13:31:01)
Offline
So why is XDG_RUNTIME_DIR not set (let alone why it's chosing this weird default)?
You did log into openbox via SDDM, yes?
Do you unset XDG_RUNTIME_DIR anywhere?
ls -l /run/user/
Offline
You did log into openbox via SDDM, yes?
Yes, I started sddm and logged into the openbox session through it.
Do you unset XDG_RUNTIME_DIR anywhere?
Not as far as I remember.
ls -l /run/user
results in
total 0
drwx------ 7 kavex kavex 180 May 16 14:46 1000
Offline
So the dir exists (that's a tmpfs, it must have been created during the running boot) and has the proper permissions but XDG_RUNTIME_DIR does't point there nor anywhere else and gets defaulted to "/tmp/runtime-kavex"…
printenv
in that terminal?
Offline
If the terminal you mean is the xterm I can open in openbox, then the output of printenv is
SHELL=/bin/bash
WINDOWID=4194316
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session3
XTERM_VERSION=XTerm(372)
GNOME_KEYRING_CONTROL=/home/kavex/.cache/keyring-4F56L1
DESKTOP_SESSION=openbox
XTERM_SHELL=/bin/bash
GTK_MODULES=canberra-gtk-module
XDG_SEAT=seat0
PWD=/home/kavex
XDG_SESSION_DESKTOP=
LOGNAME=kavex
XDG_SESSION_TYPE=x11
XAUTHORITY=/home/kavex/.Xauthority
MOTD_SHOWN=pam
HOME=/home/kavex
LANG=C
XDG_CURRENT_DESKTOP=
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XTERM_LOCALE=C
XDG_SESSION_CLASS=user
TERM=xterm
USER=kavex
PAM_KWALLET5_LOGIN=/tmp/kwallet5_kavex.socket
DISPLAY=:0
SHLVL=0
XDG_VTNR=1
GTK3_MODULES=xapp-gtk3-module
XDG_DATA_DIRS=/home/kavex/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
MAIL=/var/spool/mail/kavex
_=/usr/bin/printenv
Offline
Everything there, but the runtime dir.
LANG=C
Fix your locale, https://wiki.archlinux.org/title/Locale - it's a stretch, but…
If that's not it, I blame flatpak.
Offline
I set my locale to de_DE.UTF-8
If I type local it also says de_DE.UTF-8 in all fields now, but when I try to start kde from sddm I still get the same result
I even get the same error when I type startplasma-x11 in an xterm
Last edited by kavex (2022-05-16 17:01:21)
Offline
You get that error because the runtime_dir environment isn't set, but that's supposed to happen by pam_systemd.so during the login, so something there goes terribly wrong.
Try to remove kwallet-pam, https://archlinux.org/packages/extra/x8 … allet-pam/
It's the last pam module and post pam_systemd, no idea whether it somehow throws the session off… *shrug*
Offline
Removed the package, but sadly nothing changed.
Offline
Can you properly login w/ eg. lightdm instead of SDDM?
Offline
I tried lightdm, but sasly it does not start. Neither as command, nor as enabled service at boot.
As command it basically just opens a new line when I press enter and gives me no feedback at all.
If I use systemctl enable lightdm.service I get stuck during the next reboot, because it wasn't able to start lightdm and I should go and check systemctl status lightdm.service. If I do (after disabling the lightdm service and rebooting via chroot, I just get the info that it is inactive (dead).
Edit: Nvm, I forgot to install lightdm-gtk-greeter. If I try to log into kde-plasma, I again just get the kde cursor an a blackscreen
Last edited by kavex (2022-05-17 11:17:38)
Offline
So it's not only SDDM, something™ is severely broken about the login process.
$XDG_RUNTIME_DIR is not set if the current user is not the original user of the session.
Do you have the same problem when you create a new user account?
Offline