sddm error relating to authorization file, how to troubleshoot

Hello everyone

I’m using Fedora 30 with the KDE spin. I have an issue with sddm and I don’t know how I can identify the root cause. I’d be grateful if you can tell me how to proceed with troubleshooting.

What I observed is that sddm works and lets me log in normally, but it has the following error in Xorg.0.log as the last entry before I login:

[    14.631] (EE) Failed to open authorization file "/var/run/sddm/{e91a9a81-89c9-4215-9aff-d75a28bcf2d8}": No such file or directory

However that file exists and has a modification time just around boot time, when I go look for it.

Now I can’t just ignore this because I also want to run a script from /etc/sddm/Xsetup. I would like for this script to be run by root and even before I login that’s why I chose Xsetup. Commands that I put in Xsetup never seem to run. I assume this is because sddm breaks upon the above error.

I searched around the internet for failures to open the authorization file, but many cases are unlike mine in that they are related to graphics drivers failing and not allowing a successful login at all. Quite often people also end the thread with “I gave up and reinstalled my Manjaro/Arch/whatever”

I reinstalled sddm and sddm-kcm, taking care to delete the /etc/sddm.conf.rpmsave in between, that didn’t help. I tried manually removing the authorization file, but it’s recreated and still not found.

In my confusion I even cloned the sddm repo and searched for “authorization” and “Failed to find” but the first didn’t give results and the second gave results that made no sense relating to my situation. I’m thinking the error message must come from somewhere else, but I don’t know where to look.

I can see some errors related to sddm in journalctl, but nothing seems that important or related to the authorization file from what I can see. You can have a look yourselves:

$ journalctl -b | grep sddm
Okt 31 16:45:03 hal9000 systemd-tmpfiles[686]: [/usr/lib/tmpfiles.d/sddm.conf:1] Line references path below legacy directory /var/run/, updating /var/run/sddm → /run/sddm; please update the tmpfiles.d/ drop-in file accordingly.
Okt 31 16:45:05 hal9000 systemd-tmpfiles[978]: [/usr/lib/tmpfiles.d/sddm.conf:1] Line references path below legacy directory /var/run/, updating /var/run/sddm → /run/sddm; please update the tmpfiles.d/ drop-in file accordingly.
Okt 31 16:45:07 hal9000 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=sddm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Okt 31 16:45:08 hal9000 audit[1391]: USER_AUTH pid=1391 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Okt 31 16:45:08 hal9000 audit[1391]: USER_ACCT pid=1391 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Okt 31 16:45:08 hal9000 audit[1391]: CRED_ACQ pid=1391 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Okt 31 16:45:08 hal9000 sddm-helper[1391]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Okt 31 16:45:08 hal9000 systemd-logind[1099]: New session c1 of user sddm.
Okt 31 16:45:08 hal9000 audit[1393]: USER_ACCT pid=1393 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Okt 31 16:45:08 hal9000 systemd[1393]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
Okt 31 16:45:08 hal9000 audit[1393]: USER_START pid=1393 uid=0 auid=988 ses=1 subj=system_u:system_r:init_t:s0 msg='op=PAM:session_open grantors=pam_selinux,pam_selinux,pam_loginuid,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="sddm" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Okt 31 16:45:08 hal9000 systemd[1]: Started Session c1 of user sddm.
Okt 31 16:45:08 hal9000 audit[1391]: USER_START pid=1391 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_unix,pam_systemd acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=:0 res=success'
Okt 31 16:45:08 hal9000 sddm-greeter[1402]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
Okt 31 16:45:08 hal9000 sddm-greeter[1402]: QObject: Cannot create children for a parent that is in a different thread.
Okt 31 16:45:08 hal9000 sddm-greeter[1402]: QObject: Cannot create children for a parent that is in a different thread.
Okt 31 16:45:08 hal9000 sddm-greeter[1402]: QObject: Cannot create children for a parent that is in a different thread.
Okt 31 16:45:08 hal9000 sddm-greeter[1402]: QObject: Cannot create children for a parent that is in a different thread.
Okt 31 16:45:08 hal9000 sddm-greeter[1402]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Okt 31 16:45:08 hal9000 sddm-greeter[1402]: Cannot watch QRC-like path ":/icons/hicolor/index.theme"
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/WallpaperFader.qml:119:13: QML PropertyChanges: Cannot assign to non-existent property "opacity"
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/WallpaperFader.qml:120:17: Unable to assign [undefined] to QObject*
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/UserDelegate.qml:174: ReferenceError: ColorScope is not defined
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/UserDelegate.qml:161:9: Unable to assign [undefined] to QColor
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/UserDelegate.qml:160:9: Unable to assign [undefined] to int
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/Clock.qml:40:13: Unable to assign [undefined] to QColor
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/Clock.qml:39:13: Unable to assign [undefined] to int
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/Clock.qml:47:13: Unable to assign [undefined] to QColor
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/Clock.qml:46:13: Unable to assign [undefined] to int
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/WallpaperFader.qml:119:13: QML PropertyChanges: Cannot assign to non-existent property "opacity"
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/WallpaperFader.qml:120:17: Unable to assign [undefined] to QObject*
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/UserDelegate.qml:174: ReferenceError: ColorScope is not defined
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/UserDelegate.qml:161:9: Unable to assign [undefined] to QColor
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/UserDelegate.qml:160:9: Unable to assign [undefined] to int
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/Clock.qml:40:13: Unable to assign [undefined] to QColor
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/Clock.qml:39:13: Unable to assign [undefined] to int
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/Clock.qml:47:13: Unable to assign [undefined] to QColor
Okt 31 16:45:09 hal9000 sddm-greeter[1402]: file:///usr/share/sddm/themes/breeze/components/Clock.qml:46:13: Unable to assign [undefined] to int
Okt 31 16:45:36 hal9000 sddm-helper[1590]: gkr-pam: unable to locate daemon control file
Okt 31 16:45:36 hal9000 sddm-helper[1590]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
Okt 31 16:45:36 hal9000 audit[1590]: USER_AUTH pid=1590 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_succeed_if,pam_localuser,pam_unix,pam_gnome_keyring acct="joel" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Okt 31 16:45:36 hal9000 audit[1590]: USER_ACCT pid=1590 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="joel" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Okt 31 16:45:36 hal9000 sddm-helper[1590]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Okt 31 16:45:36 hal9000 audit[1590]: CRED_ACQ pid=1590 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix,pam_gnome_keyring acct="joel" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=? res=success'
Okt 31 16:45:36 hal9000 audit[1590]: USER_ROLE_CHANGE pid=1590 uid=0 auid=1000 ses=2 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='pam: default-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 selected-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=:0 res=success'
Okt 31 16:45:36 hal9000 sddm-helper[1391]: pam_unix(sddm-greeter:session): session closed for user sddm
Okt 31 16:45:36 hal9000 audit[1391]: USER_END pid=1391 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_unix,pam_systemd acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=:0 res=success'
Okt 31 16:45:36 hal9000 audit[1391]: CRED_DISP pid=1391 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_permit acct="sddm" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=:0 res=success'
Okt 31 16:45:36 hal9000 sddm-helper[1590]: pam_unix(sddm:session): session opened for user joel by (uid=0)
Okt 31 16:45:36 hal9000 sddm-helper[1590]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Okt 31 16:45:36 hal9000 sddm-helper[1612]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
Okt 31 16:45:36 hal9000 audit[1590]: USER_START pid=1590 uid=0 auid=1000 ses=2 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_gnome_keyring,pam_kwallet5,pam_umask,pam_lastlog acct="joel" exe="/usr/libexec/sddm-helper" hostname=? addr=? terminal=:0 res=success'
Okt 31 16:45:36 hal9000 sddm-helper[1590]: Starting: "/etc/X11/xinit/Xsession \"/usr/bin/startkde\""
Okt 31 16:45:46 hal9000 systemd[1395]: pam_unix(systemd-user:session): session closed for user sddm

Here is my fpaste:

$ fpaste --sysinfo --printonly                               
=== fpaste 0.4.0.1 System Information (fpaste --sysinfo) ===
* OS Release (cat /etc/*-release | uniq):
     Fedora release 30 (Thirty)
     NAME=Fedora
     VERSION="30 (Thirty)"
     ID=fedora
     VERSION_ID=30
     VERSION_CODENAME=""
     PLATFORM_ID="platform:f30"
     PRETTY_NAME="Fedora 30 (Thirty)"
     ANSI_COLOR="0;34"
     LOGO=fedora-logo-icon
     CPE_NAME="cpe:/o:fedoraproject:fedora:30"
     HOME_URL="https://fedoraproject.org/"
     DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f30/system-administrators-guide/"
     SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
     BUG_REPORT_URL="https://bugzilla.redhat.com/"
     REDHAT_BUGZILLA_PRODUCT="Fedora"
     REDHAT_BUGZILLA_PRODUCT_VERSION=30
     REDHAT_SUPPORT_PRODUCT="Fedora"
     REDHAT_SUPPORT_PRODUCT_VERSION=30
     PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
     Fedora release 30 (Thirty)
     
* Kernel (uname -r ; cat /proc/cmdline):
     5.3.7-200.fc30.x86_64
     BOOT_IMAGE=(hd5,gpt6)/vmlinuz-5.3.7-200.fc30.x86_64 root=UUID=5b9a37f4-fabc-4e31-8108-0f523e46dc36 ro resume=UUID=203c9c2f-e9c0-41f0-a6e6-a8013efd4150 rhgb quiet
     
* Desktop(s) Running (ps -eo comm= | grep -E '(gnome-session|startkde|startactive|xfce.?-session|fluxbox|blackbox|hackedbox|ratpoison|enlightenment|icewm-session|od-session|wmaker|wmx|openbox-lxde|openbox-gnome-session|openbox-kde-session|mwm|e16|fvwm|xmonad|sugar-session|mate-session|lxqt-session|cinnamon)' ):
     startkde
     
* Desktop(s) Installed (ls -m /usr/share/xsessions/ | sed 's/\.desktop//g' ):
     plasma
     
* SELinux Status (sestatus):
     SELinux status:                 enabled
     SELinuxfs mount:                /sys/fs/selinux
     SELinux root directory:         /etc/selinux
     Loaded policy name:             targeted
     Current mode:                   enforcing
     Mode from config file:          enforcing
     Policy MLS status:              enabled
     Policy deny_unknown status:     allowed
     Memory protection checking:     actual (secure)
     Max kernel policy version:      31
     
* SELinux Errors (selinuxenabled && journalctl --since yesterday |grep avc: | grep -Eo comm="[^ ]+" | sort |uniq -c |sort -rn):
           6 comm="mkdir"
     
* CPU Model (grep 'model name' /proc/cpuinfo | awk -F: '{print $2}' | uniq -c |
         sed -re 's/^ +//' ):
     16  AMD Ryzen 7 2700 Eight-Core Processor
     
* 64-bit Support (grep -q ' lm ' /proc/cpuinfo && echo Yes || echo No):
     Yes
     
* Hardware Virtualization Support (grep -Eq '(vmx|svm)' /proc/cpuinfo && echo Yes || echo No):
     Yes
     
* Load average (uptime):
      16:45:45 up 0 min,  3 users,  load average: 0.95, 0.27, 0.09
     
* Memory usage (free -m):
                   total        used        free      shared  buff/cache   available
     Mem:          32127        2589       28115           8        1423       29118
     Swap:         32767           0       32767
     
* Top 5 CPU hogs (ps axuScnh | awk '$2!=2510' | sort -rnk3 | head -5):
         1000  1793 86.8  4.6 270183692 1538688 ?   SNl  16:45   0:06 baloo_file
            0  1012 42.1  0.0 312156  7840 ?        Ssl  16:45   0:17 rngd
            0  2424 38.2  0.4 651168 132164 ?       Ssl  16:45   0:02 packagekitd
         1000  1798 25.2  0.6 3799208 225716 ?      Sl   16:45   0:02 plasmashell
            0     1 11.5  0.0 171588 14584 ?        Ss   16:44   0:06 systemd
     
* Top 5 Memory hogs (ps axuScnh | sort -rnk4 | head -5):
         1000  1793 87.1  4.6 270183692 1541580 ?   SNl  16:45   0:06 baloo_file
         1000  1798 25.2  0.6 3799208 225716 ?      Sl   16:45   0:02 plasmashell
            0  2424 38.2  0.4 651168 132164 ?       Ssl  16:45   0:02 packagekitd
         1000  2459  5.4  0.3 2020432 108884 ?      Sl   16:45   0:00 konsole
         1000  2247  5.2  0.3 2300092 118916 ?      Sl   16:45   0:00 akonadi_unified
     
* Disk space usage (df -hT):
     Filesystem     Type      Size  Used Avail Use% Mounted on
     devtmpfs       devtmpfs   16G     0   16G   0% /dev
     tmpfs          tmpfs      16G     0   16G   0% /dev/shm
     tmpfs          tmpfs      16G  1.8M   16G   1% /run
     tmpfs          tmpfs      16G     0   16G   0% /sys/fs/cgroup
     /dev/nvme0n1p5 ext4      394G  140G  235G  38% /
     tmpfs          tmpfs      16G   12K   16G   1% /tmp
     /dev/nvme0n1p6 ext4      2.0G  221M  1.7G  12% /boot
     /dev/nvme0n1p1 vfat       96M   74M   23M  77% /boot/efi
     tmpfs          tmpfs     3.2G  4.0K  3.2G   1% /run/user/988
     tmpfs          tmpfs     3.2G   44K  3.2G   1% /run/user/1000
     
* Block devices (without results: "blkid" AND "/sbin/blkid"):
     N/A

* PCI devices (lspci):
     00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Root Complex
     00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) I/O Memory Management Unit
     00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
     00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
     00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge
     00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
     00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
     00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
     00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59)
     00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
     00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
     00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
     00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
     00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
     00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
     00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
     00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
     00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
     01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
     02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43d0 (rev 01)
     02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01)
     02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01)
     03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
     03:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
     03:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
     03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
     03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
     03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01)
     06:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
     07:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
     09:00.0 USB controller: ASMedia Technology Inc. ASM1143 USB 3.1 Host Controller
     0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e7)
     0a:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
     0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function
     0b:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor
     0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Zeppelin USB 3.0 Host controller
     0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Renoir PCIe Dummy Function
     0c:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
     0c:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller
     
* USB devices (lsusb):
     Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
     Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
     Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
     Bus 003 Device 002: ID 1e7d:2dcd ROCCAT ROCCAT Kone Pure Owl-Eye
     Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
     Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
     Bus 001 Device 004: ID 2516:0067 Cooler Master Co., Ltd. MK750
     Bus 001 Device 003: ID 046d:0a1f Logitech, Inc. G930
     Bus 001 Device 002: ID 8087:0025 Intel Corp. 
     Bus 001 Device 005: ID 1b1c:0c13 Corsair H115i Platinum
     Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
     
* DRM Information (journalctl -k -b | grep -o 'kernel:.*drm.*$' | cut -d ' ' -f 2- ):
     [drm] amdgpu kernel modesetting enabled.
     fb0: switching to amdgpudrmfb from EFI VGA
     [drm] initializing kernel modesetting (POLARIS10 0x1002:0x67DF 0x1462:0x3418 0xE7).
     [drm] register mmio base: 0xFCE00000
     [drm] register mmio size: 262144
     [drm] add ip block number 0 <vi_common>
     [drm] add ip block number 1 <gmc_v8_0>
     [drm] add ip block number 2 <tonga_ih>
     [drm] add ip block number 3 <gfx_v8_0>
     [drm] add ip block number 4 <sdma_v3_0>
     [drm] add ip block number 5 <powerplay>
     [drm] add ip block number 6 <dm>
     [drm] add ip block number 7 <uvd_v6_0>
     [drm] add ip block number 8 <vce_v3_0>
     [drm] UVD is enabled in VM mode
     [drm] UVD ENC is enabled in VM mode
     [drm] VCE enabled in VM mode
     [drm] vm size is 128 GB, 2 levels, block size is 10-bit, fragment size is 9-bit
     [drm] Detected VRAM RAM=8192M, BAR=256M
     [drm] RAM width 256bits GDDR5
     [drm] amdgpu: 8192M of VRAM memory ready
     [drm] amdgpu: 8192M of GTT memory ready.
     [drm] GART: num cpu pages 65536, num gpu pages 65536
     [drm] PCIE GART of 256M enabled (table at 0x000000F400300000).
     [drm] Chained IB support enabled!
     [drm] Found UVD firmware Version: 1.130 Family ID: 16
     [drm] Found VCE firmware Version: 53.26 Binary ID: 3
     [drm] DM_PPLIB: values for Engine clock
     [drm] DM_PPLIB:         300000
     [drm] DM_PPLIB:         600000
     [drm] DM_PPLIB:         918000
     [drm] DM_PPLIB:         1167000
     [drm] DM_PPLIB:         1239000
     [drm] DM_PPLIB:         1282000
     [drm] DM_PPLIB:         1326000
     [drm] DM_PPLIB:         1366000
     [drm] DM_PPLIB: Validation clocks:
     [drm] DM_PPLIB:    engine_max_clock: 136600
     [drm] DM_PPLIB:    memory_max_clock: 200000
     [drm] DM_PPLIB:    level           : 8
     [drm] DM_PPLIB: values for Memory clock
     [drm] DM_PPLIB:         300000
     [drm] DM_PPLIB:         1000000
     [drm] DM_PPLIB:         2000000
     [drm] DM_PPLIB: Validation clocks:
     [drm] DM_PPLIB:    engine_max_clock: 136600
     [drm] DM_PPLIB:    memory_max_clock: 200000
     [drm] DM_PPLIB:    level           : 8
     [drm] Display Core initialized with v3.2.35!
     [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
     [drm] Driver supports precise vblank timestamp query.
     [drm] UVD and UVD ENC initialized successfully.
     [drm] VCE initialized successfully.
     [drm] fb mappable at 0xE0830000
     [drm] vram apper at 0xE0000000
     [drm] size 8294400
     [drm] fb depth is 24
     [drm]    pitch is 7680
     fbcon: amdgpudrmfb (fb0) is primary device
     amdgpu 0000:0a:00.0: fb0: amdgpudrmfb frame buffer device
     [drm] Initialized amdgpu 3.33.0 20150101 for 0000:0a:00.0 on minor 0
     
* Xorg modules (grep LoadModule /var/log/Xorg.0.log ~/.local/share/xorg/Xorg.0.log | cut -d \" -f 2 | xargs):
     glx amdgpu ati modesetting fbdev vesa fbdevhw fb dri2 glamoregl ramdac libinput
     
* GL Support (glxinfo | grep -E "OpenGL version|OpenGL renderer"):
     OpenGL renderer string: Radeon RX 580 Series (POLARIS10, DRM 3.33.0, 5.3.7-200.fc30.x86_64, LLVM 8.0.0)
     OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.7
     
* Xorg errors (grep '^\[.*(EE)' /var/log/Xorg.0.log ~/.local/share/xorg/Xorg.0.log | cut -d ':' -f 2- ):
     [    14.631] (EE) Failed to open authorization file "/var/run/sddm/{e91a9a81-89c9-4215-9aff-d75a28bcf2d8}": No such file or directory
     
* Kernel buffer tail (dmesg | tail):
     [   13.065210] virbr0: port 1(virbr0-nic) entered disabled state
     [   15.097565] igb 0000:06:00.0 enp6s0: igb: enp6s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
     [   15.206278] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
     [   15.708456] Bluetooth: RFCOMM TTY layer initialized
     [   15.708460] Bluetooth: RFCOMM socket layer initialized
     [   15.708492] Bluetooth: RFCOMM ver 1.11
     [   16.145066] xhci_hcd 0000:02:00.0: WARN: buffer overrun event for slot 2 ep 4 on endpoint
     [   19.090229] xhci_hcd 0000:02:00.0: WARN: buffer overrun event for slot 2 ep 4 on endpoint
     [   19.090235] retire_capture_urb: 3 callbacks suppressed
     [   45.671354] xhci_hcd 0000:02:00.0: WARN: buffer overrun event for slot 2 ep 4 on endpoint
     
* Last few reboots (last -x -n10 reboot runlevel):
     runlevel (to lvl 5)   5.3.7-200.fc30.x Thu Oct 31 16:45   still running
     reboot   system boot  5.3.7-200.fc30.x Thu Oct 31 16:45   still running
     runlevel (to lvl 5)   5.3.7-200.fc30.x Thu Oct 31 16:35 - 16:44  (00:08)
     reboot   system boot  5.3.7-200.fc30.x Thu Oct 31 16:35 - 16:44  (00:08)
     runlevel (to lvl 5)   5.3.7-200.fc30.x Thu Oct 31 14:40 - 16:34  (01:54)
     reboot   system boot  5.3.7-200.fc30.x Thu Oct 31 14:40 - 16:34  (01:54)
     runlevel (to lvl 5)   5.3.7-200.fc30.x Thu Oct 31 14:36 - 14:39  (00:03)
     reboot   system boot  5.3.7-200.fc30.x Thu Oct 31 14:36 - 14:39  (00:03)
     runlevel (to lvl 5)   5.3.7-200.fc30.x Thu Oct 31 14:10 - 14:36  (00:25)
     reboot   system boot  5.3.7-200.fc30.x Thu Oct 31 14:10 - 14:36  (00:25)
     
     wtmp begins Sat Jul 20 22:35:08 2019
     
* DNF Repositories (dnf repolist):
     repo id                     repo name                                     status
     code                        Visual Studio Code                                72
     *fedora                     Fedora 30 - x86_64                            56’582
     *fedora-modular             Fedora Modular 30 - x86_64                       135
     google-earth-pro            google-earth-pro                                   2
     *rpmfusion-free             RPM Fusion for Fedora 30 - Free                  616
     *rpmfusion-free-updates     RPM Fusion for Fedora 30 - Free - Updates        290
     *updates                    Fedora 30 - x86_64 - Updates                  13’737
     *updates-modular            Fedora Modular 30 - x86_64 - Updates             144
     
* DNF Extras (dnf -C list extras):
     Last metadata expiration check: 0:41:42 ago on Do 31 Okt 2019 16:04:08 CET.
     Extra Packages
     synology-cloud-station.x86_64              4.2.8-4421              @@commandline
     
* Last 20 packages installed (rpm -qa --nodigest --nosignature --last | head -20):
     qt5-qtbase-devel-5.12.5-1.fc30.x86_64         Do 31 Okt 2019 15:28:51 CET
     qt5-rpm-macros-5.12.5-1.fc30.noarch           Do 31 Okt 2019 15:28:50 CET
     mesa-libEGL-devel-19.1.7-1.fc30.x86_64        Do 31 Okt 2019 15:28:50 CET
     gpg-pubkey-be1229cf-5631588c                  Do 31 Okt 2019 15:09:43 CET
     cmake-3.14.5-1.fc30.x86_64                    Do 31 Okt 2019 15:05:45 CET
     cmake-data-3.14.5-1.fc30.noarch               Do 31 Okt 2019 15:05:44 CET
     libuv-1.33.0-2.fc30.x86_64                    Do 31 Okt 2019 15:05:43 CET
     jsoncpp-1.8.4-6.fc30.x86_64                   Do 31 Okt 2019 15:05:43 CET
     rhash-1.3.8-1.fc30.x86_64                     Do 31 Okt 2019 15:05:42 CET
     cmake-rpm-macros-3.14.5-1.fc30.noarch         Do 31 Okt 2019 15:05:42 CET
     qt-devel-4.8.7-49.fc30.x86_64                 Do 31 Okt 2019 15:04:53 CET
     mesa-libGLU-devel-9.0.0-17.fc30.x86_64        Do 31 Okt 2019 15:04:51 CET
     mesa-libGL-devel-19.1.7-1.fc30.x86_64         Do 31 Okt 2019 15:04:51 CET
     mesa-khr-devel-19.1.7-1.fc30.x86_64           Do 31 Okt 2019 15:04:51 CET
     libXft-devel-2.3.2-12.fc30.x86_64             Do 31 Okt 2019 15:04:51 CET
     libdrm-devel-2.4.99-1.fc30.x86_64             Do 31 Okt 2019 15:04:51 CET
     gl-manpages-1.1-18.20190306.fc30.noarch       Do 31 Okt 2019 15:04:51 CET
     freetype-devel-2.9.1-7.fc30.x86_64            Do 31 Okt 2019 15:04:51 CET
     fontconfig-devel-2.13.1-9.fc30.x86_64         Do 31 Okt 2019 15:04:51 CET
     expat-devel-2.2.8-1.fc30.x86_64               Do 31 Okt 2019 15:04:51 CET
     
* EFI boot manager output (efibootmgr -v):
     BootCurrent: 0002
     Timeout: 1 seconds
     BootOrder: 0002,0000
     Boot0000* Windows Boot Manager     HD(1,GPT,b0aa0b44-fdf8-4004-a727-3f89f0b02519,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}..._................
     Boot0002* Fedora   HD(1,GPT,b0aa0b44-fdf8-4004-a727-3f89f0b02519,0x800,0x32000)/File(\EFI\FEDORA\SHIM.EFI)..BO

Thank you already for taking the time to look over this if you came this far :slight_smile:

Hello @joelbusch, Welcome to the forum!
I don’t personally use SDDM, but it does look interesting so I may poke around with it. If you are using F30 Workstation, I think it would still default to the Gnome Keyring even as the KDE spin, and that could be the problem you are experiencing. SDDM doesn’t use the Gnome Keyring like GDM does but uses systemd-logind for session management, so maybe something there to look into.

Hi jakfrost, glad to be here thanks.
Okay I’m really out of my depth with this whole password storage aspect of the system.
From what I can tell both kwallet and keyring are installed:

$ dnf list --installed *keyring* *wallet* *secret* *pam*
Installed Packages
fprintd-pam.x86_64                                                                                               0.9.0-1.fc30                                                                                         @updates 
gnome-keyring.x86_64                                                                                             3.31.91-1.fc30                                                                                       @anaconda
gnome-keyring-pam.x86_64                                                                                         3.31.91-1.fc30                                                                                       @anaconda
kf5-kwallet.x86_64                                                                                               5.59.0-1.fc30                                                                                        @updates 
kf5-kwallet-libs.x86_64                                                                                          5.59.0-1.fc30                                                                                        @updates 
kwalletmanager5.x86_64                                                                                           18.12.2-1.fc30                                                                                       @anaconda
libsecret.x86_64                                                                                                 0.18.8-1.fc30                                                                                        @anaconda
libvirt-daemon-driver-secret.x86_64                                                                              5.1.0-9.fc30                                                                                         @updates 
pam.x86_64                                                                                                       1.3.1-17.fc30                                                                                        @anaconda
pam-kwallet.x86_64                                                                                               5.15.5-1.fc30                                                                                        @updates 
pam_krb5.x86_64                                                                                                  2.4.13-13.fc30                                                                                       @anaconda
systemd-pam.x86_64

And indeed when I open kWalletManager there is already a wallet named “kdewallet” open, and I see a VPN key and a Google Earth password in there.

SDDM seems to be configured to open kwallet and gnome-keyring if I’m interpreting this correctly:

$ cat /etc/pam.d/sddm
auth     [success=done ignore=ignore default=bad] pam_selinux_permit.so
auth        substack      password-auth
-auth        optional      pam_gnome_keyring.so
-auth        optional      pam_kwallet5.so
-auth        optional      pam_kwallet.so
auth        include       postlogin

account     required      pam_nologin.so
account     include       password-auth

password    include       password-auth

session     required      pam_selinux.so close
session     required      pam_loginuid.so
session     optional      pam_console.so
-session    optional    pam_ck_connector.so
session     required      pam_selinux.so open
session     optional      pam_keyinit.so force revoke
session     required      pam_namespace.so
session     include       password-auth
-session     optional      pam_gnome_keyring.so auto_start
-session     optional      pam_kwallet5.so auto_start
-session     optional      pam_kwallet.so auto_start
session     include       postlogin

The prepended - on the auth lines means to not log failures for unavailable modules according to the man page, so I’m thinking this configuration is just meant to unlock all that are available among keyring, kwallet and kwallet5.

I next decided to see if there are entries in the gnome-keyring, and because I couldn’t figure out a way to list all with secret-tools I just installed seahorse instead. There are four sections, I’ll mention them out of order:

  1. Certificates, which has “System Trust” and “Default Trust”. The former is empty, the latter contains a bunch of (null) entries issued by “No name” that appear empty.

  2. PGP Keys, which has “GnuPG keys” which is empty.

  3. Secure Shell, which has “OpenSSH keys” which contains my ssh private key

  4. Passwords, which has “Anmeldung” (German for login), which is locked.

Of course I tried to unlock “Anmeldung” and in the prompt that popped up it said: “The login keyring did not get unlocked when you logged into your computer.” which surprised me. Unlocking it with my login password worked and revealed it to be empty.

My instinct was to assume the keyring didn’t survive one of my upgrades, system reinstalls or language changes properly and I decided I should remove these two:

$ ls .local/share/keyrings/
login.keyring  user.keystore

As the archwiki proposes for resetting the keyring. After a reboot seahorse now shows an unlocked empty “Anmeldung” section. But nothing seems to have changed regarding the authorization file:

[    12.671] (EE) Failed to open authorization file "/var/run/sddm/{8b83cd74-a513-457e-9adb-aa3f2bb6a6be}": No such file or directory

or the line in journalctl that seemed related to the keyring:

Nov 01 09:43:34 hal9000 sddm-helper[1585]: gkr-pam: unable to locate daemon control file

Do you have other places I could poke?
Also could you explain why you suggested looking at the keyring in the first place, do you expect the authorization file can’t be found because sddm doesn’t have the proper rights?

Mainly I was going by sddm documentation I looked at, and specifically the differences between sddm and gdm. The error you are getting seems to be common when I search for it, but the fact there are different scenarios reported by users asking help regarding the same message, would seem to intuitively hint at a general “catch all in this category” message being issued by the developers for a collection of related errors. I will do some more reading and maybe even testing, but I am running Silverblue and not the traditional workstation, perhaps a VM is in order.