Bug 2480139

Summary:

[abrt] gwenview: KCrash::defaultCrashHandler(): gwenview killed by SIGSEGV

Product:

[Fedora] Fedora

Reporter:

Mr. Beedell, Roke Julian Lockhart (RJLB) <8ru2u4gz>

Component:

gwenview

Assignee:

Steve Cossette <farchord>

Status:

NEW ---

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

low

Docs Contact:

Priority:

low

Version:

CC:

8ru2u4gz, alekcejk, aurelien, awilliam, farchord, kde-sig, nathan95, than

Target Milestone:

---

Target Release:

---

Hardware:

x86_64

OS:

Linux

Whiteboard:

abrt_hash:45d16fb211aabef544fd8f7cc82db861569bff10;VARIANT_ID=kde;

Fixed In Version:

Doc Type:

---

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
File: proc_pid_status	none
File: maps	none
File: limits	none
File: environ	none
File: open_fds	none
File: mountinfo	none
File: os_info	none
File: cpuinfo	none
File: core_backtrace	none
File: dso_list	none
File: var_log_messages	none
File: backtrace	none
File: gwenview-20260519-220909.kcrash	none

Description Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:04 UTC

Description of problem:
This probably occurred when https://discussion.fedoraproject.org/t/how-can-i-ascertain-why-expo-caused-my-os-to-oom/191835 did.

Version-Release number of selected component:
gwenview-1:26.04.1-1.fc44

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         gwenview killed by SIGSEGV
journald_cursor: s=2c1910e140e64b2c86a6ef7504aaa761;i=10082;b=b8b7e2ab76e84f6bbdfb887c27eb234e;m=7f5bc5d62;t=6523217417f7f;x=6989aaa15c8f4fe3
executable:     /usr/bin/gwenview
cmdline:        /usr/bin/gwenview /home/beedell.roke_julian_lockhart/Pictures/Screenshots/Screenshot_20260519_180947.png
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.gwenview
rootdir:        /
uid:            1000
kernel:         7.0.8-200.fc44.x86_64
package:        gwenview-1:26.04.1-1.fc44
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: KCrash::defaultCrashHandler
comment:        This probably occurred when https://discussion.fedoraproject.org/t/how-can-i-ascertain-why-expo-caused-my-os-to-oom/191835 did.

Truncated backtrace:
Thread no. 1 (26 frames)
 #3 KCrash::defaultCrashHandler at /usr/src/debug/kf6-kcrash-6.26.0-1.fc44.x86_64/src/kcrash.cpp:623
 #5 QtWaylandClient::QWaylandInputDevice::pointer at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/tools/qscopedpointer.h:106
 #6 QtWaylandClient::QWaylandNativeInterface::nativeResourceForIntegration at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/plugins/platforms/wayland/qwaylandnativeinterface.cpp:57
 #7 Gwenview::WaylandGestures::init at /usr/include/c++/16/utility:116
 #8 QtPrivate::QSlotObjectBase::call at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qobjectdefs_impl.h:462
 #9 doActivate<false> at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qobject.cpp:4372
 #10 QtPrivate::QSlotObjectBase::call at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qobjectdefs_impl.h:462
 #11 doActivate<false> at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qobject.cpp:4372
 #12 QMetaObject::activate at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qobject.cpp:4432
 #13 QMetaObject::activate<void, QtWaylandClient::QWaylandDisplay::RegistryGlobal> at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qobjectdefs.h:320
 #14 QtWaylandClient::QWaylandDisplay::globalRemoved at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/redhat-linux-build/src/plugins/platforms/wayland/WaylandClient_autogen/include/moc_qwaylanddisplay_p.cpp:152
 #15 QtWaylandClient::QWaylandDisplay::reconnect at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/plugins/platforms/wayland/qwaylanddisplay.cpp:448
 #16 QObject::event at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qobject.cpp:1479
 #17 QApplicationPrivate::notify_helper at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/widgets/kernel/qapplication.cpp:3276
 #18 QCoreApplication::notifyInternal2 at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qcoreapplication.cpp:1114
 #19 QCoreApplication::sendEvent at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qcoreapplication.cpp:1559
 #20 QCoreApplicationPrivate::sendPostedEvents at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qcoreapplication.cpp:1914
 #21 postEventSourceDispatch at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:248
 #23 g_main_context_dispatch_unlocked at ../glib/gmain.c:4451
 #24 g_main_context_iterate_unlocked at ../glib/gmain.c:4516
 #25 g_main_context_iteration at ../glib/gmain.c:4582
 #26 QEventDispatcherGlib::processEvents at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:402
 #27 QEventLoop::exec at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/global/qflags.h:78
 #28 QCoreApplication::exec at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/corelib/kernel/qcoreapplication.cpp:1457
 #29 QGuiApplication::exec at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/gui/kernel/qguiapplication.cpp:2005
 #30 QApplication::exec at /usr/src/debug/qt6-qtbase-6.11.1-1.fc44.x86_64/src/widgets/kernel/qapplication.cpp:2546

Comment 1 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:06 UTC

Created attachment 2142072 [details]
File: proc_pid_status

Comment 2 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:07 UTC

Created attachment 2142073 [details]
File: maps

Comment 3 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:08 UTC

Created attachment 2142074 [details]
File: limits

Comment 4 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:09 UTC

Created attachment 2142075 [details]
File: environ

Comment 5 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:10 UTC

Created attachment 2142076 [details]
File: open_fds

Comment 6 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:11 UTC

Created attachment 2142077 [details]
File: mountinfo

Comment 7 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:13 UTC

Created attachment 2142078 [details]
File: os_info

Comment 8 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:14 UTC

Created attachment 2142079 [details]
File: cpuinfo

Comment 9 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:15 UTC

Created attachment 2142080 [details]
File: core_backtrace

Comment 10 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:16 UTC

Created attachment 2142081 [details]
File: dso_list

Comment 11 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:18 UTC

Created attachment 2142082 [details]
File: var_log_messages

Comment 12 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:19 UTC

Created attachment 2142083 [details]
File: backtrace

Comment 13 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-20 11:34:20 UTC

Created attachment 2142084 [details]
File: gwenview-20260519-220909.kcrash

Comment 14 Nathan 2026-05-21 09:25:57 UTC

A change request has been submitted to the upstream KDE project. See the pull request: https://invent.kde.org/graphics/gwenview/-/merge_requests/376

Comment 15 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-21 10:27:10 UTC

Thanks. I would have filed a Konqi report, but the reboot rendered it unusable.

Comment 16 Adam Williamson 2026-05-27 18:25:14 UTC

Another case of questionable autonomous agentic AI activity, see https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/SFVETHOYKQAO7KKLEXCK4IBT4WVPRE6F/ . Re-assigning to correct maintainer. Please treat the MR with caution.

Comment 17 Mr. Beedell, Roke Julian Lockhart (RJLB) 2026-05-27 20:52:18 UTC

Thanks. Because the AI was later exposed to not be under Nathan's control (rather, he was compromised), can the status of this be changed back to NEW? We shouldn't accept any maliciously-written MRs, as a matter of course. I can't change it myself.