Open 33Fraise33 opened 2 years ago
Thanks for providing the stack trace.
I'm assuming this is crashing on accessing no longer valid clipboard data provided by Qt, but I'm not sure how is that possible since the access is wrapped in a safe pointer and checked before use.
Maybe some problem with linked Qt libraries. Where is the copyq binary/package coming from?
Does the app run natively on Wayland or as an X11 app (XWayland)? To run the app natively you may need to set environment variable QT_QPA_PLATFORM=xcb
before starting it (see also known issues).
I am using the installer from the aur with the latest git fixes: https://aur.archlinux.org/packages/copyq-git/
I will try to run it natively to see if that helps for my case
Ah, sorry, I meant start the app with QT_QPA_PLATFORM=wayland
- setting xcb
will run in the X11 compatibility mode. Or try both modes :) - not sure which one is default in the system.
Is there a way to see from the application in what mode it is running ?
Is there a way to see from the application in what mode it is running ?
If you also start the app with COPYQ_LOG_LEVEL=DEBUG
env variable set, one of the first lines logged (and printed on stderr when started from terminal) would be DEBUG: [default] QtInfo: Using Wayland clipboard access
.
❯ env COPYQ_LOG_LEVEL=DEBUG QT_QPA_PLATFORM=wayland copyq
DEBUG: Server "/home/lholecek/.config/copyq/.copyq_s" started.
DEBUG: [default] QtInfo: Using Wayland clipboard access
...
Describe the bug CopyQ gives an error in my system notification when selecting text.
To Reproduce Steps to reproduce the behavior:
Expected behavior CopyQ works as expected
Screenshots TBA
Version, OS and Environment
Error log in journalctl: