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

Open
1 of 6 tasks
dante-e-v opened this issue Apr 20, 2024 · 0 comments
Open
1 of 6 tasks

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

dante-e-v opened this issue Apr 20, 2024 · 0 comments
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant