There's a 25 second delay on launching gedit in Rawhide currently, for me. If I watch journalctl, I see this: (immediately on running 'gedit' as a regular user) Jan 08 12:13:35 adam.happyassassin.net dbus-daemon[912]: dbus[912]: [system] Activating via systemd: service name='o Jan 08 12:13:35 adam.happyassassin.net dbus[912]: [system] Activating via systemd: service name='org.freedesktop.Ava Jan 08 12:13:35 adam.happyassassin.net systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Jan 08 12:13:35 adam.happyassassin.net avahi-daemon[5275]: Daemon already running on PID 0 Jan 08 12:13:35 adam.happyassassin.net systemd[1]: avahi-daemon.service: main process exited, code=exited, status=25 Jan 08 12:13:35 adam.happyassassin.net systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack. Jan 08 12:13:35 adam.happyassassin.net systemd[1]: Unit avahi-daemon.service entered failed state. (25 seconds later) Jan 08 12:14:00 adam.happyassassin.net dbus-daemon[912]: dbus[912]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out Jan 08 12:14:00 adam.happyassassin.net dbus[912]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out Jan 08 12:14:00 adam.happyassassin.net gnome-session[2279]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a00007 (Unsaved Do) Jan 08 12:14:00 adam.happyassassin.net gnome-session[2279]: Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. and then gedit starts up. Note, I do have gedit set to run during session start, which could possibly be related somehow. Not sure if the bug here is in gedit, avahi or something else.
'ps aux | grep avahi' returns nothing. Perhaps the problem here is that the avahi stuff has moved into systemd, or something?
hum, looks like I had some stale files in /var/run/avahi-daemon, cleaning those out seems to have fixed it. Re-assigning to Avahi - I think if /var/run/avahi-daemon/pid is empty it shouldn't claim to be running as PID 0, but catch that something weird has happened and deal with it somehow.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.