MY GDB FUCKING CRASHED FOR TRYING TO DEBUG MY PLASMASHELL WHAT THE FUCKKKKKK
November 8, 2026 at 3:10 AM
MY GDB FUCKING CRASHED FOR TRYING TO DEBUG MY PLASMASHELL WHAT THE FUCKKKKKK
My plasmashell crashed. GDB'd its core dump.
Downloaded debuginfod cuz without it, I saw none.
Backtraced it.
I saw no code; only local variables. Some variables are <optimized out>
How the fuck do I learn about the bug if the information was hidden away from me for "optimization"?? Smh
Downloaded debuginfod cuz without it, I saw none.
Backtraced it.
I saw no code; only local variables. Some variables are <optimized out>
How the fuck do I learn about the bug if the information was hidden away from me for "optimization"?? Smh
November 6, 2026 at 1:50 AM
My plasmashell crashed. GDB'd its core dump.
Downloaded debuginfod cuz without it, I saw none.
Backtraced it.
I saw no code; only local variables. Some variables are <optimized out>
How the fuck do I learn about the bug if the information was hidden away from me for "optimization"?? Smh
Downloaded debuginfod cuz without it, I saw none.
Backtraced it.
I saw no code; only local variables. Some variables are <optimized out>
How the fuck do I learn about the bug if the information was hidden away from me for "optimization"?? Smh
途中でひっかかりそうなやつ
thread 2066:
#2 0x00007f2b93aabc70 pthread_cond_wait (libc.so.6 + 0xabc70)
#3 0x00007f2b945bbc90 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x3bbc90)
#4 0x00007f2b96cc28b1 n/a (libQt6Quick.so.6 + 0x4c28b1)
#24 0x000055861f29c785 n/a (plasmashell + 0x27785)
thread 2066:
#2 0x00007f2b93aabc70 pthread_cond_wait (libc.so.6 + 0xabc70)
#3 0x00007f2b945bbc90 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x3bbc90)
#4 0x00007f2b96cc28b1 n/a (libQt6Quick.so.6 + 0x4c28b1)
#24 0x000055861f29c785 n/a (plasmashell + 0x27785)
November 1, 2026 at 4:40 PM
途中でひっかかりそうなやつ
thread 2066:
#2 0x00007f2b93aabc70 pthread_cond_wait (libc.so.6 + 0xabc70)
#3 0x00007f2b945bbc90 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x3bbc90)
#4 0x00007f2b96cc28b1 n/a (libQt6Quick.so.6 + 0x4c28b1)
#24 0x000055861f29c785 n/a (plasmashell + 0x27785)
thread 2066:
#2 0x00007f2b93aabc70 pthread_cond_wait (libc.so.6 + 0xabc70)
#3 0x00007f2b945bbc90 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt6Core.so.6 + 0x3bbc90)
#4 0x00007f2b96cc28b1 n/a (libQt6Quick.so.6 + 0x4c28b1)
#24 0x000055861f29c785 n/a (plasmashell + 0x27785)
NVRM: _issueRpcAndWait: rpcSendMessage failed with status 0x0000000f for fn 76 sequence 166610!
(カウントアップが続く)
ERROR: GPU:0: Failed to query display engine channel state: 0x0000c67e:0:0:0x0000000f
systemd-coredump[]:(plasmashell)
#0 0x00007f2b73a80897 n/a (libnvidia-eglcore.so.615.78.08 + 0x680897)
(カウントアップが続く)
ERROR: GPU:0: Failed to query display engine channel state: 0x0000c67e:0:0:0x0000000f
systemd-coredump[]:(plasmashell)
#0 0x00007f2b73a80897 n/a (libnvidia-eglcore.so.615.78.08 + 0x680897)
November 1, 2026 at 4:34 PM
NVRM: _issueRpcAndWait: rpcSendMessage failed with status 0x0000000f for fn 76 sequence 166610!
(カウントアップが続く)
ERROR: GPU:0: Failed to query display engine channel state: 0x0000c67e:0:0:0x0000000f
systemd-coredump[]:(plasmashell)
#0 0x00007f2b73a80897 n/a (libnvidia-eglcore.so.615.78.08 + 0x680897)
(カウントアップが続く)
ERROR: GPU:0: Failed to query display engine channel state: 0x0000c67e:0:0:0x0000000f
systemd-coredump[]:(plasmashell)
#0 0x00007f2b73a80897 n/a (libnvidia-eglcore.so.615.78.08 + 0x680897)
Been on CachyOS for several months and, I must say that it's been mostly smooth sailing.
But if you're gonna use Linux - especially a bleeding edge distro like Cachy - you should know how to switch to another tty (Ctrl+Alt+F3 for tty3) and use btop to kill plasmashell (it'll bounce back) if frozen
But if you're gonna use Linux - especially a bleeding edge distro like Cachy - you should know how to switch to another tty (Ctrl+Alt+F3 for tty3) and use btop to kill plasmashell (it'll bounce back) if frozen
History has proven that Windows will never get better. Once you accept that, the practical and ethical need for alternatives becomes crystal clear. It is not an easy ask, but a just future cannot involve Windows. aftermath.site/we-must-kill-w...
October 30, 2026 at 6:07 PM
Been on CachyOS for several months and, I must say that it's been mostly smooth sailing.
But if you're gonna use Linux - especially a bleeding edge distro like Cachy - you should know how to switch to another tty (Ctrl+Alt+F3 for tty3) and use btop to kill plasmashell (it'll bounce back) if frozen
But if you're gonna use Linux - especially a bleeding edge distro like Cachy - you should know how to switch to another tty (Ctrl+Alt+F3 for tty3) and use btop to kill plasmashell (it'll bounce back) if frozen
I don't really know how `restart`ing/`force-reload`ing `sddm.service` and `plasma-plasmashell.service` interacts with `plasmashell --replace`, uhhhhhhh-
October 24, 2026 at 7:57 PM
I don't really know how `restart`ing/`force-reload`ing `sddm.service` and `plasma-plasmashell.service` interacts with `plasmashell --replace`, uhhhhhhh-
so I had to `dbus-run-session plasmashell` then send that to a background job and then disown the process to let init adopt it so I don't have a terminal hanging open.
I'm so tired,
I'm so tired,
October 23, 2026 at 9:55 PM
so I had to `dbus-run-session plasmashell` then send that to a background job and then disown the process to let init adopt it so I don't have a terminal hanging open.
I'm so tired,
I'm so tired,
speaking of,
Plasma got confused about which windows were on which desktop, so I went to restart it with `kquitapp/kstart`, which should be fine, but due to some dbus stupidity plasmashell is unable to re-start because it can't make the dbus endpoint....
Plasma got confused about which windows were on which desktop, so I went to restart it with `kquitapp/kstart`, which should be fine, but due to some dbus stupidity plasmashell is unable to re-start because it can't make the dbus endpoint....
October 23, 2026 at 9:55 PM
speaking of,
Plasma got confused about which windows were on which desktop, so I went to restart it with `kquitapp/kstart`, which should be fine, but due to some dbus stupidity plasmashell is unable to re-start because it can't make the dbus endpoint....
Plasma got confused about which windows were on which desktop, so I went to restart it with `kquitapp/kstart`, which should be fine, but due to some dbus stupidity plasmashell is unable to re-start because it can't make the dbus endpoint....
I don't think I explained what I said above correctly. What I meant about "...to the point of a force restart of my machine..." was that plasmashell would keep crashing, and the only way I knew how to fix it was to force restart the machine.
October 19, 2026 at 4:39 PM
I don't think I explained what I said above correctly. What I meant about "...to the point of a force restart of my machine..." was that plasmashell would keep crashing, and the only way I knew how to fix it was to force restart the machine.
The new @kde.org Plasma update 6.8 broke some of my items on my task-manager (taskbar), to the point where either they don't work, or if i try to pin them back to the task-manager, it'll crash plasmashell to the point of a force restart of my machine :/
Here's hoping it'll be fixed soon.
Here's hoping it'll be fixed soon.
October 19, 2026 at 4:35 PM
The new @kde.org Plasma update 6.8 broke some of my items on my task-manager (taskbar), to the point where either they don't work, or if i try to pin them back to the task-manager, it'll crash plasmashell to the point of a force restart of my machine :/
Here's hoping it'll be fixed soon.
Here's hoping it'll be fixed soon.
Ok, I managed to cause the taskbar to fuck up in Kubuntu. And turns out there's a relatively easy command to 'reset' it. First ALT + Spacebar to open the 'runner' at the top of the screen. Then enter the following:
systemctl restart --user plasma-plasmashell
systemctl restart --user plasma-plasmashell
October 9, 2026 at 6:41 AM
Ok, I managed to cause the taskbar to fuck up in Kubuntu. And turns out there's a relatively easy command to 'reset' it. First ALT + Spacebar to open the 'runner' at the top of the screen. Then enter the following:
systemctl restart --user plasma-plasmashell
systemctl restart --user plasma-plasmashell
sometimes I press Alt+F2 and run `plasmashell --replace` just to feel something
October 6, 2026 at 5:06 PM
sometimes I press Alt+F2 and run `plasmashell --replace` just to feel something
ダンプは再起動後のログに表示されるけど、Wine、Steam、Xwayland、plasmashell、…と出ていて整理しないと読みにくいかも
画像はとりあえず、plasmashellの（長すぎて画像でも貼りきれないけど、この後も似たようなパターンが続く感じ…）
pacman -Q nvidia-580xx-dkms
nvidia-580xx-dkms 580.178.04-1
画像はとりあえず、plasmashellの（長すぎて画像でも貼りきれないけど、この後も似たようなパターンが続く感じ…）
pacman -Q nvidia-580xx-dkms
nvidia-580xx-dkms 580.178.04-1
October 6, 2026 at 11:25 PM
ダンプは再起動後のログに表示されるけど、Wine、Steam、Xwayland、plasmashell、…と出ていて整理しないと読みにくいかも
画像はとりあえず、plasmashellの（長すぎて画像でも貼りきれないけど、この後も似たようなパターンが続く感じ…）
pacman -Q nvidia-580xx-dkms
nvidia-580xx-dkms 580.178.04-1
画像はとりあえず、plasmashellの（長すぎて画像でも貼りきれないけど、この後も似たようなパターンが続く感じ…）
pacman -Q nvidia-580xx-dkms
nvidia-580xx-dkms 580.178.04-1
kwin_wayland_wrapper[2009]: (EE) Caught signal 6 (Aborted).
kwin_wayland_wrapper[19895]: eglInitialize() failed
XWAYLAND: Disabling GLAMOR support
EGL setup failed, disabling glamor
Failed to initialize glamor, falling back to sw
systemd-coredump[19857]: Process 2085 (plasmashell) … signal 11/SEGV
kwin_wayland_wrapper[19895]: eglInitialize() failed
XWAYLAND: Disabling GLAMOR support
EGL setup failed, disabling glamor
Failed to initialize glamor, falling back to sw
systemd-coredump[19857]: Process 2085 (plasmashell) … signal 11/SEGV
October 6, 2026 at 11:53 PM
kwin_wayland_wrapper[2009]: (EE) Caught signal 6 (Aborted).
kwin_wayland_wrapper[19895]: eglInitialize() failed
XWAYLAND: Disabling GLAMOR support
EGL setup failed, disabling glamor
Failed to initialize glamor, falling back to sw
systemd-coredump[19857]: Process 2085 (plasmashell) … signal 11/SEGV
kwin_wayland_wrapper[19895]: eglInitialize() failed
XWAYLAND: Disabling GLAMOR support
EGL setup failed, disabling glamor
Failed to initialize glamor, falling back to sw
systemd-coredump[19857]: Process 2085 (plasmashell) … signal 11/SEGV
（発生時点でログが取れたので）
CachyOS
KDE Plasma 環境でHDMIにノイズが乗る現象（発生は稀）
・KDE設定>音声 のテストで片方（左）だけノイズが乗る
・同テストで左右ともに音は出る
・PipeWireがデバイスを見失っている
・今回発生したのはOSの起動直後
（journalctl -f で監視中に発生）
plasmashell[2069]: PipeWire remote error: -2 unknown resource 3 op:7
plasmashell[2069]: PipeWire remote error: -2 target not found
CachyOS
KDE Plasma 環境でHDMIにノイズが乗る現象（発生は稀）
・KDE設定>音声 のテストで片方（左）だけノイズが乗る
・同テストで左右ともに音は出る
・PipeWireがデバイスを見失っている
・今回発生したのはOSの起動直後
（journalctl -f で監視中に発生）
plasmashell[2069]: PipeWire remote error: -2 unknown resource 3 op:7
plasmashell[2069]: PipeWire remote error: -2 target not found
October 6, 2026 at 5:38 AM
（発生時点でログが取れたので）
CachyOS
KDE Plasma 環境でHDMIにノイズが乗る現象（発生は稀）
・KDE設定>音声 のテストで片方（左）だけノイズが乗る
・同テストで左右ともに音は出る
・PipeWireがデバイスを見失っている
・今回発生したのはOSの起動直後
（journalctl -f で監視中に発生）
plasmashell[2069]: PipeWire remote error: -2 unknown resource 3 op:7
plasmashell[2069]: PipeWire remote error: -2 target not found
CachyOS
KDE Plasma 環境でHDMIにノイズが乗る現象（発生は稀）
・KDE設定>音声 のテストで片方（左）だけノイズが乗る
・同テストで左右ともに音は出る
・PipeWireがデバイスを見失っている
・今回発生したのはOSの起動直後
（journalctl -f で監視中に発生）
plasmashell[2069]: PipeWire remote error: -2 unknown resource 3 op:7
plasmashell[2069]: PipeWire remote error: -2 target not found
plasmashell 自体の不具合じゃなくて Qt のバグっぽい ?
September 28, 2026 at 5:35 AM
plasmashell 自体の不具合じゃなくて Qt のバグっぽい ?
plasmashell が segfault で死にまくる不具合に遭遇したけどなんか既知のバグらしい。なんだこれ
September 28, 2026 at 5:33 AM
plasmashell が segfault で死にまくる不具合に遭遇したけどなんか既知のバグらしい。なんだこれ
nullptr になった後に再初期化を忘れてそう？？？
>plasmashell[18604]: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1" returning nullptr
>kded6[18587]: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1" returning nullptr
>plasmashell[18604]: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1" returning nullptr
>kded6[18587]: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1" returning nullptr
September 26, 2026 at 9:25 AM
nullptr になった後に再初期化を忘れてそう？？？
>plasmashell[18604]: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1" returning nullptr
>kded6[18587]: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1" returning nullptr
>plasmashell[18604]: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1" returning nullptr
>kded6[18587]: No object for name "alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1" returning nullptr
Alt+F2
plasmashell --replace &
Fals das nicht hilft
pkill -9 plasmashell && kstart plasmashell
plasmashell --replace &
Fals das nicht hilft
pkill -9 plasmashell && kstart plasmashell
September 25, 2026 at 9:20 AM
Alt+F2
plasmashell --replace &
Fals das nicht hilft
pkill -9 plasmashell && kstart plasmashell
plasmashell --replace &
Fals das nicht hilft
pkill -9 plasmashell && kstart plasmashell
Mal angenommen, um den kde plasmashell desktop reparieren zu lassen, hat man die .config umbenannt, damit sie neu geschrieben wird, dann zurück benannt, wo könnten jetzt alle Daten und Konfigurationen sein?
September 25, 2026 at 6:36 AM
Mal angenommen, um den kde plasmashell desktop reparieren zu lassen, hat man die .config umbenannt, damit sie neu geschrieben wird, dann zurück benannt, wo könnten jetzt alle Daten und Konfigurationen sein?
[KDE] I was kind of bored of plasmashell so I built my own
Link: https://redd.it/1wkzjnn
#unixporn #linux #screenshot
Link: https://redd.it/1wkzjnn
#unixporn #linux #screenshot
September 19, 2026 at 10:36 PM
[KDE] I was kind of bored of plasmashell so I built my own
Link: https://redd.it/1wkzjnn
#unixporn #linux #screenshot
Link: https://redd.it/1wkzjnn
#unixporn #linux #screenshot
DEFAULT_SOURCE の今の値を確認しようと思ったけど、pulseaudio が入ってない（pipewire-pulse とコンフリクトするからpulseの方のインストール時に抜かれる）と、pacmd が使えないんだ……
> plasmashell[2046]: No object for name "@DEFAULT_SOURCE@" returning nullptr
とかが出てくるのもおかしい感じがするけど……
> plasmashell[2046]: No object for name "@DEFAULT_SOURCE@" returning nullptr
とかが出てくるのもおかしい感じがするけど……
September 19, 2026 at 11:44 PM
DEFAULT_SOURCE の今の値を確認しようと思ったけど、pulseaudio が入ってない（pipewire-pulse とコンフリクトするからpulseの方のインストール時に抜かれる）と、pacmd が使えないんだ……
> plasmashell[2046]: No object for name "@DEFAULT_SOURCE@" returning nullptr
とかが出てくるのもおかしい感じがするけど……
> plasmashell[2046]: No object for name "@DEFAULT_SOURCE@" returning nullptr
とかが出てくるのもおかしい感じがするけど……
ok so plasmashell likes to freeze and pin a single core at 99.9% for 30 seconds-10 minuts at a time if you have pictures in the clipboard history okay cool
September 1, 2026 at 1:51 AM
ok so plasmashell likes to freeze and pin a single core at 99.9% for 30 seconds-10 minuts at a time if you have pictures in the clipboard history okay cool