I have been experiencing the exact same issue. I tried turning off the wifi and bluetooth as well as removing any external device but it didnāt change anything.
Donāt know if it helps but running /lib/systemd/systemd-udevd -D output the following codes :
1-7:1.0: SEQNUM=141434 blocked by SEQNUM=141257
0003:1770:FF00.8664: SEQNUM=141435 blocked by SEQNUM=141258
1-7:1.0: SEQNUM=141436 blocked by SEQNUM=141257
0003:1770:FF00.8637: Device (SEQNUM=141257, ACTION=remove) processed
0003:1770:FF00.8637: sd-device-monitor: Passed 348 byte to netlink monitor
1-7:1.0: Device (SEQNUM=141258, ACTION=unbind) ready for processing
1-7:1.0: sd-device-monitor: Passed 238 byte to netlink monitor
1-7:1.0: SEQNUM=141260 blocked by SEQNUM=141258
The issue is still the same for me. Iāve got used to restarting the services at boot. I try to look for someone reporting the same issue every now and then but nothing comes up. If I ever find anything I will post it here.
I have a MSI gaming laptop with a backlit keyboard. The backlit isnāt supported by default so I had to install this MSIKLM tool to make it work. When autostart is enabled, it creates a udev rules that is, for some reasons, incompatible with my setup. Removing the rules fixed the issue. I will create a post directly to the github to further investigate the problem.
Now in case your setup is different, here is what I did to figure out which device was creating the issue:
First I ran udevadm monitor to get the device name (which you already did).
Then I went to the corresponding folder at /sys/bus/usb/devices/1-7/1-7:1.0/. In there, there was a folder named 0003:1770:FF00.0EC2 which should rougly correspond to the name you get from udevadm monitor
I had a look around and found a file called uevent which gave me the name of the device, i.e my keyboard. From there, I just remembered than I had installed a package to manage the backlight of my keyboard and tried removing it.