Q4OS Forum

hs1949

Member

Registered: 2021-10-20

Posts: 10

Q4OS slow on startup

Q4OS slow on startup. About 2 minutes. I haven't found an answer to this problem. (I'm new to Linux Q4OS, so I'm not used to command lines yet). Thanks for your help. hs1949

Q4OS lent au demarrage. Environ 2 minutes. Je n'ai pas trouvé de réponse à ce problème. (je suis nouvau sur Linux Q4OS, et donc pas encore habitué aux lignes de commndes). Merci pour votre aide. hs1949

kc1di

Member

From: SW Maine USA

Registered: 2021-05-07

Posts: 3

Re: Q4OS slow on startup

please go to a terminal and type this command and post the output back here.

systemd-analyze blame

hs1949

Member

Registered: 2021-10-20

Posts: 10

Re: Q4OS slow on startup

Hello, thank you very much for your answer. I will do this as soon as possible and I will send you the result of the analysis. Have a good day.

hs1949

Member

Registered: 2021-10-20

Posts: 10

Re: Q4OS slow on startup

Hello, here is the requested report. Thanks again in advance for more

27.951s man-db.service
18.608s snapd.service
13.237s NetworkManager-wait-online.service
12.369s udisks2.service
9.850s dev-sda1.device
9.738s nmbd.service
8.354s snapd.seeded.service
7.869s logrotate.service
6.716s dev-loop2.device
6.487s dev-loop5.device
6.471s dev-loop0.device
6.406s dev-loop3.device
6.201s dev-loop1.device
5.602s systemd-journal-flush.service
5.274s ModemManager.service
4.926s dev-loop4.device
4.855s systemd-udevd.service
4.838s polkit.service
4.349s avahi-daemon.service
4.251s NetworkManager.service
4.212s systemd-logind.service
4.210s wpa_supplicant.service
4.145s smbd.service
3.430s apparmor.service
lines 1-24...skipping...
27.951s man-db.service
18.608s snapd.service
13.237s NetworkManager-wait-online.service
12.369s udisks2.service
9.850s dev-sda1.device
9.738s nmbd.service
8.354s snapd.seeded.service
7.869s logrotate.service
6.716s dev-loop2.device
6.487s dev-loop5.device
6.471s dev-loop0.device
6.406s dev-loop3.device
6.201s dev-loop1.device
5.602s systemd-journal-flush.service
5.274s ModemManager.service
4.926s dev-loop4.device
4.855s systemd-udevd.service
4.838s polkit.service
4.349s avahi-daemon.service
4.251s NetworkManager.service
4.212s systemd-logind.service
4.210s wpa_supplicant.service
4.145s smbd.service
3.430s apparmor.service
2.529s cups.service
2.370s exim4.service
2.182s exim4-base.service
1.681s rsyslog.service
1.482s user@1000.service
1.362s systemd-modules-load.service
1.322s upower.service
  954ms systemd-sysusers.service
  897ms snap-bare-5.mount
  853ms colord.service
  760ms snap-core18-2285.mount
  726ms snap-gtk\x2dcommon\x2dthemes-1519.mount
  708ms lvm2-monitor.service
  690ms snap-gnome\x2d3\x2d28\x2d1804-162.mount
  689ms lm-sensors.service
  687ms systemd-random-seed.service
  682ms snap-remmina-4857.mount
  560ms modprobe@drm.service
  552ms rpcbind.service
  550ms systemd-tmpfiles-setup.service
  541ms binfmt-support.service
  522ms modprobe@fuse.service
  515ms systemd-tmpfiles-setup-dev.service
  472ms tdm.service
  470ms snap-snapd-14979.mount
  449ms e2scrub_reap.service
  434ms systemd-journald.service
  399ms hddtemp.service
  398ms keyboard-setup.service
  371ms systemd-rfkill.service
  368ms modprobe@configfs.service
  333ms packagekit.service
  319ms ufw.service
  275ms systemd-udev-trigger.service
  253ms run-rpc_pipefs.mount
  240ms systemd-update-utmp.service
  221ms systemd-sysctl.service
  187ms systemd-user-sessions.service
  174ms nfs-config.service
  166ms dev-disk-by\x2duuid-3fad3ccb\x2d7a56\x2d4f09\x2d9db7\x2d82f1da9f794f.swap
  136ms console-setup.service
  118ms proc-sys-fs-binfmt_misc.mount
  118ms systemd-remount-fs.service
   77ms systemd-timesyncd.service
   51ms systemd-tmpfiles-clean.service
   51ms dev-hugepages.mount
   50ms dev-mqueue.mount
   48ms sys-kernel-debug.mount
   47ms sys-kernel-tracing.mount
   45ms kmod-static-nodes.service
   36ms user-runtime-dir@1000.service
   22ms systemd-update-utmp-runlevel.service
   19ms alsa-restore.service
    2ms sys-kernel-config.mount
    2ms sys-fs-fuse-connections.mount
    1ms snapd.socket
   47us blk-availability.service
lines 20-81/81 (END)

eole73

Member

Registered: 2022-07-18

Posts: 8

Re: Q4OS slow on startup

Hello,
to avoid creating a new thread on this subject, I permit to use this one. For those of you who saw my last posts, I've installed Q4OS on 2009 Asus laptop. So everything's ok, but the boot is 2 min long.

The computer is used only to go checking some mails and write some texts, look at some photos, for a person who understand nothing about computer stuff (so do I sometimes I might say! ) , so there's no need to have a lot of things running on or in the background and time consuming, but just the essential stuff.

I looked at the system loading with 'systemd-analyze blame' and here is the result (I cut off below 5s):

francine@q4os-desktop:~$ systemd-analyze
Startup finished in 8.787s (kernel) + 1min 14.025s (userspace) = 1min 22.813s
graphical.target reached after 44.055s in userspace
francine@q4os-desktop:~$ systemd-analyze blame
53.438s man-db.service
21.115s udisks2.service
13.544s dev-sda1.device
11.769s systemd-journal-flush.service
10.777s NetworkManager-wait-online.service
 9.855s ModemManager.service
 9.655s NetworkManager.service
 9.438s exim4-base.service
 9.187s polkit.service
 8.455s avahi-daemon.service
 8.355s wpa_supplicant.service
 8.350s systemd-logind.service
 8.059s logrotate.service
 5.195s systemd-udevd.service
 ...

I'm wondering if I could disable man-db.service as it takes 53s to run? What consequences would it have if I disable it?
Is there another service I might disable without any or only minor consequences to save some time during the boot?

Last edited by eole73 (2022-07-26 13:44)