But what should i do if dwm is too BLOATED for me and TTY is way too buggy…?
1 Like
I’m running KDE Plasma on 6.2 kernel. No lts for me. Everything works! Ethernet, WiFi, Graphics, Sound, Keyboard, Mouse. What more could I ask for?
Even if that is true, it’s not something to brag about. It’s quite embarrassing, actually.
1 Like
IRL, I doubt that worse applies 
I couldn’t measure it, that’s for sure! Even with too many conkys running (most of them smooth scrolling) I can’t detect any difference from ‘instantaneous’ in day-to day use (btw, the scrollers etc have an around a 3% performance hit, with spikes to 5% - basically undetectable). If performance was a concern, I could probably learn OpenBox or i3… but NOT easily anymore!
Why should i be embarrassed. At least i can confirm how bad it actually is in comparison.
I don’t know. I feel things like that are best kept secret… You know, rumours start quickly, and suddenly, you’re that guy who uses windoze. The user nobody wants to associate with you, everyone around you is suddenly busy when you want to talk to them, your neighbours look away when they see you… You hear people whispering when you pass them. It’s all so very subtle, but you feel nothing is right. They know!
3 Likes
And worst of all - we know that you know what you know!
I know it’s bad! I’m starting to think I’m the 
2 Likes
1 Like
Yes, basically what I suspected, because I don’t think any normal user suffers from desktop blackouts every time they use their PC. What I don’t know is what to do to stop inmediately.
And as I side note, I am very stupid. It’s ok, the first step to quit it is admitting it.
2 Likes
Don’t be hard on yourself. No one is stupid. Btw we are just having a little fun so don’t take it the wrong way. We are here to help. I’m not really sure what you may have done or why you are having these issues. As i said above I never seem to have these kinds of things and I’ve been using KDE Plasma for a while. What is your hardware. Are you able to post it? Post the url from this command.
inxi -Faz | eos-sendlog
Edit: Maybe also what have you installed on KDE? What changes have you made?
2 Likes
$ inxi -Faz | eos-sendlog
bash: eos-sendlog: command not found
However skipping the last half:
$ inxi -Faz
System:
Kernel: 6.1.12-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-linux
root=UUID=f24f4bb4-f833-4baa-8a23-093123c5af7d rw nowatchdog
nvme_load=YES loglevel=3
Desktop: KDE Plasma v: 5.27.1 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 1 dm: SDDM
Distro: EndeavourOS base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: PRIME B550-PLUS v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 2803
date: 04/27/2022
CPU:
Info: model: AMD Ryzen 5 3500 bits: 64 type: MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB
desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 16 MiB
desc: 2x8 MiB
Speed (MHz): avg: 2644 high: 3848 min/max: 2200/4120 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 3848 2: 2076
3: 2200 4: 2054 5: 1983 6: 3706 bogomips: 43131
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
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 mitigation: untrained return thunk; SMT disabled
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: Retpolines, IBPB: conditional, STIBP:
disabled, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
vendor: XFX Speedster MERC 319 driver: amdgpu v: kernel arch: RDNA-2
code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1,DP-2,DP-3
bus-ID: 09:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: x11 server: X.Org v: 21.1.7 compositor: kwin_x11 driver: X:
loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa
dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: HDMI-A-1 mapped: HDMI-A-0 model: HP 24x serial: <filter>
built: 2019 res: 1920x1080 dpi: 93 gamma: 1.2 size: 527x297mm (20.75x11.69")
diag: 605mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 6800 XT (navi21
LLVM 15.0.7 DRM 3.49 6.1.12-arch1-1) direct-render: Yes
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 09:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0b:00.4 chip-ID: 1022:1487 class-ID: 0403
Sound API: ALSA v: k6.1.12-arch1-1 running: yes
Sound Server-1: JACK v: 1.9.22 running: no
Sound Server-2: PulseAudio v: 16.1 running: yes
Sound Server-3: PipeWire v: 0.3.66 running: no
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 06:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp6s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 1.14 TiB used: 328.48 GiB (28.1%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix
model: BC501 HFM256GDJTNG-8310A size: 238.47 GiB block-size: physical: 512 B
logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD serial: <filter>
rev: 80003C00 temp: 56.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Toshiba model: DT01ACA100
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
type: HDD rpm: 7200 serial: <filter> rev: A8L0 scheme: MBR
Partition:
ID-1: / raw-size: 237.49 GiB size: 232.7 GiB (97.98%) used: 37 GiB (15.9%)
fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 1000 MiB size: 998 MiB (99.80%)
used: 312 KiB (0.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 58.4 C mobo: N/A gpu: amdgpu temp: 52.0 C
mem: 52.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 710
Info:
Processes: 232 Uptime: 49m wakeups: 0 Memory: 23.35 GiB
used: 4.22 GiB (18.1%) Init: systemd v: 253 default: graphical
tool: systemctl Compilers: gcc: 12.2.1 clang: 15.0.7 Packages: pm: pacman
pkgs: 1076 libs: 359 tools: yay Shell: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.25
There may be CPU bottlenecks but I’ll replace the CPU in a month or so. I just couldn’t hoard all at once.
I would update the UEFI firmware before or after you replace the CPU to the latest version. I see that you are running pulse audio? Pipewire is the default. Did you switch to pulse?
Sound API: ALSA v: k6.1.12-arch1-1 running: yes
Sound Server-1: JACK v: 1.9.22 running: no
Sound Server-2: PulseAudio v: 16.1 running: yes
Sound Server-3: PipeWire v: 0.3.66 running: no
Possibly other changes you have made are what is causing your issue.
I think. I had a audio issue on Wine and a topic said you can use Cadence to route all audio through JACK.
After installing jack2 cadence pulseaudio-jack zita-ajbridge as it says, it added deps that replaced pipewire packages and can’t get back because somehow jack deps managed to be a dep of plasma-workspace when it used to be something from pipewire.
It didn’t work so I uninstalled most of it.
Wine can cause issues sometimes. Are you currently having problems still?
@Eoef
There’s a new update to KDE now. 5.27-2
This is an interesting question.
Is plasma filled with so many bugs it is unusable? Not in my experience. I use plasma all day every day on more than one machine. I have never seen either of the issues you are seeing.
Are there issues? Yes. Every DE has issues.
Can the issues be caused by misuse? Yes. However, that isn’t always the case.
Why do some people have more problems than others? A hard question to answer.
- We all use the system differently
- We all have different hardware
- We have different settings
- We different software installed
Have I ever seen bugs in plasma? Yes. However, I don’t see them on anything like the frequency that some others do. I think that is true in general though. I rarely encounter the issues that others do. I don’t have updates that break my system despite the fact that I run more systems than most people do. In theory, I should have more problems, not less. I have never been able to understand why. It could be argued that I am a more experienced user but I am not sure that really explains it.
4 Likes
A classic KDE bug is the way it handles multi-monitor systems. Everyone (at KDE) knows about it and admit it is a KDE problem.
Thanks to this unbearable showstopper, I was forced to use BSPWM, and discover a new world 
.
With 5.27 this has been improved a lot, but not in Wayland though (at least from my experience).
I am sure it will be completely corrected in the near future, as they have given great focus on it lately.
You can see that, if you don’t have multi-monitor setups, you will never face this horrible bug.
Hey, months later I’ve discovered what triggers this. Turns out powering my screen off causes this blackout! It always happens, I could reproduce it consistently and never happens under other circumstances. It’s not fixed though, only solution is logging out/restarting.
The first bug when apps don’t open seems solved after I stopped using an animated wallpaper. Funky.
I only have one monitor.