Manjaro KDE crashes, cannot be restarted using systemctl


  1. plasmashell hangs when I try to mess around in the GUI, and I’m unable to restart it with systemctl (throws Unit plasmashell.service not found ).
  2. When I try to use powershell itself, it says that Qt couldn’t load it (paste unavailable for now).


  • Desktop Environment freezes often (mouse pointer can be moved)
  • Added 5.4.58 in favour of 5.7.15 and replaced graphics drivers.
  • If the setting through GUI fails, everything works properly for the same setting through TUI.
  • If I switch to a secondary tty terminal and do sudo systemctl restart sddm it stops sddm but doesn’t start it back up.
  • Manjaro Hello shows 20.1 Mikah when I’m running 20.0.3 Lysia (I switched from Manjaro GNOME 20.1rc to Manjaro KDE using a manual reinstallation from live bootable).

I have read a host of problems similar to this one all within 2020, possibly linked to 20.0.3 Lysia.


Output from mhwd:

[tulikam@tulika-hppavilionnotebook ~]$ sudo mhwd -li
> Installed PCI configs:
                  NAME               VERSION          FREEDRIVER           TYPE
video-hybrid-intel-nvidia-450xx-prime            2019.10.25               false            PCI
video-hybrid-intel-nvidia-440xx-prime            2019.10.25               false            PCI
     video-modesetting            2020.01.13                true            PCI

Warning: No installed USB configs!

Output from inxi:

[tulikam@tulika-hppavilionnotebook ~]$ sudo inxi -Fxxxza --no-host
[sudo] password for tulikam: 
Sorry, try again.
[sudo] password for tulikam: 
System:    Kernel: 5.4.58-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.4-x86_64 root=UUID=60db5b06-b7a3-4e80-8171-a302cf4a17d8 rw quiet apparmor=1 
           security=apparmor udev.log_priority=3 
           Console: tty 1 wm: kwin_x11 DM: SDDM Distro: Manjaro Linux 
Machine:   Type: Laptop System: HP product: HP Pavilion Notebook v: Type1ProductConfigId serial: <filter> Chassis: type: 10 
           serial: N/A 
           Mobo: HP model: 80A4 v: 91.19 serial: <filter> UEFI: Insyde v: F.54 date: 09/22/2015 
Battery:   ID-1: BAT0 charge: 23.7 Wh condition: 23.7/23.7 Wh (100%) volts: 16.8/14.8 model: Hewlett-Packard Primary 
           type: Li-ion serial: N/A status: Full 
CPU:       Topology: Dual Core model: Intel Core i5-6200U socket: BGA1168 (U3E1) note: check bits: 64 type: MT MCP 
           arch: Skylake family: 6 model-id: 4E (78) stepping: 3 microcode: D6 L1 cache: 128 KiB L2 cache: 3072 KiB 
           L3 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19204 
           Speed: 2709 MHz min/max: 400/2800 MHz base/boost: 2000/2400 volts: 0.8 V ext-clock: 100 MHz Core speeds (MHz): 
           1: 2702 2: 2700 3: 2700 4: 2700 
           Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable 
           Type: l1tf mitigation: PTE Inversion 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling 
           Type: srbds status: Vulnerable: No microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:1916 
           Device-2: NVIDIA GM108M [GeForce 940M] driver: nvidia v: 450.57 alternate: nouveau,nvidia_drm bus ID: 01:00.0 
           chip ID: 10de:1347 
           Device-3: Realtek HP Truevision HD type: USB driver: uvcvideo bus ID: 1-3:3 chip ID: 0bda:57c4 serial: <filter> 
           Display: server: X.Org 1.20.8 compositor: kwin_x11 driver: modesetting,nvidia 
           alternate: fbdev,intel,nouveau,nv,vesa display ID: :0 screens: 1 
           Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") s-diag: 414mm (16.3") 
           Monitor-1: eDP-1 res: 1366x768 hz: 60 dpi: 101 size: 344x194mm (13.5x7.6") diag: 395mm (15.5") 
           OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 20.1.5 direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel 
           alternate: snd_soc_skl bus ID: 00:1f.3 chip ID: 8086:9d70 
           Sound Server: ALSA v: k5.4.58-1-MANJARO 
Network:   Device-1: Realtek RTL8723BE PCIe Wireless Network Adapter vendor: Hewlett-Packard driver: rtl8723be v: kernel 
           port: 4000 bus ID: 03:00.0 chip ID: 10ec:b723 
           IF: wlo1 state: up mac: <filter> 
           Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 
           bus ID: 04:00.0 chip ID: 10ec:8136 
           IF: eno1 state: down mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 14.47 GiB (1.6%) 
           ID-1: /dev/sda vendor: Toshiba model: MQ01ABD100 family: 2.5" HDD MQ01ABD... size: 931.51 GiB block size: 
           physical: 4096 B logical: 512 B sata: 3.0 speed: 6.0 Gb/s rotation: 5400 rpm serial: <filter> rev: 2C temp: 42 C 
           scheme: GPT 
           SMART: yes state: enabled health: PASSED on: 332d 22h cycles: 3470 Old-Age: g-sense error rate: 21284 
Partition: ID-1: / raw size: 931.22 GiB size: 915.60 GiB (98.32%) used: 14.47 GiB (1.6%) fs: ext4 block size: 4096 B 
           dev: /dev/sda2 
Swap:      Alert: No Swap data was found. 
Sensors:   System Temperatures: cpu: 67.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 186 Uptime: 20m Memory: 15.48 GiB used: 1.09 GiB (7.0%) Init: systemd v: 245 Compilers: gcc: 10.1.0 
           Packages: pacman: 1204 lib: 321 flatpak: 0 Shell: Bash (sudo) v: 5.0.18 running in: yakuake inxi: 3.1.05 

Hello and welcome,

You should remove this drivers. AFAIK do not influence the functionality of the latest driver, but i can’t be 100% sure tho.

In rest, i recommend the same thing as here:

Give it a try and report back.


Hello, I think this is not the way to go: In the old forum there was a tutorial or two how to get optimus-manager to work. See here:

It feels too experimental and I think it risks further breakages. I’m not sure I want to move forward with this.
I can’t access any image from the archived forum, so it’s already crossed into risky waters in my head.

You should remove this drivers. AFAIK do not influence the functionality of the latest driver, but i can’t be 100% sure tho.

I’ll remove the 440xx and video-modesetting for now.

Probably 2+ years ago it was experimental, when it started, but for at least 6 months was the most successful option and also offers the most of hybrid GPU combination.

Let us know how it works.

1 Like

Can’t remove video-modesetting since it’s a dependency for 450xx. Removed 440xx and rebooting.

Any idea why it’s slow every time?

EDIT: triggering reboot logs a bunch of PCIEport errors before powering off.

Attempting to repro by crashing plasmashell by doing the following:

  • Opening Edit Widgets… from anywhere.
  • Selecting More Options…
  • Attempting to close the GUI window

I’ve also resolved to try using optimus-manager.

However, I can’t find optimus-manager-qt using pamac.

EDIT: nvm it’s beause AUR wasn’t enabled.

Is an AUR package, you need to enable AUR in Pamac > Preferences
Also you can run from terminal:
pamac build optimus-manager-qt

aaaand there’s our first non-responsive GUI, <sarcastic>good job debugging GUI with a GUI, self</sarcastic>!

Not to impose, but I have another concurrent issue on another thread, is there a way I can refer you to it?

I don’t find any of the conf files reported in the forum post, but a xorg.conf.d in /etc/X11/. Should I go ahead with renaming?

i can’t really provide any suggestion to solve the issue, but maybe you can save yourself some reboots with nohup plasmashell --replace & when it crashes again :slight_smile:

I guess I can kill non-compliant plasmashell processes with htop as well, but does your command do something better than that?

I also got a Failed to start Journal Service this time.

i don’t think so - it’s just a neat oneliner i used back when i had plasma crashing often (was a faulty ram stick in my case)

@Termy @bogdancovaciu I successfully got optimus-manager installed but it complains that I haven’t set up a power management plan in my nvidia driver. How should I do that?

I repro’d my crash - it’s worse than before - takes the entire DE with it. nohup doesn’t work.

I find that my kernel is now automagically 5.4.58-1-MANJARO.

I repro’d yet again and the error message came (this time on Hybrid mode, again).


  1. plasmashell hangs when I try to mess around in the GUI, and I’m unable to restart it with systemctl (throws Unit plasmashell.service not found ).

  2. I follow this repo:

    • Find Edit Widget...
    • Select Configure Desktop...
    • Attempt to close the window

    Sometimes I get a neat error popup asking me to terminate plasmashell, and sometimes even that doesn’t show up.

  3. I’m currently using optimus-manager to no special effect on this problem as a suggested fix attempt.