Hi! Greetings from Brazil!
KDE freezes just before the desktop session is ready. This problem happens randomly, just about 20% of bootings. Only CTRL + ALT + F2 works on it and only rebooting may start the system normally.
If the system starts well, it works wonderfully.
However, it doesn’t happen to other systems, such as lastest Manjaro XFCE or lastest MX KDE, so it may be a bug related to Manjaro KDE only.
I collected some data regarding this problem:
inxi -F
System:
Host: wren4 Kernel: 5.10.105-1-MANJARO arch: x86_64 bits: 64
Desktop: KDE Plasma v: 5.24.3 Distro: Manjaro Linux
Machine:
Type: Desktop Mobo: INTEL model: H61 serial: <superuser required>
BIOS: American Megatrends v: 4.6.5 date: 02/19/2019
CPU:
Info: quad core model: Intel Core i5-2400 bits: 64 type: MCP cache:
L2: 1024 KiB
Speed (MHz): avg: 1796 min/max: 1600/3400 cores: 1: 2003 2: 1988 3: 1596
4: 1597
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
driver: i915 v: kernel
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
gpu: i915 resolution: 1440x900~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1)
v: 3.3 Mesa 21.3.7
Audio:
Device-1: Intel 7 Series/C216 Family High Definition Audio
driver: snd_hda_intel
Sound Server-1: ALSA v: k5.10.105-1-MANJARO running: yes
Sound Server-2: PulseAudio v: 15.0 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169
IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 0a:e0:af:b3:1a:a6
Drives:
Local Storage: total: 1.13 TiB used: 1.03 TiB (91.7%)
ID-1: /dev/sda vendor: A-Data model: SU630 size: 223.57 GiB
ID-2: /dev/sdb vendor: Western Digital model: WD10EZEX-00RKKA0
size: 931.51 GiB
Partition:
ID-1: / size: 39.07 GiB used: 26.36 GiB (67.5%) fs: ext4 dev: /dev/sda8
Swap:
ID-1: swap-1 type: partition size: 7.7 GiB used: 0 KiB (0.0%)
dev: /dev/sda5
Sensors:
System Temperatures: cpu: 29.8 C mobo: 27.8 C
Fan Speeds (RPM): N/A
Info:
Processes: 198 Uptime: 8m Memory: 7.65 GiB used: 1.94 GiB (25.4%)
Shell: Zsh inxi: 3.3.14
journalctl (last lines that don’t appear on normal booting)
mar 29 18:54:08 wren4 kded5[552]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
mar 29 18:54:13 wren4 baloo_file[612]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
mar 29 18:54:16 wren4 plasmashell[608]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
mar 29 18:54:17 wren4 python[654]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
mar 29 18:54:33 wren4 kded5[552]: kf.solid.backends.udisks2: Error getting props: "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
Those lines above repeat a lot when the system freezes.
journalctl -r _COMM=plasmashell
fev 12 23:14:35 wren4 plasmashell[551]: qt.svg: <input>:303:2223: Could not add child element to parent element because the types are incorrect.
fev 12 23:14:35 wren4 plasmashell[551]: qt.svg: <input>:303:1980: Could not add child element to parent element because the types are incorrect.
fev 12 23:14:35 wren4 plasmashell[551]: qt.svg: <input>:303:1739: Could not add child element to parent element because the types are incorrect.
fev 12 23:14:35 wren4 plasmashell[551]: qt.svg: <input>:303:1631: Could not add child element to parent element because the types are incorrect.
fev 12 23:14:35 wren4 plasmashell[551]: qt.svg: <input>:303:1453: Could not add child element to parent element because the types are incorrect.
fev 12 23:14:35 wren4 plasmashell[551]: qt.svg: <input>:303:1251: Could not add child element to parent element because the types are incorrect.
fev 12 23:14:35 wren4 plasmashell[551]: qt.svg: <input>:303:1049: Could not add child element to parent element because the types are incorrect.
fev 12 23:14:35 wren4 plasmashell[551]: qt.svg: <input>:303:913: Could not add child element to parent element because the types are incorrect.
fev 12 23:14:35 wren4 plasmashell[551]: qt.svg: <input>:303:659: Could not add child element to parent element because the types are incorrect.
fev 12 23:14:35 wren4 plasmashell[551]: qt.svg: <input>:303:463: Could not add child element to parent element because the types are incorrect.
fev 12 23:14:35 wren4 plasmashell[551]: qt.svg: <input>:303:258: Could not add child element to parent element because the types are incorrect.
fev 12 23:14:34 wren4 plasmashell[551]: kf.plasma.quick: Applet preload policy set to 1
fev 12 23:14:34 wren4 plasmashell[551]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
fev 12 23:14:34 wren4 plasmashell[551]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
fev 12 23:14:32 wren4 plasmashell[551]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
fev 12 23:14:32 wren4 plasmashell[551]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
journalctl -f results in a unstoppable loop of code…
It seems that the culprit is the kf.solid.backends.udisks2 because its error messages only appears when the system freezes.
I’ve looked the internet for this matter and tested a lot of things:
- Downgraded kernel from 5.15 LTS to 5.10 LTS
- Uninstalled dropbox (now using Maestral)
- Tested both BTRFS and EXT4 fresh systems
Can you guys help me?