KDE remains black but apps work, Screensaver works


Hello, I installed Manaro KDE yesterday using Architect and yesterday everything was working fine, I even rebooted a couple of times. Today when I login into the whole DE remains black but Manjaro Hello and terminal can be launched just fine. Also the screensaver works completely fine. Any ideas what I can do to have a working DE?

We can try to run a little script to try and install the main parts of KDE.
Also .. orient mirrors and clear cache for clean files..

paccache -rvk0
sudo pacman-mirrors -f
DONATOR=https://gitlab.manjaro.org/profiles-and-settings/iso-profiles/-/raw/master/manjaro/kde/Packages-Desktop; DONATION=$(wget -qO- $DONATOR | awk '/##/{f=0} f; /Plasma5/{f=1}' | sed '/^>/ d' | awk '{ print $1 }'); sudo pacman -Syyu $DONATION

Did you install any themes?

Interesting, does it pull the default configs down?

No .. just the most important packages (that are particular to KDE)

So equivelant of sudo pacman -S plasma kf5 ?

no - because its made off of our list of plasma desktop packages .. see the link/list:
And its extendable, changeable to include/discount what would be preferred from that list .. the one posted here is pretty close to the plasma group though.

1 Like

Thanks for the explanation, I find regex and sed hard to read :smiley:

Doesnt everyone? Unless you were already a knowledgeable programmer in the 70's .. or a robot :robot:

1 Like

Thanks for the reply! :smiley: Tried the commands, nothing changed. still exact same behaviour.

Ok .. maybe we can see by either looking through the logs:

journalctl -xb -p3

Or .. also you could try starting a bit more manually .. such as instead of logging in, go to TTY (Ctrl+Alt+F3) and login there, and run startplasma-x11

Either way it might also be helpful to get the inxi:

inxi -Fxxxza --no-host

startplasma-x11 tells me Display is not set or cannot connect to the XServer.

inxi -Fxxxza --no-host gives the following result:

  Kernel: 5.7.9-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.1.0 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.7-x86_64 
  root=UUID=c97ed37f-b953-4f5b-8485-225d45bdfa6d rw quiet 
  Desktop: KDE Plasma 5.19.3 tk: Qt 5.15.0 wm: gnome-shell dm: SDDM 
  Distro: Manjaro Linux 
  Type: Desktop Mobo: ASUSTeK model: P6T v: Rev 1.xx serial: <filter> 
  BIOS: American Megatrends v: 1408 date: 09/21/2010 
  Topology: Quad Core model: Intel Core i7 920 bits: 64 type: MT MCP 
  arch: Nehalem family: 6 model-id: 1A (26) stepping: 5 microcode: 1D 
  L2 cache: 8192 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 42777 
  Speed: 1604 MHz min/max: 1600/2668 MHz boost: enabled Core speeds (MHz): 
  1: 1604 2: 1604 3: 1604 4: 1604 5: 1604 6: 1604 7: 1604 8: 1604 
  Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; 
  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: Not affected 
  Type: tsx_async_abort status: Not affected 
  Device-1: AMD Cayman XT [Radeon HD 6970] vendor: PC Partner Limited 
  driver: radeon v: kernel bus ID: 02:00.0 chip ID: 1002:6718 
  Display: x11 server: X.Org 1.20.8 driver: radeon FAILED: ati 
  unloaded: modesetting alternate: fbdev,vesa compositor: gnome-shell 
  resolution: 1920x1080~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: AMD CAYMAN (DRM 2.50.0 / 5.7.9-1-MANJARO LLVM 10.0.0) 
  v: 4.3 Mesa 20.1.3 compat-v: 3.1 direct render: Yes 
  Device-1: Intel 82801JI HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 00:1b.0 chip ID: 8086:3a3e 
  Device-2: AMD Cayman/Antilles HDMI Audio [Radeon HD 6930/6950/6970/6990] 
  vendor: PC Partner Limited driver: snd_hda_intel v: kernel bus ID: 02:00.1 
  chip ID: 1002:aa80 
  Sound Server: ALSA v: k5.7.9-1-MANJARO 
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK M3A78 Series driver: r8169 v: kernel port: e800 
  bus ID: 06:00.0 chip ID: 10ec:8168 
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Local Storage: total: 251.53 GiB used: 19.14 GiB (7.6%) 
  ID-1: /dev/sda vendor: Corsair model: Force GT size: 111.79 GiB 
  block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
  serial: <filter> rev: 2 scheme: MBR 
  ID-2: /dev/sdb vendor: Western Digital model: WD1500HLFS-01G6U0 
  size: 139.74 GiB block size: physical: 512 B logical: 512 B 
  speed: 1.5 Gb/s rotation: 10000 rpm serial: <filter> rev: 4V01 scheme: MBR 
  ID-1: / raw size: 111.29 GiB size: 109.04 GiB (97.98%) 
  used: 19.14 GiB (17.6%) fs: ext4 dev: /dev/sda2 
  System Temperatures: cpu: 46.0 C mobo: N/A gpu: radeon temp: 53 C 
  Fan Speeds (RPM): N/A gpu: radeon fan: 0 
  Processes: 259 Uptime: 1h 09m Memory: 7.76 GiB used: 1.55 GiB (19.9%) 
  Init: systemd v: 245 Compilers: gcc: 10.1.0 Shell: bash v: 5.0.18 
  running in: gnome-terminal inxi: 3.0.37 

journalctl -xb -p3 gives the following in the end:

-- Defined-By: systemd
-- Support: https://archived.forum.manjaro.org/c/technical-issues-and-assistance
-- Documentation: man:core(5)
-- Process 17366 (plasmashell) crashed and dumped core.
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Jul 20 22:51:21  systemd-coredump[17814]: Process 17310 (kwin_x11) of >
                                                   Stack trace of thread 17310:
                                                   #0  0x00007fda9ac6e355 n/a (>
-- Subject: Process 17310 (kwin_x11) dumped core
-- Defined-By: systemd
-- Support: https://archived.forum.manjaro.org/c/technical-issues-and-assistance
-- Documentation: man:core(5)
-- Process 17310 (kwin_x11) crashed and dumped core.
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
kernel: blk_update_request: I/O error, dev sda, secto>
kernel: ata6.00: revalidation failed (errno=-2)

...hm..what about

env Display=':0' startplasma-x11

Also .. this might have something to do with gdm ..

EDIT for your edit ..
hm. check also please pacman -Qs kwin

i need to go today but I'll try again tommorow cause it's not my PC.
Thanks for the help though! :smiley:

The result was the same with the Display=':0' command.

Was this on a cold boot or resuming from standby? Sounds like a bug which has affected a few on KDE since the 19.3 update.

Also see here
and here

1 Like

It was cold boot. Logging out and in doesn't change the behaviour. I've installed Gnome for the time being but I do want to get back on KDE at some point. :smiley: Thank you so much for the info! :smiley:

There are a couple of things to try:

lookandfeeltool -a org.kde.breeze.desktop
#log out/in

If that doesn't work:

cd /home/<your-username>/.config
mkdir plasma-old
mv *rc plasma-old/
mv kdeglobals plasma-old/

This backs up your configs, the reboot recreates the defaults. If it doesn't work you can copy them back.

1 Like

Slightly different then it would seem. I've not been able to recreate the issue on a cold boot but have seen a few reports of trouble logging out and back in.

No joy, it was worth a try though. I must say, that new Breath theme is snappy, I almost kept it.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by