LL5 very slow start

[robonlinux]

Hi all, LL5 on Lenovo G50-30 Notebook taking a long time to load  - this seems to be the important bit.  Any help greatly appreciated.
[  43.868289] Bluetooth: BNEP (Ethernet Emulation) ver 1.3[  43.868292] Bluetooth: BNEP filters: protocol multicast
[  43.868300] Bluetooth: BNEP socket layer initialized
[  43.927832] NET: Registered protocol family 38
[  48.587704] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
[  48.707804] r8169 0000:03:00.0 enp3s0: Link is Down
[  54.261819] wlp2s0: authenticate with a6:91:b1:4f:36:55
[  54.265366] wlp2s0: send auth to a6:91:b1:4f:36:55 (try 1/3)
[  54.266403] wlp2s0: authenticated
[  54.274207] wlp2s0: associate with a6:91:b1:4f:36:55 (try 1/3)
[  54.275404] wlp2s0: RX AssocResp from a6:91:b1:4f:36:55 (capab=0x1011 status=0 aid=2)
[  54.285296] wlp2s0: associated
[  55.323135] wlp2s0: Limiting TX power to 36 (36 - 0) dBm as advertised by a6:91:b1:4f:36:55
[  55.324024] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[  58.726326] kauditd_printk_skb: 19 callbacks suppressed
[  58.726332] audit: type=1400 audit(1594720343.759:31): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=983 comm="cups-browsed" capability=23  capname="sys_nice"
[  78.132780] Bluetooth: RFCOMM TTY layer initialized
[  78.132793] Bluetooth: RFCOMM socket layer initialized
[  78.132810] Bluetooth: RFCOMM ver 1.11
[  89.806872] logitech-hidpp-device 0003:046D:4062.0006: HID++ 4.5 device connected.
[  110.106504] logitech-hidpp-device 0003:046D:405E.0005: multiplier = 8

[Lite Wise]

Try to find which part of the boot procedure is slowing down the system so you know where to focus on.
You can use the following commands in Terminal:

Code:

systemd-analyze

and

Code:

systemd-analyze blame

[Liteneasy]

Lite Wise thanks for your interest.  The output of commands suggested is:
systemd-analyze
Startup finished in 10.721s (kernel) + 1min 6.263s (userspace) = 1min 16.984s
graphical.target reached after 1min 6.235s in userspace
40.209s networking.service                                 
30.337s blueman-mechanism.service                           
24.998s networkd-dispatcher.service                         
18.606s NetworkManager-wait-online.service                 
14.510s systemd-journal-flush.service                       
13.973s udisks2.service                                     
11.892s accounts-daemon.service                             
11.601s ModemManager.service                               
11.584s NetworkManager.service                             
11.243s dev-sda5.device                                     
10.349s polkit.service                                     
9.048s avahi-daemon.service                               
9.034s bluetooth.service                                   
8.333s switcheroo-control.service                         
8.267s thermald.service                                   
8.259s systemd-logind.service                             
8.244s wpa_supplicant.service                             
4.992s gpu-manager.service                                 
4.377s systemd-resolved.service                           
3.785s rsyslog.service                                     
3.378s apparmor.service                                   
3.241s preload.service                                     
3.063s lightdm.service

And output from dmesg from the 40 sec mark:
  42.728643] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  42.728647] Bluetooth: BNEP filters: protocol multicast
[  42.728655] Bluetooth: BNEP socket layer initialized
[  42.821093] NET: Registered protocol family 38
[  51.353975] kauditd_printk_skb: 19 callbacks suppressed
[  51.353979] audit: type=1400 audit(1602917429.451:31): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=839 comm="cups-browsed" capability=23  capname="sys_nice"
[  56.929164] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
[  57.051605] r8169 0000:03:00.0 enp3s0: Link is Down
[  61.515942] wlp2s0: authenticate with a6:91:b1:4f:36:55
[  61.519041] wlp2s0: send auth to a6:91:b1:4f:36:55 (try 1/3)
[  61.520034] wlp2s0: authenticated
[  61.526300] wlp2s0: associate with a6:91:b1:4f:36:55 (try 1/3)
[  61.527644] wlp2s0: RX AssocResp from a6:91:b1:4f:36:55 (capab=0x1011 status=0 aid=3)
[  61.535073] wlp2s0: associated
[  61.658047] wlp2s0: Limiting TX power to 23 (23 - 0) dBm as advertised by a6:91:b1:4f:36:55
[  61.658977] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[  84.324584] Bluetooth: RFCOMM TTY layer initialized
[  84.324610] Bluetooth: RFCOMM socket layer initialized
[  84.324639] Bluetooth: RFCOMM ver 1.11
[  96.332234] logitech-hidpp-device 0003:046D:4062.0006: HID++ 4.5 device connected.

Any other ideas.  I'm using an Logitech wireless integrated mouse/keyboard and a wireless headset although that is not usually turned on at start up.
Cheers Rob

[Lite Wise]

If you are not using bluetooth I should disable the service during startup since it cost you some time.
Don't see really shocking issues here to be honest.
Maybe IPv6 slows it down. You can try to boot without your wireless enabled to see if it makes a difference too.