I’m using Manjaro KDE and after entering my password first I have to wait several seconds (like 10 or so) then I see a black screen than Yakukake is displayed for several seconds (again 10 or so) then the background image appears (the bing daily wallpaper is set up to be used) then my widgets appear then the bottom bar (dunno what’s it called) appears then the status bar (well where things like network connection, notifications, languages, etc. reside) appears on the LEFT side of that bar then these icons move to the RIGHT and the pinned application icons and the Application Launcher appears on the LEFT as it should. I didn’t used to see this process so it was much faster or it didn’t occur at all. Except that I really don’t think I should be waiting this much for boot with an i5 9600K and 32 GB RAM even with a HDD plus it used to be faster.
The output of systemd-analyze:
Startup finished in 15.053s (firmware) + 2.902s (loader) + 2.247s (kernel) + 14.199s (userspace) = 34.403s
graphical.target reached after 13.376s in userspace
Output of 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.
└─snapd.service @9.137s +4.238s
└─snapd.socket @9.132s +394us
└─systemd-timesyncd.service @8.806s +325ms
└─systemd-tmpfiles-setup.service @8.642s +145ms
└─home.mount @8.584s +55ms
└─systemd-fsck@dev-disk-by\x2duuid-e001cc6f\x2d2f73\x2d4c08\x2d8745\x2d7169d4f925a7.service @8.412s +154ms
I’ve already disabled and masked lvm2-monitor and ModemManager services (just following other ppls solutions).
The output of systemd-analyze blame:
I supply further information on request, I just don’t know what else can be retrieved and how.
I’d like to get back my faster load times if possible Thank you.
An SSD would definitely help. Please post the output of
Hi, thank you for your contribution. I don’t have any spare ssds, and I don’t await anything like 3 sec boot, but I remember having nearly instant desktop loads after the splash screen after entering my password at login and it’s close to 10 seconds now (probably more). That’s why I suspect something’s wrong. I have to mention that my /home is on a separate partition and the OS has been reinstalled I think twice without wiping the /home partition. The long load times were present even before the reinstalls, I’m like 90% sure about that.
Whatever, the output of the command is:
Kernel: 5.8.18-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
root=UUID=01ab0f81-e7f6-41a6-8088-583afada7ba7 rw quiet apparmor=1
Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM
Distro: Manjaro Linux
Type: Desktop Mobo: Micro-Star model: H310M PRO-VDH PLUS (MS-7C09) v: 1.0
serial: UEFI: American Megatrends v: 1.30 date: 09/04/2019
Info: 6-Core model: Intel Core i5-9600K bits: 64 type: MCP arch: Kaby Lake
family: 6 model-id: 9E (158) stepping: D (13) microcode: DE
L2 cache: 9216 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Speed: 800 MHz min/max: 800/4600 MHz Core speeds (MHz): 1: 800 2: 800 3: 800
4: 800 5: 800 6: 800
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
mitigation: Speculative Store Bypass disabled via prctl and seccomp
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
Type: srbds mitigation: TSX disabled
Type: tsx_async_abort mitigation: TSX disabled
Device-1: NVIDIA TU104 [GeForce RTX 2070 SUPER] vendor: Micro-Star MSI
driver: nvidia v: 455.45.01 alternate: nouveau,nvidia_drm bus ID: 01:00.0
chip ID: 10de:1e84
Display: x11 server: X.Org 1.20.10 compositor: kwin_x11 driver: nvidia
display ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3")
s-diag: 583mm (23")
Monitor-1: HDMI-0 res: 1920x1080 dpi: 30 size: 1600x900mm (63.0x35.4")
diag: 1836mm (72.3")
OpenGL: renderer: GeForce RTX 2070 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01
direct render: Yes
Device-1: Intel 200 Series PCH HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:a2f0
Device-2: NVIDIA TU104 HD Audio vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel bus ID: 01:00.1 chip ID: 10de:10f8
Sound Server: ALSA v: k5.8.18-1-MANJARO
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel port: d000 bus ID: 02:00.0
chip ID: 10ec:8168
IF: enp2s0 state: up speed: 100 Mbps duplex: full mac:
Local Storage: total: 1.02 TiB used: 49.94 GiB (4.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda vendor: A-Data model: SU650 size: 111.79 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: rev: 428a
ID-2: /dev/sdb vendor: Western Digital model: WD10EZEX-75WN4A1
size: 931.51 GiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
rotation: 7200 rpm serial: rev: 7113 scheme: GPT
ID-1: / raw size: 100.00 GiB size: 97.93 GiB (97.93%)
used: 18.24 GiB (18.6%) fs: ext4 dev: /dev/sdb3
ID-2: /home raw size: 225.00 GiB size: 220.47 GiB (97.99%)
used: 31.69 GiB (14.4%) fs: ext4 dev: /dev/sdb4
Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: partition size: 6.27 GiB used: 0 KiB (0.0%) priority: -2
System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 32 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 24%
Processes: 226 Uptime: 3h 23m Memory: 31.31 GiB used: 4.24 GiB (13.5%)
Init: systemd v: 246 Compilers: gcc: 10.2.0 alt: 6 clang: 11.0.0
Packages: 1406 pacman: 1404 lib: 376 flatpak: 0 snap: 2 Shell: Bash
v: 5.0.18 running in: yakuake inxi: 3.1.08
Hoping for further replies
Please enclose terminal output within the
</> button so it is more easily readable.
Try to create a new user and test the boot process, just to make sure this isn’t something in your home data.
So I’ve created a new user and set up the Desktop as close to my original user’s as possible. Without the widgets and the daily wallpaper from bing I didn’t see the system tray appear on the left then after a few seconds pop to the right, it seemed as it appeared on the right right away. With all the widgets I did see the system tray appear on the left then pop to the right BUT it was like a blink of an eye compared to the time on my original account, where I literally see how the notification about network connection appears then it freezes (the filling circle around the closing x [the countdown until the notification disappears] just stops filling up), then everything pops back to it’s place. I haven’t timed it actually, but it seems it’s faster to log in to the newly created account but just by several seconds.
Hope this helped somewhat.
Oh and one more thing. After I’ve bought my video card I used the system as it was for a while (I’ve had an AMD video card for a short amount of time, then I’ve removed it and used the integrated graphics in my CPU, then installed the Nvidia card and the nvidia drivers and I don’t remember removing any other driver whatsoever), then funny things started to happen with the system, graphics-wise mostly, so I’ve decided to reinstall it. Again I’m not a 100% sure, but it comes back to me like, I begun to have these problems after that reinstall.
Hi there, I’m here to report, that another strange thing happened just now. So first, I’ve got an audio-video receiver and amplifier, that sometimes won’t show any video, and playing with selecting different inputs, turning the TV off/on, turning the amplifier off/on, unplugging and plugging the HDMI cables back in would solve that, but sometimes I have to restart the computer. This was the case today and I choose the reset button on the computer case. Afterwards I’ve typed my password in, pressed enter and now the screen didn’t turn black, but the login screen remained there, then Yakuake appeared and after several seconds my, desktop showed up and the popping thing with the system tray happened, but it was probably as fast as on the other user account I’ve created. BUT Yakuake and Konsole are now not transparent (I mean the background) and in the settings at Color Scheme and font, it says “This color scheme uses a transparent background which does not appear to be supported on your desktop”. I’ve had an update yesterday, but only pamac related programs have been updated (pamac-cli, pamac, … can’t remember all of them), so I don’t think that update changed something, but I was using the transparent backgrounds before I turned my PC off yesterday evening. I don’t know whether this adds some relevant information, but I wanted you to know about the situation.
I’ve googled a bit and I’ve had to turn the OpenGL detection on (it was written in the settings, that it caused crashes in KWin, hence it’s been turned off), and I’ve set the compositor to OpenGL 3.1, now the transparency is back. So i’m thinking, that actually when I haven’t seen anything on the screen (before resetting the PC) It might have been caused by some crash in the windowing system, but I’m still more inclined to the thought that amplifier was the culprit before.
Well, first of all, pressing the reset button to reboot the PC is a very bad habit. Why did you do that? You can corrupt partition data doing that. When you reboot or turn your PC off, the system always makes sure data is consistent. When you press the reset button you just cut the power off suddenly. Don’t do that unless you really can’t reboot or turn off your system properly. To make things worse, you have an HDD and you probably have default cache settings, which increases the amount of data which is delayed to be written to disk.
Regarding OpenGL, you did alright. I have no idea why it was deactivated, but, nowadays, not having graphical acceleration on a relatively modern PC is like going back 20 years.
Regarding the widgets, the wallpaper and etc., keep in mind the most stuff you have loading at boot, the longer it will take, and you have an HDD, which takes even longer.
Yeah I’ve had no visuals from the PC as I’ve mentioned, so either holding the power button or pressing the reset button remained as least drastic options, or at least nothing else came to my mind.