Bug 2273737

Created attachment 2025522 [details]
File: proc_pid_status

Created attachment 2025523 [details]
File: maps

Created attachment 2025524 [details]
File: limits

Created attachment 2025525 [details]
File: environ

Created attachment 2025526 [details]
File: open_fds

Created attachment 2025527 [details]
File: mountinfo

Created attachment 2025528 [details]
File: os_info

Created attachment 2025529 [details]
File: cpuinfo

Created attachment 2025530 [details]
File: core_backtrace

Created attachment 2025531 [details]
File: exploitable

Created attachment 2025532 [details]
File: backtrace

ticket opend manualy https://bugzilla.redhat.com/show_bug.cgi?id=2273828


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasma-systemmonitor killed by SIGSEGV
journald_cursor: s=6f31985489c84cf29c527b64f7430a3e;i=21ecd77;b=b5d004a178ea4c3e9d67160dd642957c;m=af5629134;t=615791ccefcab;x=72800adb48791cf1
executable:     /usr/bin/plasma-systemmonitor
cmdline:        /usr/bin/plasma-systemmonitor
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.plasma\x2dsystemmonitor-10da3a4ffad14ebeb24b62453b96eaba.scope
rootdir:        /
uid:            1000
kernel:         6.8.4-300.fc40.x86_64
package:        plasma-systemmonitor-6.0.3-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: QHashPrivate::iterator<QHashPrivate::Node<QModelIndex, QSortFilterProxyModelPrivate::Mapping*> >::node
comment:        ticket opend manualy https://bugzilla.redhat.com/show_bug.cgi?id=2273828

As 2273828 was accepted as a blocker, we should probably consider this too.

Nicolas Fella pointed this upstream issue as similar: https://bugs.kde.org/show_bug.cgi?id=479235

Just to be sure I checked here for the qt6-qtdeclarative version installed => qt6-qtdeclarative-6.6.2-3.fc40 so this bug really isn't a duplicate of #2273828

Created attachment 2025853 [details]
coredump

Steps to Reproduce:
1. Updated Fedora 40 KDE with all testing packages
2. Open system monitor.
3. Open details sidebar
4. Select one application to show details
5. Select another application
6. Keep selecting different apps for some time, like 10s for ex.

Actual Results:
System monitor crashes.

Adding upstream bug report reference: https://bugs.kde.org/show_bug.cgi?id=479235

Discussed during the 2024-04-08 blocker review meeting: [1]

The decision to classify this bug as a AcceptedBlocker (Final) was made:

""For all release-blocking desktop / arch combinations, the following applications must start successfully and withstand a basic functionality test: ...". system monitor is not in the current list, but there is a strong consensus at the meeting (including KDE SIG folks) that this was an oversight in drafting the list and it should always have been there. We will amend the list, and accept this bug in the meantime"

[1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-04-08/f40-blocker-review.2024-04-08-16.00.html

Per https://pagure.io/fedora-qa/blocker-review/issue/1572#comment-904795 I believe we should re-consider blocker status here, based on further testing by KDE SIG. Clearing AcceptedBlocker so this is now in proposed state again.

-3 blocker / +3 FE in https://pagure.io/fedora-qa/blocker-review/issue/1572 , updating.

I killed dnfdragora


reporter:       libreport-2.17.15
type:           CCpp
reason:         plasma-systemmonitor killed by SIGSEGV
journald_cursor: s=e005207fc8f146689869510a33ad4d2f;i=f54b25;b=d2c7bdfec79a4a3cb9644dfae789fc3f;m=32ee1bfe;t=61935125e2737;x=987223bd05045bfc
executable:     /usr/bin/plasma-systemmonitor
cmdline:        /usr/bin/plasma-systemmonitor
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.plasma\x2dsystemmonitor-fd58fb1dedeb4b1e81557ca6e029d30e.scope
rootdir:        /
uid:            1000
kernel:         6.8.10-300.fc40.x86_64
package:        plasma-systemmonitor-6.0.4-1.fc40
runlevel:       N 5
dso_list:       /usr/bin/plasma-systemmonitor plasma-systemmonitor-6.0.4-1.fc40.x86_64 (Fedora Project) 1714163342
backtrace_rating: 4
crash_function: QHashPrivate::iterator<QHashPrivate::Node<QModelIndex, QSortFilterProxyModelPrivate::Mapping*> >::node
comment:        I killed dnfdragora

This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-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 '40'.

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 40 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.

Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Per upstream issue: "Yes, this should be fixed with 6.4."