Why is OpenSUSE Tumbleweed taking ages to boot?

Hi all,
recently installed openSUSE and I can say I am loving it! However I noticed that it is taking anywhere from 2-4 mins to boot. The first time I booted it after installation it took seconds (should note this is on an ssd) but now it seems to be taking forever. I havent done anyting but install steam and nvidia drivers and a few other programs. Here is the first 3 lines of my systemd-analyze blame output
2min 3.902s btrfsmaintenance-refresh.service
2min 2.166s chrony-wait.service
1min 59s plymouth-quit-wait.service

I have no clue what these services are and why they are taking so long, please someone help!

If you inspect /etc/fstab, is btrfs present anywhere? If not:

 sudo zypper rm btrfs*

may be all you need to do. You seem to be describing https://bugzilla.opensuse.org/show_bug.cgi?id=1124823

You can use

systemctl cat chrony-wait.service

which will give you some information, and the relevant “man page”.

My system has:

erlangen:~ # systemd-analyze blame|head
    4min 14.403s fstrim.service
    1min 46.299s mlocate.service
         25.745s backup-albums.service
         12.977s backup-rpmdb.service
          3.799s systemd-networkd-wait-online.service
          2.848s display-manager.service
          2.424s plymouth-quit-wait.service
          1.348s systemd-logind.service
           656ms apparmor.service
           622ms mcelog.service
erlangen:~ # 

The above doesn’t matter. What really matters:

erlangen:~ # systemd-analyze critical-chain 
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

 **graphical.target @8.429s**
└─display-manager.service @5.580s +2.848s
  └─apache2.service @5.484s +95ms
    └─remote-fs.target @5.483s
      └─iscsi.service @5.477s +5ms
        └─network-online.target @5.474s
**          └─systemd-networkd-wait-online.service @1.673s +3.799s**
            └─systemd-networkd.service @1.178s +494ms
              └─network-pre.target @1.177s
                └─firewalld.service @897ms +279ms
                  └─dbus.service @895ms
                    └─basic.target @889ms
                      └─paths.target @889ms
                        └─cups.path @839ms
                          └─sysinit.target @837ms
                            └─apparmor.service @179ms +656ms
erlangen:~ # 

The times include the wait for network configuration.

When the machine stalls, click escape to get supplementary information from the splash screen.

Maybe a stop job is running?