Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I believe that I've ascertained how to reproduce https://bugs.kde.org/show_bug.cgi?id=437675#c1: take a photograph, then quickly invoke the effect sidebar. Version-Release number of selected component: kamoso-25.08.0-1.fc42 Additional info: reporter: libreport-2.17.15 type: CCpp reason: kamoso killed by SIGSEGV journald_cursor: s=a2d6d580caa24cf3a9483be7f85033e4;i=26dbbc;b=d9556942b8a740ffb2d9bea7885652e1;m=3c5f3d8c0;t=63d4b5fec7872;x=fd1fb1f1a0c528d executable: /usr/bin/kamoso cmdline: kamoso cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.konsole rootdir: / uid: 1000 kernel: 6.15.10-200.fc42.x86_64 package: kamoso-25.08.0-1.fc42 runlevel: N 5 backtrace_rating: 4 crash_function: std::__atomic_base<QObjectPrivate::Connection*>::load comment: I believe that I've ascertained how to reproduce https://bugs.kde.org/show_bug.cgi?id=437675#c1: take a photograph, then quickly invoke the effect sidebar. Truncated backtrace: Thread no. 0 (19 frames) #0 std::__atomic_base<QObjectPrivate::Connection*>::load at /usr/include/c++/15/bits/atomic_base.h:828 #1 std::atomic<QObjectPrivate::Connection*>::load at /usr/include/c++/15/atomic:587 #2 QAtomicOps<QObjectPrivate::Connection*>::loadAcquire<QObjectPrivate::Connection*> at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/thread/qatomic_cxx11.h:214 #3 QBasicAtomicPointer<QObjectPrivate::Connection>::loadAcquire at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/thread/qbasicatomic.h:177 #4 QObjectPrivate::maybeSignalConnected at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:457 #5 doActivate<false> at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4046 #6 QMetaObject::activate at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qobject.cpp:4206 #7 PipelineItem::failed at /usr/src/debug/kamoso-25.08.0-1.fc42.x86_64/redhat-linux-build/src/kamoso_autogen/include/webcamcontrol.moc:189 #8 PipelineItem::onBusMessage at /usr/src/debug/kamoso-25.08.0-1.fc42.x86_64/src/video/webcamcontrol.cpp:100 #9 PipelineItem::pipelineWatch at /usr/src/debug/kamoso-25.08.0-1.fc42.x86_64/src/video/webcamcontrol.cpp:156 #10 gst_bus_source_dispatch at ../gst/gstbus.c:841 #12 g_main_context_dispatch_unlocked at ../glib/gmain.c:4249 #13 g_main_context_iterate_unlocked at ../glib/gmain.c:4314 #14 g_main_context_iteration at ../glib/gmain.c:4379 #15 QEventDispatcherGlib::processEvents at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:399 #16 QEventLoop::exec at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/global/qflags.h:77 #17 QCoreApplication::exec at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/corelib/kernel/qcoreapplication.cpp:1449 #18 QGuiApplication::exec at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/gui/kernel/qguiapplication.cpp:1986 #19 QApplication::exec at /usr/src/debug/qt6-qtbase-6.9.1-1.fc42.x86_64/src/widgets/kernel/qapplication.cpp:2570
Created attachment 2104900 [details] File: proc_pid_status
Created attachment 2104901 [details] File: maps
Created attachment 2104902 [details] File: limits
Created attachment 2104903 [details] File: environ
Created attachment 2104904 [details] File: open_fds
Created attachment 2104905 [details] File: mountinfo
Created attachment 2104906 [details] File: os_info
Created attachment 2104907 [details] File: cpuinfo
Created attachment 2104908 [details] File: core_backtrace
Created attachment 2104909 [details] File: exploitable
Created attachment 2104910 [details] File: dso_list
Created attachment 2104911 [details] File: backtrace
IDK whether the previews being white, per https://bugzilla.redhat.com/show_bug.cgi?id=2391167#c0, is relevant, since they weren't when this was first reported (if this is the same problem as https://bugs.kde.org/show_bug.cgi?id=437675#c1). Is this even the same as the linked upstream ticket?
Per https://bugzilla.redhat.com/show_bug.cgi?id=2391169#c0, shall remove the upstream connection, replacing it with a tentative connection to https://bugzilla.redhat.com/show_bug.cgi?id=2391169#c0, and am clearing the `NEEDINFO`.
This message is a reminder that Fedora Linux 42 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '42'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 42 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
> You tried to change the Whiteboard field from abrt_hash:352bea4b5fd265e9d76fe11ed7bd17a29368f360;VARIANT_ID=kde; to abrt_hash:352bea4b5fd265e9d76fe11ed7bd17a29368f360;VARIANT_ID=kde; | abrt_hash:06f2df1d83fa9f3d5069a7cd595b2ee2bda9fa0b;VARIANT_ID=kde;, but only the assignee or reporter of the bug, or a user with the required permissions may change that field. *** This bug has been marked as a duplicate of bug 2463756 ***