Slow Boot Time on Fedora 31


Hi, Fedora people.

It takes my PC approximately 2min 30sec to log in. From power up to having the desktop fully functional. This is what systemd-analyze blame shows:

14.841s packagekit.service                                                                       
 9.115s firewalld.service                                                                        
 6.972s udisks2.service                                                                          
 6.423s accounts-daemon.service                                                                  
 6.118s NetworkManager-wait-online.service                                                       
 6.110s ModemManager.service                                                                     
 5.735s initrd-switch-root.service                                                               
 5.658s lvm2-monitor.service                                                                     
 5.070s systemd-udev-settle.service                                                              
 4.424s avahi-daemon.service                                                                     
 4.086s rtkit-daemon.service                                                                     
 4.050s systemd-logind.service                                                                   
 4.050s abrtd.service                                                                            
 3.437s dbus-broker.service                                                                      
 3.284s dracut-initqueue.service                                                                 
 2.803s gssproxy.service                                                                         
 2.514s upower.service                                                                           
 2.185s smartd.service                                                                           
 2.003s polkit.service                                                                           
 1.974s chronyd.service                                                                          
 1.914s rsyslog.service                                                                          
 1.741s media-Pel\xc3\xadculas.mount                                                             
 1.653s media-M\xc3\xbasica.mount                                                                
 1.526s lvm2-pvscan@8:6.service                                                                  
 1.057s systemd-fsck@dev-disk-by\x2duuid-d526c7b9\x2d3f3b\x2d424e\x2d8421\x2def3837a0dbfd.service
 1.023s systemd-udevd.service                                                                    
 1.021s user@1000.service                                                                        
  797ms systemd-fsck@dev-mapper-fedora_localhost\x2d\x2dlive\x2dhome.service                     
  754ms cups.service                                                                             
  750ms systemd-journald.service                                                                 
  747ms NetworkManager.service                                                                   
  652ms systemd-tmpfiles-setup-dev.service                                                       
  617ms systemd-vconsole-setup.service                                                           
  577ms home.mount                                                                               
  455ms systemd-udev-trigger.service                                                             
  433ms initrd-parse-etc.service                                                                 
  432ms geoclue.service                                                                          
  383ms boot.mount                                                                               
  375ms systemd-binfmt.service                                                                   
  371ms systemd-random-seed.service                                                              
  334ms colord.service

I understand very little about what this all means. What can I turn off? How do I do that? The step-by-step approach of any solution will help.


Can you also run systemd-analyze critical-chain in your terminal?

One thing for certain is that you can disable and mask ModemManager.service.

Hi, man; this is what I got: @30.447s
└─sddm.service @30.444s
  └─plymouth-quit.service @30.183s +223ms
    └─systemd-user-sessions.service @30.057s +37ms
      └─ @30.054s
        └─ @30.054s
          └─iscsi-shutdown.service @29.963s +582us
            └─ @29.953s
              └─NetworkManager.service @29.326s +625ms
                └─ @29.322s
                  └─firewalld.service @12.776s +16.545s
                    └─polkit.service @19.022s +2.634s
                      └─ @12.747s
                        └─dbus-broker.service @13.399s +4.544s
                          └─dbus.socket @12.731s
                            └─ @12.698s
                              └─systemd-update-utmp.service @12.654s +42ms
                                └─systemd-tmpfiles-setup.service @12.336s +224ms
                                  └─import-state.service @12.126s +207ms
                                    └─ @12.122s
                                      └─run-user-1000.mount @39.212s
                                        └─ @10.343s
                                          └─lvm2-monitor.service @4.507s +5.591s
                                            └─dm-event.socket @4.473s

Ok. How can I do that?

This is what systemd-analyze blame shows me today:

16.545s firewalld.service                                                                        
11.844s packagekit.service                                                                       
10.428s NetworkManager-wait-online.service                                                       
 9.631s udisks2.service                                                                          
 8.912s accounts-daemon.service                                                                  
 8.507s ModemManager.service                                                                     
 6.420s unbound-anchor.service                                                                   
 5.663s initrd-switch-root.service                                                               
 5.654s avahi-daemon.service                                                                     
 5.591s lvm2-monitor.service                                                                     
 5.177s abrtd.service                                                                            
 5.173s rtkit-daemon.service                                                                     
 5.156s systemd-logind.service                                                                   
 5.049s systemd-udev-settle.service                                                              
 4.544s dbus-broker.service                                                                      
 2.988s gssproxy.service                                                                         
 2.832s smartd.service                                                                           
 2.634s polkit.service                                                                           
 2.555s upower.service                                                                           
 2.283s dracut-initqueue.service                                                                 
 2.188s chronyd.service                                                                          
 1.654s media-Pel\xc3\xadculas.mount                                                             
 1.557s cups.service                                                                             
 1.496s rsyslog.service                                                                          
 1.353s media-M\xc3\xbasica.mount                                                                
 1.326s lvm2-pvscan@8:6.service                                                                  
 1.172s systemd-fsck@dev-disk-by\x2duuid-d526c7b9\x2d3f3b\x2d424e\x2d8421\x2def3837a0dbfd.service
 1.023s systemd-udevd.service                                                                    
  904ms systemd-fsck@dev-mapper-fedora_localhost\x2d\x2dlive\x2dhome.service                     
  878ms user@1000.service                                                                        
  708ms systemd-journald.service                                                                 
  649ms home.mount                                                                               
  634ms systemd-vconsole-setup.service                                                           
  630ms systemd-tmpfiles-setup-dev.service                                                       
  625ms NetworkManager.service                                                                   
  498ms boot.mount                                                                               
  479ms geoclue.service                                                                          
  429ms initrd-parse-etc.service                                                                 
  362ms systemd-udev-trigger.service                                                             
  352ms systemd-random-seed.service                                                              
  316ms systemd-binfmt.service

Run these three commands as root:

systemctl stop ModemManager.service
systemctl disable ModemManager.service
systemctl mask ModemManager.service

The first one stops it, the second keeps it from being started at boot and the last makes sure that it can’t be started by some other service or program.

1 Like

Ok. All three with systemctl stop, disable and mask commands? :thinking:

Of course. How else?

1 Like

Man, you said it was SAFE! Now my PC won’t even boot up! It gets stuck on Fedora’s screen. Now what do I do? What’s the solution?

I damaged my PC! Now it won’t even start! :rage:

That’s interesting…

I’ve been masking those three services for years on numerous computers and there was never a problem.
Maybe something else has happened that is the cause of your problem.

Press ESC key and check why is the boot process stuck.

1 Like

Man, which terminal am I gonna use those commands on? The PC won’t start!

Not at all?

If that is the case, you have a hardware fault which you need to repair…

I’ll try to describe the situation as best I can: when I turn on my PC, after the screen where it shows the installed kernels (there are usually three), it goes to the screen with the Fedora logo and gets stuck there. It does not start. It does not go past the Fedora screen.

When you get to the list of kernels, you should be able to use your cursor keys to select which kernel to boot. Try selecting the previous kernel, and if that boots, the issue is with the new kernel. If not, there should be a rescue option. That won’t get you a full system with a GUI, but it will allow you to correct whatever went wrong. If my memory’s not playing tricks with you, you’ll end up logged in as root. Try running these three commands:

systemctl unmask plymouth-quit.service
systemctl enable plyouth-quit.service

I picked that one to bring back because it’s the only one that I don’t personally know is safe to get rid of. Let us know if that works or if not, if it changes anything.

Great advice.
Also, try hitting the ESC key when you get at Fedora logo. This way you can see where the boot process stopped.

Ok, this is what ESC shows:

[FAILED] Failed to start Desktop Display Manager.
See ‘systemctl status sddm.service’ for details.

Ok, this worked. Thanks.

Interesting. I see you’re using KDE, am I right?
Somehow, this doesn’t happen on GNOME and XFCE…

I removed my initial suggestion to masksystemctl mask plymouth-quit.service