Created attachment 1001544 [details]
Since around March 6th, my Fedora 22 desktop system has frequently failed to boot properly.
Unfortunately the last time I booted the system before that was February 23rd, so there's quite a big list of possible changes in there.
I have tried downgrading from systemd-219-8.fc22 to systemd-219-5.fc22 and from kernel-4.0.0-0.rc3.git1.2 to 3.20.0-0.rc0.git10.1.fc22; neither seems to change anything, the bug still happens.
When the boot fails, various services don't attempt to start for some time, and when they try and start, many fail. The system never manages to start any consoles or gdm.
From the debug console (tty9), running 'systemctl' appears to do nothing for a long time, then shows an error like "Failed to register match for disconnected message".
I will attach logs of both failed and successful boots with systemd.log_level = debug.
The boot fails on average ~3 in 4 times.
Created attachment 1001545 [details]
In the upcoming systemd update there's a fix for socket path handling. I'm not sure if this could be the same issue, but it'd be good if you could test if it helps.
systemd-219-9.fc22 has been submitted as an update for Fedora 22.
Nope, sorry, doesn't help :/ saw the bug on 2 of 3 test boots with 219-9.
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-219-9.fc22'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
This is definitely a bug in 219. I have the same issue with my rhel build.
Unfortunately on my machine it occurs quite rarely so its hard to debug.
I see similar problem, my case is described in bug 1204023.
Lukas: it occurs frequently for me, I'm happy to do any debugging anyone requests, but I'd really like to see this fixed. It's kind of unfortunate that my system neither starts up nor shuts down properly most of the time! (I suffer from one or other of the bugs in the disaster zone that is https://bugzilla.redhat.com/show_bug.cgi?id=1088619 ).
Just guessing... This could be the same problem:
Martin Pitt is reverting commit 13790add4bf648fed816361794d8277a75253410 in Ubuntu as a workaround.
I just tested with systemd-219-11.fc22 and 8 boots in a row didn't hit the bug once. It may be a bit early to declare 'mission accomplished', but it looks good.
zbyszek, any chance you could submit an update for 219-11?
I just applied all v219-stable patches on top of our package, and re-applied 13790a again (i. e. dropped the revert). I now get the boot failures again, so I'm afraid the patches in v219-stable aren't sufficient.
Hum, interesting. So either I got really lucky yesterday, or we're actually seeing two different bugs, or (I suppose) latest stable changes things enough to hide whatever's triggering the bug when I boot my system, but not to fix your reproducer...
Good news! It seems this got finally fixed (involuntarily) in upstream git master, and the patch cleanly backports to 219. See
for the details.
+1 resurrection of kittens
Is this already fixed in F22?
I came here via a search on 'fedora 22 avahi-daemon fails'.
avahi-daemon fails to start on one of my servers, but not on others
(In reply to Ferry Huberts from comment #15)
> Is this already fixed in F22?
> I came here via a search on 'fedora 22 avahi-daemon fails'.
> avahi-daemon fails to start on one of my servers, but not on others
Nevermind, this was an install failure for the avahi package: the avahi user was not created.
I've seen this with the tcpdump packages as well.
I think there might be some rpm/dnf issue there.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.