# KDE Still freezing

**URL:** <https://discuss.kde.org/t/kde-still-freezing/7662>\
**Category:** Help\
**Created:** [November 25, 2023, 7:32am UTC](https://discuss.kde.org/t/kde-still-freezing/7662 "2023-11-25T07:32:29Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![Balls](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/balls/32/5849_2.png) [@Balls](https://discuss.kde.org/u/Balls)\
**Post date:** [November 25, 2023, 7:32am UTC](https://discuss.kde.org/t/kde-still-freezing/7662/1 "2023-11-25T07:32:29Z")

</div>

In a prior post of mine I brought to your attention an issue I was having with freezing. The solution to that post concluded to be switching from Wayland to X11 however, I’m still experiencing freezes on X11. And I still have to reboot to get my PC to normal.

Again, if this isn’t fully fixable I would appreciate being let known of a way to restart my de from an arbitrary tty (e.g ctrl alt fn3) the usual stop and start plasmashell doesn’t work in tty’s, at least for me. I always get an error mentioning that xcb couldn’t connect. Sorry for the duplicate

System details:

- I use KDE plasma
- I use the X11 protocol
- I use arch linux
- I have two gpus. A dedicated NVIDIA one and an integrated Intel one (Which from what i’ve seen is used to render my desktop)

---

<div class="post-metadata">

**Author:** ![Duha](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/duha/32/32926_2.png) [@Duha](https://discuss.kde.org/u/Duha)\
**Post date:** [November 25, 2023, 12:28pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/2 "2023-11-25T12:28:57Z")

</div>

`systemctl restart --user plasma-plasmashell.service` **works for me** from tty.

Another thing you can try is using `DISPLAY=:1 plasmashell --replace` see: [kde5 - How to restart KDE Plasma from tty? - Unix & Linux Stack Exchange](https://unix.stackexchange.com/questions/499370/how-to-restart-kde-plasma-from-tty)  
But that **doesn’t work for me**.

Once you can restart plasma you should post your journald log so we can see what freezes.

---

<div class="post-metadata">

**Author:** ![Balls](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/balls/32/5849_2.png) [@Balls](https://discuss.kde.org/u/Balls)\
**Post date:** [November 25, 2023, 1:52pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/3 "2023-11-25T13:52:13Z")

</div>

The method that works for you gives me the following error: `Failed to connect to bus: No medium found`

additionally, the `plasmashell --replace` method gives me the following error:

```auto
xcb: could not connect to display :1 
This application failed to start because no qt platform plugin could be initialized

```

^ Truncated version, the full one has some mumbo jumbo and i don’t know how to copy stuff from my tty

---

<div class="post-metadata">

**Author:** ![WilsonEPhillips](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/wilsonephillips/32/6628_2.png) [@WilsonEPhillips](https://discuss.kde.org/u/WilsonEPhillips)\
**Post date:** [November 25, 2023, 1:53pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/4 "2023-11-25T13:53:39Z")

</div>

What distro are you on. Possibly one without systemd?

Nevermind I just check your history and it’s Arch.

---

<div class="post-metadata">

**Author:** ![Balls](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/balls/32/5849_2.png) [@Balls](https://discuss.kde.org/u/Balls)\
**Post date:** [November 25, 2023, 1:56pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/5 "2023-11-25T13:56:54Z")

</div>

Thats my bad i should specify again.

---

<div class="post-metadata">

**Author:** ![WilsonEPhillips](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/wilsonephillips/32/6628_2.png) [@WilsonEPhillips](https://discuss.kde.org/u/WilsonEPhillips)\
**Post date:** [November 25, 2023, 2:03pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/6 "2023-11-25T14:03:38Z")

</div>

I just found this. [qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. | Qt Forum](https://forum.qt.io/topic/93247/qt-qpa-plugin-could-not-load-the-qt-platform-plugin-xcb-in-even-though-it-was-found)

It looks like “I had the same problem, install libxcb-xinerama0 and I solved it, Thanks!”

Will that help? It’s work a try. Yeah, you can’t copy and paste from a tty. Phone camera works though. 🙂

---

<div class="post-metadata">

**Author:** ![Balls](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/balls/32/5849_2.png) [@Balls](https://discuss.kde.org/u/Balls)\
**Post date:** [November 25, 2023, 2:15pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/7 "2023-11-25T14:15:57Z")

</div>

Problem is, pacman doesn’t have libxcb-xinerama0? ~~it does have libxcb-xinerama.so.0 but i dont want to do something stupid~~

---

<div class="post-metadata">

**Author:** ![WilsonEPhillips](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/wilsonephillips/32/6628_2.png) [@WilsonEPhillips](https://discuss.kde.org/u/WilsonEPhillips)\
**Post date:** [November 25, 2023, 2:23pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/8 "2023-11-25T14:23:40Z")

</div>

Not all distros use the name package names.

I did a search for the following and there were a lot of hits.

arch xcb: could not connect to display :1 This application failed to start because no qt platform plugin could be initialized

You could start with just a reinstall of xcb and see what that does.

---

<div class="post-metadata">

**Author:** ![Balls](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/balls/32/5849_2.png) [@Balls](https://discuss.kde.org/u/Balls)\
**Post date:** [November 25, 2023, 2:46pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/9 "2023-11-25T14:46:14Z")

</div>

I suspect that when i run plasmashell --replace something is trying to access qt’s platform plugin path but that something doesn’t exactly knows the path of the platform plugins (/usr/lib/qt/plugins/platforms) but, i don’t know how to specify the path to it

---

<div class="post-metadata">

**Author:** ![ngraham](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/ngraham/32/64_2.png) [@ngraham](https://discuss.kde.org/u/ngraham)\
**Post date:** [November 25, 2023, 2:46pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/10 "2023-11-25T14:46:58Z")

</div>

TBH This feels like a distro setup issue more than a KDE Plasma issue. Which feels especially possible due to using Arch, which is a DIY distro.

---

<div class="post-metadata">

**Author:** ![Balls](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/balls/32/5849_2.png) [@Balls](https://discuss.kde.org/u/Balls)\
**Post date:** [November 25, 2023, 2:48pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/11 "2023-11-25T14:48:14Z")

</div>

I’m not saying that KDE is to blame, but KDE is the most relevant platform to my problem so that’s why I decide to mention my problem here

---

<div class="post-metadata">

**Author:** ![Balls](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/balls/32/5849_2.png) [@Balls](https://discuss.kde.org/u/Balls)\
**Post date:** [November 25, 2023, 3:05pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/12 "2023-11-25T15:05:35Z")

</div>

I’ll do a fresh install, wish me luck

---

<div class="post-metadata">

**Author:** ![WilsonEPhillips](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/wilsonephillips/32/6628_2.png) [@WilsonEPhillips](https://discuss.kde.org/u/WilsonEPhillips)\
**Post date:** [November 25, 2023, 3:15pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/13 "2023-11-25T15:15:08Z")

</div>

Make sure you have a fresh backup of your stuff.

---

<div class="post-metadata">

**Author:** ![Balls](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/balls/32/5849_2.png) [@Balls](https://discuss.kde.org/u/Balls)\
**Post date:** [November 25, 2023, 4:18pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/14 "2023-11-25T16:18:38Z")

</div>

Good news. Freezing is gone. In this install i opted for open source drivers instead of proprietary ones and several other things. Happy to say I can finally use my pc properly

---

<div class="post-metadata">

**Author:** ![ngraham](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/ngraham/32/64_2.png) [@ngraham](https://discuss.kde.org/u/ngraham)\
**Post date:** [November 25, 2023, 5:57pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/15 "2023-11-25T17:57:09Z")

</div>

Sounds like the problem was in the NVIDIA driver all along. An unfortunately common occurrence, and one of the reasons why KDE developers often recommend against using NVIDIA GPUs if possible.

---

<div class="post-metadata">

**Author:** ![HeraldForever](https://discuss-cdn.kde.org/user_avatar/discuss.kde.org/heraldforever/32/13502_2.png) [@HeraldForever](https://discuss.kde.org/u/HeraldForever)\
**Post date:** [January 13, 2024, 4:29pm UTC](https://discuss.kde.org/t/kde-still-freezing/7662/16 "2024-01-13T16:29:42Z")

</div>

I am getting this error in the output of `dmesg`:

```auto
[6810.950843] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[6833.305224] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[6833.305232] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[6833.305239] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[6833.305245] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[7091.626753] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8374.864354] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8376.871016] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8387.076310] i915 0000:00:02.0: [drm] *ERROR* [CRTC:80:pipe A] flip_done timed out
[8397.316130] i915 0000:00:02.0: [drm] *ERROR* flip_done timed out
[8397.316149] i915 0000:00:02.0: [drm] *ERROR* [CRTC:80:pipe A] commit wait timed out
[8397.387563] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8671.286056] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8683.452650] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8683.452660] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8683.452664] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8683.452667] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8683.452670] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8683.452673] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8692.819281] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8699.602575] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8702.735882] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8702.735894] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8702.735898] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!
[8702.735901] i915 0000:00:02.0: [drm] *ERROR* The master control interrupt lied (DE PIPE)!

```

Does that mean something regarding the freeze ?

> **My system info (inxi -Faz)**
>
> ```auto
> System:
> Kernel: 6.7.0-060700rc8-generic arch: x86_64 bits: 64 compiler: N/A
> clocksource: tsc available: acpi_pm
> parameters: BOOT_IMAGE=/vmlinuz-6.7.0-060700rc8-generic
> root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
> Desktop: KDE Plasma v: 5.27.8 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
> dm: SDDM Distro: Ubuntu 23.10 (Mantic Minotaur)
> Machine:
> Type: Laptop System: ASUSTeK product: ROG Strix G614JU_G614JU v: 1.0
> serial: <superuser required>
> Mobo: ASUSTeK model: G614JU v: 1.0 serial: <superuser required>
> UEFI: American Megatrends LLC. v: G614JU.321 date: 10/24/2023
> Battery:
> ID-1: BAT0 charge: 84.6 Wh (100.0%) condition: 84.6/90.0 Wh (94.0%)
> volts: 17.4 min: 16.0 model: AS3GYFG3KC R220358 type: Unknown
> serial: <filter> status: full
> CPU:
> Info: model: 13th Gen Intel Core i9-13980HX bits: 64 type: MST AMCP
> arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
> process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
> microcode: 0x11D
> Topology: cpus: 1x cores: 24 mt: 8 tpc: 2 st: 16 threads: 32 smt: enabled
> cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32 KiB, 16x64 KiB
> L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
> Speed (MHz): avg: 804 high: 881 min/max: 800/5400:5600:4000 scaling:
> driver: intel_pstate governor: powersave cores: 1: 800 2: 800 3: 800 4: 806
> 5: 800 6: 800 7: 800 8: 800 9: 800 10: 867 11: 881 12: 800 13: 800 14: 800
> 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 21: 800 22: 800 23: 800
> 24: 800 25: 800 26: 800 27: 800 28: 800 29: 800 30: 800 31: 800 32: 800
> bogomips: 154828
> Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
> Vulnerabilities:
> Type: gather_data_sampling status: Not affected
> Type: itlb_multihit status: Not affected
> Type: l1tf status: Not affected
> Type: mds status: Not affected
> Type: meltdown status: Not affected
> Type: mmio_stale_data status: Not affected
> Type: retbleed status: Not affected
> Type: spec_rstack_overflow status: Not affected
> Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
> prctl
> Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
> sanitization
> Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB:
> conditional, RSB filling, PBRSB-eIBRS: SW sequence
> Type: srbds status: Not affected
> Type: tsx_async_abort status: Not affected
> Graphics:
> Device-1: Intel Raptor Lake-S UHD Graphics vendor: ASUSTeK driver: i915
> v: kernel arch: Gen-13 process: Intel 7 (10nm) built: 2022+ ports:
> active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 0000:00:02.0
> chip-ID: 8086:a788 class-ID: 0300
> Device-2: NVIDIA AD107M [GeForce RTX 4050 Max-Q / Mobile]
> vendor: ASUSTeK GN21-X2 driver: nvidia v: 535.146.02
> alternate: nvidiafb,nouveau,nvidia_drm non-free: 535.xx+
> status: current (as of 2023-08) arch: Lovelace code: AD1xx
> process: TSMC n4 (5nm) built: 2022-23+ ports: active: none
> empty: DP-3,HDMI-A-3,eDP-2 bus-ID: 0000:01:00.0 chip-ID: 10de:28e1
> class-ID: 0300
> Device-3: Sonix USB2.0 HD UVC WebCam driver: uvcvideo type: USB rev: 2.0
> speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:4 chip-ID: 322e:2122
> class-ID: 0e02
> Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 23.2.0
> compositor: kwin_x11 driver: X: loaded: modesetting,nvidia
> unloaded: fbdev,nouveau,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
> Screen-1: 0 s-res: 1680x1050 s-dpi: 98 s-size: 436x273mm (17.17x10.75")
> s-diag: 514mm (20.25")
> Monitor-1: eDP-1 model: TL160ADMP03-0 built: 2022 res: 1680x1050 hz: 60
> dpi: 124 gamma: 1.2 size: 345x215mm (13.58x8.46") diag: 407mm (16")
> ratio: 16:10 modes: 2560x1600
> API: OpenGL v: 4.6 Mesa 23.2.1-1ubuntu3.1 renderer: Mesa Intel Graphics
> (RPL-S) direct-render: Yes
> Audio:
> Device-1: Intel vendor: ASUSTeK driver: snd_hda_intel v: kernel
> alternate: snd_sof_pci_intel_tgl bus-ID: 0000:00:1f.3 chip-ID: 8086:7a50
> class-ID: 0403
> Device-2: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel
> bus-ID: 0000:01:00.1 chip-ID: 10de:22be class-ID: 0403
> API: ALSA v: k6.7.0-060700rc8-generic status: kernel-api
> tools: alsactl,alsamixer,amixer
> Server-1: PipeWire v: 0.3.79 status: active with: 1: pipewire-pulse
> status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
> tools: pactl,pw-cat,pw-cli,wpctl
> Network:
> Device-1: Intel driver: iwlwifi v: kernel port: N/A bus-ID: 0000:00:14.3
> chip-ID: 8086:7a70 class-ID: 0280
> IF: wlo1 state: up mac: <filter>
> Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
> vendor: ASUSTeK driver: r8169 v: kernel port: 4000 bus-ID: 0000:6c:00.0
> chip-ID: 10ec:8168 class-ID: 0200
> IF: enp108s0 state: down mac: <filter>
> Bluetooth:
> Device-1: Intel driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s
> lanes: 1 mode: 1.1 bus-ID: 1-14:5 chip-ID: 8087:0033 class-ID: e001
> Report: hciconfig ID: hci0 rfk-id: 0 state: down
> bt-service: enabled,running rfk-block: hardware: no software: yes
> address: <filter>
> Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff
> link-mode: peripheral accept
> RAID:
> Hardware-1: Intel Volume Management Device NVMe RAID Controller Intel
> driver: vmd v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:a77f rev:
> class-ID: 0104
> Drives:
> Local Storage: total: 953.87 GiB used: 273.16 GiB (28.6%)
> SMART Message: Unable to run smartctl. Root privileges required.
> ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Micron model: 2400 MTFDKBA1T0QFM
> size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
> lanes: 4 tech: SSD serial: <filter> fw-rev: V3MA003 temp: 41.9 C
> scheme: GPT
> Partition:
> ID-1: / raw-size: 929.41 GiB size: 913.75 GiB (98.31%)
> used: 272.53 GiB (29.8%) fs: ext4 dev: /dev/dm-1 maj-min: 252:1
> mapped: vgkubuntu-root
> ID-2: /boot raw-size: 1.67 GiB size: 1.61 GiB (96.26%)
> used: 598.2 MiB (36.4%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
> ID-3: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
> used: 43.2 MiB (8.5%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
> Swap:
> Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
> ID-1: swap-1 type: partition size: 1.91 GiB used: 0 KiB (0.0%)
> priority: -2 dev: /dev/dm-2 maj-min: 252:2 mapped: vgkubuntu-swap_1
> Sensors:
> System Temperatures: cpu: 36.0 C mobo: N/A
> Fan Speeds (rpm): cpu: 1900
> Info:
> Processes: 548 Uptime: 2h 37m wakeups: 5 Memory: total: 24 GiB note: est.
> available: 23.09 GiB used: 6.85 GiB (29.7%) Init: systemd v: 253
> target: graphical (5) default: graphical tool: systemctl Compilers:
> gcc: 13.2.0 alt: 12/13 clang: 16.0.6 Packages: 3412 pm: dpkg pkgs: 3386
> libs: 2158 tools: apt,apt-get,aptitude pm: flatpak pkgs: 20 pm: snap pkgs: 6
> Shell: Bash v: 5.2.15 running-in: konsole inxi: 3.3.29
> 
> ```
