I hadn't seen this bug before today when I noticed that it's blocking my kernel in groovy-proposed. I upgraded systemd, and I am seeing this issue. But when I boot back to 5.4.0-37 the problem persists, so it doesn't seem to have anything to do with the 5.8 kernel.
It seems like a problem with apport-autoreport.service. I'm not an expert on debugging system units, but I get the impression it was constantly restarting -- it always seemed to be in the activating state, but with a different pid each time I checked. 'systemd list-jobs' also showed this service with a different job id each time I ran the command. I was finally able to get out of this state by running 'systemctl mask --runtime apport-autoreport.service'.
This clearly doesn't look like an issue with the 5.8 kernel since I also see it with 5.4, so I'm removing the block-proposed tag.
I hadn't seen this bug before today when I noticed that it's blocking my kernel in groovy-proposed. I upgraded systemd, and I am seeing this issue. But when I boot back to 5.4.0-37 the problem persists, so it doesn't seem to have anything to do with the 5.8 kernel.
It seems like a problem with apport- autoreport. service. I'm not an expert on debugging system units, but I get the impression it was constantly restarting -- it always seemed to be in the activating state, but with a different pid each time I checked. 'systemd list-jobs' also showed this service with a different job id each time I ran the command. I was finally able to get out of this state by running 'systemctl mask --runtime apport- autoreport. service' .
This clearly doesn't look like an issue with the 5.8 kernel since I also see it with 5.4, so I'm removing the block-proposed tag.