You are not logged in.
Pages: 1
My Q4OS is taking almost 1:30 minutes to start up
I have a computer manufactured in 2009 with a Core 2 Duo 2,793GH and 3GB of DDR2 RAM and no off board video card.
Every Debian and UNIX-Linux based operating system I've tested on it has always booted very very quickly.
When I installed Q4OS 3 Centaurus in 2019 it only needed about 16 seconds to be ready to use.
Earlier this year I needed to reinstall the operating system and decided to upgrade to Q4OS 4 Gemini.
I noticed right away that the new system took a long time to start up.
Even using an old machine your operating system has always worked perfectly for me with the exception of the time needed to start which suffered from this bloat.
Some more information:
I installed Q4OS-Debian on an ext4-formatted partition with 6GB of swap memory; I use GRUB 2 Bootloader to manage the boot of two other operating systems (Windows); not snapcore.
C:\home\russ> systemd-analyze blame
18.651s man-db.service
12.798s udisks2.service
11.044s logrotate.service
10.831s systemd-journal-flush.service
9.063s ModemManager.service
7.671s dev-sda2.device
6.709s NetworkManager-wait-online.service
6.131s apt-daily.service
5.692s NetworkManager.service
5.190s polkit.service
5.134s exim4-base.service
4.728s avahi-daemon.service
4.527s systemd-logind.service
4.522s wpa_supplicant.service
3.852s systemd-udevd.service
3.538s apparmor.service
2.387s exim4.service
2.357s rsyslog.service
1.993s e2scrub_reap.service
1.651s e2scrub_all.service
1.388s upower.service
996ms geoclue.service
941ms apt-daily-upgrade.service
924ms hddtemp.service
741ms lm-sensors.service
716ms user@1000.service
554ms systemd-modules-load.service
493ms tdm.service
439ms cups.service
428ms systemd-tmpfiles-setup-dev.service
383ms modprobe@drm.service
378ms dev-hugepages.mount
377ms dev-mqueue.mount
376ms sys-kernel-debug.mount
374ms sys-kernel-tracing.mount
365ms keyboard-setup.service
364ms kmod-static-nodes.service
363ms lvm2-monitor.service
363ms packagekit.service
361ms modprobe@configfs.service
359ms modprobe@fuse.service
345ms systemd-update-utmp.service
344ms systemd-sysusers.service
334ms systemd-journald.service
334ms systemd-udev-trigger.service
254ms systemd-random-seed.service
230ms alsa-restore.service
182ms systemd-sysctl.service
161ms tor.service
146ms tor@default.service
135ms systemd-timesyncd.service
110ms systemd-user-sessions.service
89ms systemd-tmpfiles-setup.service
81ms console-setup.service
41ms systemd-remount-fs.service
34ms systemd-tmpfiles-clean.service
16ms user-runtime-dir@1000.service
15ms systemd-update-utmp-runlevel.service
5ms sys-fs-fuse-connections.mount
4ms sys-kernel-config.mount
56us blk-availability.service
I'm a animal!
Offline
After initialization is completed the system works normally as usual.
I'm a animal!
Offline
Pages: 1