I think this message should be unrelated:
But you can apply the fix from this issue for a test.
Well it fixed that message.
Here’s the entire output of journalctl around the time of my last test with presentation mode off:
ct 25 09:26:04 dom0 qrexec-policy-daemon[2878]: qrexec: qubes.InputMouse+: sys-usb -> @adminvm: allowed to dom0
Oct 25 09:26:04 dom0 audit: BPF prog-id=73 op=LOAD
Oct 25 09:26:04 dom0 audit: BPF prog-id=74 op=LOAD
Oct 25 09:26:04 dom0 audit: BPF prog-id=75 op=LOAD
Oct 25 09:26:04 dom0 qrexec-policy-daemon[2878]: qrexec: qubes.InputKeyboard+: sys-usb -> @adminvm: allowed to dom0
Oct 25 09:26:04 dom0 kernel: audit: type=1334 audit(1729866364.264:420): prog-id=73 op=LOAD
Oct 25 09:26:04 dom0 kernel: audit: type=1334 audit(1729866364.264:421): prog-id=74 op=LOAD
Oct 25 09:26:04 dom0 kernel: audit: type=1334 audit(1729866364.264:422): prog-id=75 op=LOAD
Oct 25 09:26:04 dom0 systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
Oct 25 09:26:04 dom0 qrexec-policy-daemon[2878]: qrexec: qubes.InputKeyboard+: sys-usb -> @adminvm: allowed to dom0
Oct 25 09:26:04 dom0 systemd[1]: Started systemd-hostnamed.service - Hostname Service.
Oct 25 09:26:04 dom0 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succe>
Oct 25 09:26:04 dom0 kernel: audit: type=1130 audit(1729866364.303:423): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=?>
Oct 25 09:26:04 dom0 kernel: input: sys-usb: Hoksi Technology DURGOD Taurus K320 System Control as /devices/virtual/input/input44
Oct 25 09:26:04 dom0 kernel: input: sys-usb: Hoksi Technology DURGOD Taurus K320 Mouse as /devices/virtual/input/input45
Oct 25 09:26:04 dom0 qrexec-policy-daemon[2878]: qrexec: qubes.InputKeyboard+: sys-usb -> @adminvm: allowed to dom0
Oct 25 09:26:04 dom0 systemd-logind[1937]: Watching system buttons on /dev/input/event9 (sys-usb: Hoksi Technology DURGOD Taurus K320 System Control)
Oct 25 09:26:04 dom0 qrexec-policy-daemon[2878]: qrexec: qubes.InputKeyboard+: sys-usb -> @adminvm: allowed to dom0
Oct 25 09:26:04 dom0 kernel: input: sys-usb: Hoksi Technology DURGOD Taurus K320 Consumer Control as /devices/virtual/input/input46
Oct 25 09:26:04 dom0 kernel: input: sys-usb: Hoksi Technology DURGOD Taurus K320 Keyboard as /devices/virtual/input/input47
Oct 25 09:26:04 dom0 kernel: input: sys-usb: Hoksi Technology DURGOD Taurus K320 as /devices/virtual/input/input48
Oct 25 09:26:04 dom0 systemd-logind[1937]: Watching system buttons on /dev/input/event18 (sys-usb: Hoksi Technology DURGOD Taurus K320 Consumer Control)
Oct 25 09:26:04 dom0 systemd-logind[1937]: Watching system buttons on /dev/input/event19 (sys-usb: Hoksi Technology DURGOD Taurus K320 Keyboard)
Oct 25 09:26:04 dom0 systemd-logind[1937]: Watching system buttons on /dev/input/event20 (sys-usb: Hoksi Technology DURGOD Taurus K320)
Oct 25 09:26:04 dom0 qrexec-policy-daemon[2878]: qrexec: qubes.InputMouse+: sys-usb -> @adminvm: allowed to dom0
Oct 25 09:26:04 dom0 kernel: input: sys-usb: Logitech M315/M235 as /devices/virtual/input/input49
Oct 25 09:26:27 dom0 systemd[1]: Started getty@tty2.service - Getty on tty2.
Oct 25 09:26:27 dom0 kernel: audit: type=1130 audit(1729866387.527:424): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?>
Oct 25 09:26:27 dom0 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 09:26:33 dom0 audit[6950]: USER_AUTH pid=6950 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_unix acct="rbleidt" exe="/usr/bin/login" hostname=dom0 addr=? terminal>
Oct 25 09:26:33 dom0 audit[6950]: USER_ACCT pid=6950 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_unix acct="rbleidt" exe="/usr/bin/login" hostname=dom0 addr=? terminal=/de>
Oct 25 09:26:33 dom0 kernel: audit: type=1100 audit(1729866393.005:425): pid=6950 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_unix acct="rbleidt" exe="/usr/bin/login" >
Oct 25 09:26:33 dom0 kernel: audit: type=1101 audit(1729866393.005:426): pid=6950 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_unix acct="rbleidt" exe="/usr/bin/login" host>
Oct 25 09:26:33 dom0 audit[6950]: CRED_ACQ pid=6950 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_unix acct="rbleidt" exe="/usr/bin/login" hostname=dom0 addr=? terminal=/dev/tt>
Oct 25 09:26:33 dom0 audit[6950]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=3 a1=7ffe937e0c50 a2=4 a3=7ffe937e0964 items=0 ppid=1 pid=6950 auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=>
Oct 25 09:26:33 dom0 audit: PROCTITLE proctitle=2F62696E2F6C6F67696E002D70002D2D
Oct 25 09:26:33 dom0 kernel: audit: type=1103 audit(1729866393.006:427): pid=6950 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_unix acct="rbleidt" exe="/usr/bin/login" hostnam>
Oct 25 09:26:33 dom0 kernel: audit: type=1006 audit(1729866393.006:428): pid=6950 uid=0 old-auid=4294967295 auid=1000 tty=tty2 old-ses=4294967295 ses=4 res=1
Oct 25 09:26:33 dom0 kernel: audit: type=1300 audit(1729866393.006:428): arch=c000003e syscall=1 success=yes exit=4 a0=3 a1=7ffe937e0c50 a2=4 a3=7ffe937e0964 items=0 ppid=1 pid=6950 auid=1000 uid=0 gi>
Oct 25 09:26:33 dom0 kernel: audit: type=1327 audit(1729866393.006:428): proctitle=2F62696E2F6C6F67696E002D70002D2D
The "audit" messages are not something I'm familiar with. I don't see anything that pops out as a error. Any ideas?
Sorry, hit reply before finished.
Problem with no keyboard or mouse still there after applying " authselect select minimal" fix. Message about pam_sss is gone.
The "audit" messages are not something I'm familiar with. I don't see anything that pops out as a error. Any ideas?
I don’t see anything related in the log.
Just to be precise this is not a problem with not working keyboard/mouse but because your screen is frozen because of a screensaver:
Try to lock your screen, make sure that keyboard/mouse is working on locked screen, switch the KVM to another PC, then switch it back to Qubes OS PC and check if your screen is frozen or not.
I’m still testing this on overnight runs. My preliminary conclusion is:
Presentation mode off, then cold boot.
If the lock screen is triggered with ctrl-alt-L and the KVM switched away, on return the mouse and keyboard work, and I can login on the lock screen.
After doing that, I can switch away from an unlocked, open desktop and the problem does not occur.
If I reboot the machine and do not ever lock it, the problem does occur after switching away.
This would need more testing to be sure.
Maybe your system is suspending?
Check the power settings in dom0 and disable suspend if it’s enabled.
Suspend in system power settings was set to “never”
Display power management was turned on, I just set that to “off”.