Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I did as https://bugzilla.redhat.com/show_bug.cgi?id=2467251#c0 describes. Version-Release number of selected component: copyq-15.0.0-1.fc44 Additional info: reporter: libreport-2.17.15 type: CCpp reason: copyq killed by SIGSEGV journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=18657d6;b=3d0db8fa19f8483d8262762f73da107a;m=2bfe4618e;t=65125ec73f9c1;x=fe2df73718566d69 executable: /usr/bin/copyq cmdline: /usr/bin/copyq --clipboard-access monitorClipboard cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-copyq rootdir: / uid: 1000 kernel: 6.19.14-300.fc44.x86_64 package: copyq-15.0.0-1.fc44 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: wl_proxy_get_version comment: I did as https://bugzilla.redhat.com/rest/bug?product=Fedora&component=0ad&creator=8ru2u4gz&creation_time_end=2026-05-06T00:00:00Z#:~:text=%22id%22%20:%20468585%2C explain. Blame https://github.com/abrt/gnome-abrt/issues/398#issue-4392045360 for this lacklustre description. Truncated backtrace: Thread no. 1 (17 frames) #0 wl_proxy_get_version at ../src/wayland-client.c:2445 #1 zwlr_data_control_offer_v1_receive at /usr/src/debug/kf6-kguiaddons-6.25.0-1.fc44.x86_64/redhat-linux-build/src/wayland-wlr-data-control-unstable-v1-client-protocol.h:645 #2 QtWayland::ext_data_control_offer_v1::receive at /usr/src/debug/kf6-kguiaddons-6.25.0-1.fc44.x86_64/redhat-linux-build/src/qwayland-ext-data-control-v1.cpp:394 #3 DataControlOffer::retrieveData at /usr/src/debug/kf6-kguiaddons-6.25.0-1.fc44.x86_64/src/systemclipboard/waylandclipboard.cpp:224 #4 QMimeDataPrivate::retrieveTypedData at /usr/src/debug/qt6-qtbase-6.10.3-1.fc44.x86_64/src/corelib/kernel/qmimedata.cpp:106 #5 QMimeData::data at /usr/src/debug/qt6-qtbase-6.10.3-1.fc44.x86_64/src/corelib/kernel/qmimedata.cpp:554 #6 ClipboardDataGuard::data at /usr/src/debug/copyq-15.0.0-1.fc44.x86_64/src/common/clipboarddataguard.cpp:90 #7 ClipboardDataGuard::getUtf8Data at /usr/src/debug/copyq-15.0.0-1.fc44.x86_64/src/common/clipboarddataguard.cpp:148 #8 cloneData at /usr/src/debug/copyq-15.0.0-1.fc44.x86_64/src/common/common.cpp:180 #9 X11PlatformClipboard::updateClipboardData at /usr/src/debug/copyq-15.0.0-1.fc44.x86_64/src/platform/x11/x11platformclipboard.cpp:787 #10 X11PlatformClipboard::onChanged at /usr/src/debug/copyq-15.0.0-1.fc44.x86_64/src/platform/x11/x11platformclipboard.cpp:703 #11 QtPrivate::QSlotObjectBase::call at /usr/src/debug/qt6-qtbase-6.10.3-1.fc44.x86_64/src/corelib/kernel/qobjectdefs_impl.h:461 #12 doActivate<false> at /usr/src/debug/qt6-qtbase-6.10.3-1.fc44.x86_64/src/corelib/kernel/qobject.cpp:4273 #13 QMetaObject::activate at /usr/src/debug/qt6-qtbase-6.10.3-1.fc44.x86_64/src/corelib/kernel/qobject.cpp:4333 #14 QMetaObject::activate<void, QClipboard::Mode> at /usr/include/qt6/QtCore/qobjectdefs.h:319 #15 KSystemClipboard::changed at /usr/src/debug/kf6-kguiaddons-6.25.0-1.fc44.x86_64/redhat-linux-build/src/KF6GuiAddons_autogen/include/moc_ksystemclipboard.cpp:120 #16 QObject::event at /usr/src/debug/qt6-qtbase-6.10.3-1.fc44.x86_64/src/corelib/kernel/qobject.cpp:1413 Potential duplicate: bug 2432616
Created attachment 2139725 [details] File: proc_pid_status
Created attachment 2139726 [details] File: maps
Created attachment 2139727 [details] File: limits
Created attachment 2139728 [details] File: environ
Created attachment 2139729 [details] File: open_fds
Created attachment 2139730 [details] File: mountinfo
Created attachment 2139731 [details] File: os_info
Created attachment 2139732 [details] File: cpuinfo
Created attachment 2139733 [details] File: core_backtrace
Created attachment 2139734 [details] File: exploitable
Created attachment 2139735 [details] File: dso_list
Created attachment 2139736 [details] File: var_log_messages
Created attachment 2139737 [details] File: backtrace
I attempted to reproduce https://bugzilla.redhat.com/show_bug.cgi?id=2441762#c0. reporter: libreport-2.17.15 type: CCpp reason: copyq killed by SIGSEGV journald_cursor: s=c1f108f1ef4e48808a377c0a73f168fc;i=18da56e;b=4ce3355d5f634367aa77fc6d4520a0b0;m=8abee4228;t=651425569839a;x=83ea1d70ee63961e executable: /usr/bin/copyq cmdline: /usr/bin/copyq --clipboard-access monitorClipboard cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-copyq rootdir: / uid: 1000 kernel: 6.19.14-300.fc44.x86_64 package: copyq-15.0.0-1.fc44 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: wl_proxy_get_version comment: I attempted to reproduce https://bugzilla.redhat.com/show_bug.cgi?id=2441762#c0.
CopyQ 16.0 is currently in testing; please upgrade to the latest release and re-test. If the issue persists on the new version, feel free to open a new ticket with updated logs.
I was copying values, from https://bugzilla.redhat.com/show_bug.cgi?id=2521586#c3. reporter: libreport-2.17.15 type: CCpp reason: copyq killed by SIGSEGV journald_cursor: s=a2d6d580caa24cf3a9483be7f85033e4;i=651ae7;b=5362a5fff17f4c27ab559d7dfd46f5fe;m=ddee2796;t=659b6ba177126;x=b1f712c019a77f9 executable: /usr/bin/copyq cmdline: /usr/bin/copyq --clipboard-access monitorClipboard cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-copyq rootdir: / uid: 1000 kernel: 7.1.9-200.fc44.x86_64 package: copyq-16.0.0-1.fc44 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: wl_proxy_get_version comment: I was copying values, from https://bugzilla.redhat.com/show_bug.cgi?id=2521586#c3.
I presume that https://retrace.fedoraproject.org/faf/reports/bthash/477ae0be3b1ca09deef022c1503e7310e1b1374f counts? I can also report a new ticket, if so.
That Retrace report is associated with Fedora 42, which is no longer supported. Since you can reproduce the crash with CopyQ 16.0 on Fedora 44, please open a new Bugzilla ticket and include the complete updated crash report and backtrace there.
Apologies. I likely cited the old trace because I forgot to generate a new one. However, note that the retrace server displays all packages as FC42 — that's why it's being retired — so it might well have been a valid trace, unless I missed something. I'd submit a new report, but I accidentally just deleted the report, having forgotten that it's not necessarily reproducible on demand: > ~~~ > RokeJulianLockhart@beedell:~$ abrt remove ab9a23b > Id ab9a23b > Component copyq > Count 1 > Time 2026-08-23 14:20:01 > Command line /usr/bin/copyq --clipboard-access monitorClipboard > Package copyq-16.0.0-1.fc44 > User id 1000 (RokeJulianLockhart) > Path /var/spool/abrt/ccpp-2026-08-23-14:20:01.607387-4358 > Reported to > ABRT Server https://retrace.fedoraproject.org/faf/reports/bthash/477ae0be3b1ca09deef022c1503e7310e1b1374f > Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=2467253 > > Are you sure you want to delete this problem? [y/N] y > Removed > ~~~ I should have just force-retraced it. I shall return in a few weeks or days, when it next reproduces, unless I possess a trace, on another machine, somewhere.
This appears to have approximately reproduced when a recurrence of https://bugzilla.redhat.com/show_bug.cgi?id=2467253#c19 did. reporter: libreport-2.17.15 type: CCpp reason: copyq killed by SIGSEGV journald_cursor: s=a2d6d580caa24cf3a9483be7f85033e4;i=6a16ef;b=6c3ba3ed07c444fb9aed3e98e9c6523c;m=1c9ef5be1;t=65b4bef4db98d;x=7e10e657fd579776 executable: /usr/bin/copyq cmdline: /usr/bin/copyq --clipboard-access monitorClipboard cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-copyq rootdir: / uid: 1000 kernel: 7.2.4-200.fc44.x86_64 package: copyq-16.0.0-1.fc44 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: wl_proxy_get_version comment: This appears to have approximately reproduced when a recurrence of https://bugzilla.redhat.com/show_bug.cgi?id=2467253#c19 did.
This appears to have approximately reproduced when a recurrence of https://bugzilla.redhat.com/show_bug.cgi?id=2467253#c19 did. reporter: libreport-2.17.15 type: CCpp reason: copyq killed by SIGSEGV journald_cursor: s=a2d6d580caa24cf3a9483be7f85033e4;i=6a16ef;b=6c3ba3ed07c444fb9aed3e98e9c6523c;m=1c9ef5be1;t=65b4bef4db98d;x=7e10e657fd579776 executable: /usr/bin/copyq cmdline: /usr/bin/copyq --clipboard-access monitorClipboard cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-copyq rootdir: / uid: 1000 kernel: 7.2.4-200.fc44.x86_64 package: copyq-16.0.0-1.fc44 runlevel: /bin/sh: line 1: runlevel: command not found reported_to: Bugzilla: URL=https://bugzilla.redhat.com/show_bug.cgi?id=2467253 backtrace_rating: 4 crash_function: wl_proxy_get_version comment: This appears to have approximately reproduced when a recurrence of https://bugzilla.redhat.com/show_bug.cgi?id=2467253#c19 did.
(In reply to Mr Beedell, Roke Julian Lockhart from comment #21) Apologies about that. That was actually the same recurrence, but due to what https://github.com/abrt/abrt/issues/1689#issue-3786852562 describes, failed to submit a separate report: > ~~~ > PS /> abrt report cda36d6 > Reporting problem cda36d6 > > Server responded with an error: 'Element 'desktop' is invalid: String '/usr/share/wayland-sessions/plasma.desktop' does not match the pattern '^[a-zA-Z0-9_/-]+$'' > no actions matching this problem found for event 'collect_GConf' > no actions matching this problem found for event 'collect_vimrc_system' > no actions matching this problem found for event 'collect_vimrc_user' > No /home/RokeJulianLockhart/.cache/gdm/session.log > Generating backtrace > Backtrace is generated and saved, 174318 bytes > Looking for similar problems in bugzilla > abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#2432616' was found > Searching for updates > No updates for this package found > > No changes were detected in the report > This problem was already reported to Bugzilla (see 'https://bugzilla.redhat.com/show_bug.cgi?id=246725'). Do you still want to create a new bug? [y/N] y > Checking for duplicates > Bug is already reported: 2467253 > Adding new comment to bug 2467253 > Status: CLOSED WONTFIX https://bugzilla.redhat.com/show_bug.cgi?id=2467253 > This problem does not have an uReport assigned. > Lock file '.lock' was locked by process 255278, but it crashed? > ~~~ Am I permitted to report upstream, instead of at RedHat Bugzilla, if I must manually file the bug anyway?
Of course.