Cannot connect to qrexec agent for 60 seconds

User Support
1

Hello,

After updating my system, from a fresh install of QubesOS I had noticed that I couldn’t use my USB keyboard and USB mouse at the login screen, so I had enabled autoskip in the grub config. Afterwards I checked the sys-USB which all seemed fine. But I noticed that my Fedora-40-xfce was down and couldn’t start it gives me the “Cannot connect to qrexec agent for 60 seconds” error. I increased the timeout to 300 seconds and it still gives me the same error. When looking in the logs (I can’t give you logs because I am completely unable to use my system. No sys-net, sys-firewall and sys-usb.) I notice that qubes-db.service fails, and than a lot of systemd dependencies fail. I have no idea on how to fix this. Can someone maybe help me with this issue?

1 Like
2

What hardware did you install Qubes OS on?

3

CPU = AMD Ryzen 5800x
Motherboard = Gigabyte B550 Aorus Master
GPU = AMD Radeon RX 6700 XT
SSD = Samsung NVME 970 pro
RAM = DDR4 32 GB Ram

1 Like
4

Did this hardware work with a previous version of Qubes? There is no entry for it in the Hardware Compatibility List.

5

Right before I upgraded it worked flawless (via the Qubes Updater), I just installed QubesOS on it, no idea if it works on previous versions. I noticed my IOMMU was set on Auto which I put on enabled right now. But still no result. I see that the B550M is supported but till QubesOS 4.1 I don’t know if that matters? I’m on the latest version 4.2.3

1 Like
6

What exactly did you updated with the Qubes Updater before you were unable to use your USB keyboard and mouse?

7

I updated dom0, debian-12-xfce and I had the error too when I tried to update fedora-40-xfce. But my sys-net and sys-usb were still working. I can check the install logs if you know where they are.

1 Like
8

Well I got it working again.

I saw that I was on a beta bios version that was taken off of the original website due to stability issues and I noticed that my time was also off, so I upgraded my BIOS to the latest stable version, enabled IOMMU and virtualization, and than reinstalled QubesOS with the correct time in the bios and QubesOS. Afterwards I upgraded once again and it all works now. I am guessing that the offset of the clock caused issues with upgrading and IOMMU too.

1 Like