Fast clicking on Meta+V causes the whole Plasma workspace to restart, nothing is reported by coredumpctl, journald logs the following information: 6/26/24 10:14 PM kwin_wayland kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 6/26/24 10:14 PM kwin_wayland kwin_core: Failed to focus 0x1800011 (error 8) 6/26/24 10:14 PM kwin_wayland kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11 6/26/24 10:14 PM kwin_wayland_wrapper error in client communication (pid 1916) 6/26/24 10:14 PM kwin_wayland qt.core.qobject.connect: QObject::disconnect: Unexpected nullptr parameter 6/26/24 10:14 PM plasmashell xdg_wm_base#3: error 3: no xdg_popup parent surface has been specified 6/26/24 10:14 PM plasmashell The Wayland connection broke. Did the Wayland compositor die? 6/26/24 10:14 PM systemd plasma-plasmashell.service: Main process exited, code=exited, status=255/EXCEPTION 6/26/24 10:14 PM systemd plasma-plasmashell.service: Failed with result 'exit-code'. 6/26/24 10:14 PM systemd plasma-plasmashell.service: Scheduled restart job, restart counter is at 2. 6/26/24 10:14 PM systemd Starting KDE Plasma Workspace... 6/26/24 10:14 PM systemd Started KDE Plasma Workspace.
I tried to replicate this but can't, whether manually pressing the shortcut or keeping it pressed. I tried it with several images in the clipboard, I tried it with 31 megabytes of Lorem Ipsum plain text. I tried it with an empty clipboard. The only thing I got was fast flickering from the popup opening and closing so often. Do you have an idea about specific circumstances that may have caused this? Does it happen reliably for you?
(In reply to cwo from comment #1) > Do you have an idea about specific circumstances that may have caused this? > Does it happen reliably for you? It happens at random frequency, sometimes first hit, sometimes 1 miss 1 hit, sometimes 2 or more miss then it occurs. The only customized thing I have is setting 700 items as history for Klipper. Is there any way apart from coredumpctl to retrieve the crash?
Can you share more information of your system? System Settings -> About this system -> click copy details and paste them here
(In reply to Akseli Lahtinen from comment #3) > Can you share more information of your system? This was not present on 6.1.0, it happened after upgrading to 6.1.1, the problem is more aggressive on two laptops: Operating System: Manjaro Linux KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.6-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i3-5005U CPU @ 2.00GHz Memory: 5.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 Operating System: Manjaro Linux KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.6-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 2 × Pentium® Dual-Core CPU T4400 @ 2.20GHz Memory: 5.6 GiB of RAM Graphics Processor: Mesa Mobile Intel® GM45 Express Chipset Manufacturer: Acer Product Name: T
I have this same problem on my desktop. I don't know how else to debug it, but journalctl show me there errors after workspace crashing due to klipper: kesä 27 19:33:59 cachyos-x8664 kwin_wayland_wrapper[870]: error in client communication (pid 1008) kesä 27 19:33:59 cachyos-x8664 plasmashell[1008]: xdg_wm_base#3: error 3: no xdg_popup parent surface has been specified kesä 27 19:34:00 cachyos-x8664 plasmashell[2885]: error getting max keyboard brightness via dbus QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path '/org/kde/Solid/PowerManagement/Actions/KeyboardBrightnessControl'") Operating System: CachyOS Linux KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.10.0-rc5-2-cachyos-rc-lto (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7600 6-Core Processor Memory: 30,8 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 4070 Ti SUPER/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B650M DS3H
Looks like the same issue as Bug 488515, but applied to this popup too. FWIW I also cannot reproduce the issue by spamming Meta+V, albeit with my puny 20 item history.
Or maybe the fix for that issue happened to fix this one too? I see that that issue is only fixed for Plasma 6.2.
I also have this issue after updating to Plasma 6.1.1. I can get it to fail 50% of the time after having copied an image into the clipboard and then trying to press Meta+V three times. journalctl: Jun 28 11:34:24 desktop plasmashell[8117]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt Jun 28 11:34:24 desktop plasmashell[8117]: org.kde.plasma.keyboardindicator: Unknown key Qt::Key_Alt Jun 28 11:34:35 desktop plasmashell[8117]: xdg_wm_base#3: error 3: no xdg_popup parent surface has been specified Jun 28 11:34:35 desktop plasmashell[8117]: The Wayland connection experienced a fatal error: Protocol error Jun 28 11:34:36 desktop systemd[1407]: plasma-plasmashell.service: Main process exited, code=exited, status=255/EXCEPTION Jun 28 11:34:36 desktop systemd[1407]: plasma-plasmashell.service: Failed with result 'exit-code'. Jun 28 11:34:36 desktop systemd[1407]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 5. Jun 28 11:34:36 desktop systemd[1407]: Starting KDE Plasma Workspace.. Operating System: EndeavourOS KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.6-arch1-1 (64-bit) Graphics Platform: Wayland
I cannot reproduce it. What window is active and where is the cursor when you press Meta+V?
(In reply to Vlad Zahorodnii from comment #9) > I cannot reproduce it. What window is active and where is the cursor when > you press Meta+V? It happens everywhere, with Firefox, Kate... even with desktop visible and no app opened.
I have the same issue. I first thought it was because of the large amount of history I had set, which was 512 entries. But even after reducing the amount I still have this crash. KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.6-zen1-1-zen (64-bit) Graphics Platform: Wayland
I also have this issue. I also get crashes when opening the debug console via "qdbus6 org.kde.KWin /KWin org.kde.KWin.showDebugConsole " with the same error "QDBusError("org.freedesktop.DBus.Error.UnknownObject", "No such object path". General instability and freezes after upgrading to 6.1.1
Created attachment 171157 [details] This is the core dump I get from the clipboard
I'm also seeing this on Arch. Steps to Replicate (For me): - Press Meta+V to open clipboard selection list modal. - Press Meta+V again while the paste modal is still visible Caveats (For me): - Plasmashell does not seem to crash if Meta+V is pressed and the clipboard popup modal is not focused. (This can be achieved by pressing Meta, keeping it held down until the Application Launcher to shows up, and then pressing V, so you can unfocus the popup/modal without dismissing it) Uninformed Musings / Speculation as to cause (I am not a *KDE* developer): I heard that keybinds only involving the Meta key were added recently, maybe it's related to that? Another thought is that it might have do with Wayland and the concept of focus somehow (?). Closing Thoughts: I've seen other people in this thread that can cause this crash through a single press of Meta+V, I think I've experienced the crash when Meta+V is pressed, but I can't intentionally replicate this.
I can reproduce this reliably by : - Pressing Meta+V - Clicking on the Search Bar on the modal - Pressing Meta+V Operating System: Garuda Linux KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-zen1-1-zen (64-bit) Graphics Platform: Wayland
I am able to reproduce consistently. 1. Press Meta+V 2. **Release Meta and V** 3. Press Meta+V If using a 3-key shortcut, releasing only 2 of them cause the issue. e.g. Maj+Alt+V ⇒ Release Maj+Alt ⇒ Press Maj+Alt I am also able to reproduce the single press crash 1. Meta (open the Application Launcher) 2. Meta (close it), or open an application by using the keyboard or the mouse 3. (... Do whatever you want: nothing, wait, write, Alt+Tab, Meta+C; except explicit focus to a panel by clicking on it, or going to the/another desktop ...) 4. Press Meta+V Summary: Meta+V try to open a dialog on closed/closing dialog As a workaround, switch to the desktop/another virtual desktop before using Meta+V. e.g. Meta+D+D, **Release all**, Meta+V (Meta, Meta, Meta+D+D+V will crash) --- Output of plasmashell when crashing xdg_wm_base#3: error 3: no xdg_popup parent surface has been specified The Wayland connection experienced a fatal error: Protocol error Operating System: EndeavourOS KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-zen1-1-zen (64-bit) Graphics Platform: Wayland
Same exact issue on Operating System: Arch Linux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 60.7 GiB of RAM Graphics Processor: AMD Radeon Graphics My workaround for now is to rebind Meta-V from Show Clipboard at Mouse Position to the Clippbord applet in the System Tray.
I can reproduce the bug on Arch. Operating System: Arch Linux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics
*** Bug 489462 has been marked as a duplicate of this bug. ***
Fixed in Qt 6.7.3. I've sent an email to the distributions mailing list asking to patch qtwayland 6.7.2 until 6.7.3 is released.
(In reply to Vlad Zahorodnii from comment #20) > Fixed in Qt 6.7.3. I've sent an email to the distributions mailing list > asking to patch qtwayland 6.7.2 until 6.7.3 is released. The crash is gone after upgrading to qt6-wayland 6.7.2-2 both on Arch and Manjaro unstable.
*** Bug 490152 has been marked as a duplicate of this bug. ***
*** Bug 492289 has been marked as a duplicate of this bug. ***