Multiple times a day when highlighting text to copy CopyQ will generate an error indicating the segfault in the linked report has occurred. Error: Process crashed 1. copyq --clipboard-access monitorClipboard Reproducible: Sometimes Steps to Reproduce: 1. Highlight some text, quite often highlighting text in Slack client app will produce this whereas highlighting raw text such as this text in a dialog will not. Actual Results: CopyQ segfaults Expected Results: No segfault.
Please try the new release 9.1.0 and if problem still occurs reopen. Thanks!
Reopening this because I'm still seeing it with copyq-9.1.0-1.fc40.x86_64 installed and these crashes are being reported here [0]. Interestingly whilst the interface reports CopyQ Clipboard Manager 9.1.0 and the command line shows the following; $ /usr/bin/copyq --version CopyQ Clipboard Manager 9.1.0 Qt: 5.15.15 KNotifications: 5.116.0 Compiler: GCC Arch: x86_64-little_endian-lp64 OS: Fedora Linux 40 (Forty) the crash reports are always showing copyq 0:8.0.0-1.fc40 ? There is only one copyq instance running so I'm confused as to why that would be the case but, regardless, I'm still seeing this issue. [0] https://retrace.fedoraproject.org/faf/reports/660138/
This seems like a Qt bug (maybe related to https://bugreports.qt.io/browse/QTBUG-66638). Perhaps we can move to *Qt 6* version of the app. I'm using a custom Qt 6 build, and it has been working well on Fedora (but I have not seen any issue with the Qt 5 builds either).
(In reply to Lukas Holecek from comment #3) > This seems like a Qt bug (maybe related to > https://bugreports.qt.io/browse/QTBUG-66638). > > Perhaps we can move to *Qt 6* version of the app. I'm using a custom Qt 6 > build, and it has been working well on Fedora (but I have not seen any issue > with the Qt 5 builds either). We can try that of course (need to do it eventually anyway) but I'm a bit concerned on what the crash reports are showing 0:8.0.0-1.fc40? That seems a bit odd to me. FWIW, I haven't been able to recreate. @Brad, just for grins can you do a: rpm -qa | grep copyq and a find copyq* -type f -executable -print I'm just curious.
Rebuild QT6 for F41 & F42
FEDORA-2024-dbd1a6904b (copyq-9.1.0-2.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-dbd1a6904b
FEDORA-2024-ef485b4ce6 (copyq-9.1.0-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ef485b4ce6
(In reply to Gerald Cox from comment #4) > We can try that of course (need to do it eventually anyway) but I'm a bit > concerned on what the crash reports are showing > 0:8.0.0-1.fc40? That seems a bit odd to me. > > FWIW, I haven't been able to recreate. > > @Brad, just for grins can you do a: > > rpm -qa | grep copyq > and a > find copyq* -type f -executable -print > > I'm just curious. Sure. $ rpm -qa | grep copyq copyq-9.1.0-1.fc40.x86_64 $ sudo find / -name copyq* -type f -executable -print /usr/bin/copyq $ /usr/bin/copyq --version CopyQ Clipboard Manager 9.1.0 Qt: 5.15.15 KNotifications: 5.116.0 Compiler: GCC Arch: x86_64-little_endian-lp64 OS: Fedora Linux 40 (Forty) $ abrt info --pretty full 09ffe86 Id 09ffe86 Component copyq Count 1 Time 2024-11-05 08:05:35 Command line /usr/bin/copyq --clipboard-access monitorClipboard Package copyq-9.1.0-1.fc40 User id 1000 (brad) Path /var/spool/abrt/ccpp-2024-11-05-08:05:35.833827-1192992 I have no idea where it is getting the 0:8.0.0-1.fc40 version from?
FEDORA-2024-ef485b4ce6 (copyq-9.1.0-2.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
(In reply to Brad Hubbard from comment #8) > (In reply to Gerald Cox from comment #4) > > We can try that of course (need to do it eventually anyway) but I'm a bit > > concerned on what the crash reports are showing > > 0:8.0.0-1.fc40? That seems a bit odd to me. > > > > FWIW, I haven't been able to recreate. > > > > @Brad, just for grins can you do a: > > > > rpm -qa | grep copyq > > and a > > find copyq* -type f -executable -print > > > > I'm just curious. > > Sure. > > $ rpm -qa | grep copyq > > copyq-9.1.0-1.fc40.x86_64 > > $ sudo find / -name copyq* -type f -executable -print > /usr/bin/copyq > > $ /usr/bin/copyq --version > CopyQ Clipboard Manager 9.1.0 > Qt: 5.15.15 > KNotifications: 5.116.0 > Compiler: GCC > Arch: x86_64-little_endian-lp64 > OS: Fedora Linux 40 (Forty) > > $ abrt info --pretty full 09ffe86 > Id 09ffe86 > Component copyq > Count 1 > Time 2024-11-05 08:05:35 > Command line /usr/bin/copyq --clipboard-access monitorClipboard > Package copyq-9.1.0-1.fc40 > > User id 1000 (brad) > > Path /var/spool/abrt/ccpp-2024-11-05-08:05:35.833827-1192992 > > I have no idea where it is getting the 0:8.0.0-1.fc40 version from? Thanks for the quick response. That is indeed puzzling. In any event, as Lukas suggested I've built with qt6 so hopefully that will fix the issue for you. It should be available in the testing repository tomorrow November 6th. You can also download it directly from here if you wish: https://koji.fedoraproject.org/koji/buildinfo?buildID=2579360
FEDORA-2024-dbd1a6904b has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-dbd1a6904b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-dbd1a6904b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-dbd1a6904b (copyq-9.1.0-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.