Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Screen Flicker On KDE Plasma Wayland - Possibly A Wayland Bug #190

Closed
1 of 6 tasks
dante-e-v opened this issue Apr 20, 2024 · 6 comments · May be fixed by #203
Closed
1 of 6 tasks

Screen Flicker On KDE Plasma Wayland - Possibly A Wayland Bug #190

dante-e-v opened this issue Apr 20, 2024 · 6 comments · May be fixed by #203
Labels
bug Something isn't working

Comments

@dante-e-v
Copy link

dante-e-v commented Apr 20, 2024

Describe the bug
Using clipboard in KDE Plasma Wayland makes the screen start flickering. Every time it flickers input is stopped so no typing on a keyboard during it.

It also clears any right-click context menus and closes desktop edit mode.

For some reason it also makes it so I can't launch a new plasma session in a different tty. Specifically it gives an error of:

*ERROR* Failed to open channel.

To Reproduce
Steps to reproduce the behavior:

$ cb copy "test"

Expected behavior
I expected that things would run normally and not glitch out the entire session.

Version
I'm using CB 0.9.0.1-1 from the AUR with Arch Linux (Vanilla). I installed it with the AUR helper paru.

Questionnaire
Check these boxes to see if your issue is valid or not.

  • If I compiled CB, then any errors that may be present don't mention "LTO error" (this is sadly a bug with the compiler, not Clipboard)
  • If I compiled CB, then any errors that may be present don't mention "XYZ has not been defined in namespace std" (this sadly means you need a compiler with C++20 support, so upgrade first)
  • I check all these boxes without reading them
  • I think bachata is the best music
  • I'm using the latest commit/release (we only support the latest)
  • If I downloaded CB from GitHub Actions or with the install script, any errors that may be present don't mention "GLIBC XYZ not found" (your system is sadly too outdated for CB, so upgrade it)

Additional context
I made sure to check issues and haven't seen anything like this.

I'm not familiar with how to find any logs pertaining to clipboard so if there are any I can grab that might helpful to debug this please let me know.

Wayland logs might also be useful so please let me know which ones I should grab and post.

I'm doing all this in a virtual machine. I know Wayland has issues with virtual machines but I've not encountered a bug like this with anything else.

@dante-e-v dante-e-v added the bug Something isn't working label Apr 20, 2024
@jirutka
Copy link

jirutka commented Jun 1, 2024

I’m experiencing the same bug on Alpine Linux v3.19 with Sway 1.8. And it doesn’t happen just for cb copy, but even cb config. What’s going on here?

EDIT: It stops when I disable GUI (CLIPBOARD_NOGUI=1).

@Yanislavcore
Copy link

Yanislavcore commented Jun 6, 2024

I have the same problem on my Fedora 40 with KDE Plasma 6 and Wayland.

If I launch "cb", it stays launched and never dies causing screen and focus flicker.

➜  ~ killall cb
➜  ~ ps aux | rg "\s+cb"
➜  ~ cb
┏━━ All your clipboards with content ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ 0│ <...>                                                                                                                                                                                                                ┃
┗━━▌Text, Files, Directories,  Data ▐━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
➜  ~ ps aux | rg "\s+cb"
yanisla+  188861  0.0  0.0 243032  5404 ?        Ss   19:13   0:00 cb

@Mcrtin
Copy link

Mcrtin commented Sep 21, 2024

Same problem on hyprland; run cb and the currently focused window starts to flicker.
When in fullscreen it goes back to a normal window; the interval is initially, after the first run of cb ca. 3 sec. when calling it more times the interval shortens.

@iFreilicht
Copy link

Some problem in NixOS with KDE Plasma 6 and Wayland. As noted above, CLIPBOARD_NOGUI=1 fixes this, but that's not a good solution, I use cb primarily because of the GUI integration.

iFreilicht added a commit to iFreilicht/Clipboard that referenced this issue Sep 25, 2024
Fixes Slackadays#190

The GUIClipboardDaemon created a new Wayland window every ~2 seconds to
interact with the clipboard. This steals focus from the currently active
window for a very short time, causing context menus and overlays to
close. It basically made Clipboard unusable on Wayland.

The simplest strategy of fixing this is to align Linux with all other
platforms by only reading data from the clipboard on-demand instead of
doing it continuously.
@iFreilicht
Copy link

I actually managed to fix it! 🥳 It took a long time to understand how Clipboard interacts with Wayland, but in the end the fix was relatively simple. If you are suffering from the same issue, please take the time to test the fix. See #203 for details on how to do that.

@Slackadays
Copy link
Owner

Dupe of #171, we still need to fix Wayland though

@Slackadays Slackadays closed this as not planned Won't fix, can't repro, duplicate, stale Oct 19, 2024
Repository owner locked and limited conversation to collaborators Oct 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants