Bug 485751 - plasma-systemmonitor crashes when clicking show details sidebar
Summary: plasma-systemmonitor crashes when clicking show details sidebar
Status: RESOLVED DUPLICATE of bug 482169
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: 6.0.4
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-18 18:49 UTC by Julien Delquié
Modified: 2024-04-18 19:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Demo of the issue (2.25 MB, video/webm)
2024-04-18 18:50 UTC, Julien Delquié
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Delquié 2024-04-18 18:49:17 UTC
SUMMARY

plasma-systemmonitor crashes when clicking show details sidebar.

I don’t have a backtrace (don’t know why DrKonqi is not launched).

STEPS TO REPRODUCE
1. Open plasma-systemmonitor
2. Click on Applications
3. Click on show details sidebar

OBSERVED RESULT

plasma-systemmonitor crashes.

EXPECTED RESULT

plasma-systemmonitor shows details in sidebar.

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.15
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.6-gentoo-x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 31.3 Gio of RAM
Graphics Processor: AMD Radeon RX 7800 XT

ADDITIONAL INFORMATION

There is a demo of the crash in attachment.

Here is what I can find in dmesg:
avril 18 20:40:21 pasokon.maison kernel: plasma-systemmo[407398]: segfault at 8 ip 00007f21b8799f44 sp 00007fff7b777848 error 4 in libQt6Quick.so.6.7.0[7f21b841f000+3e5000] likely on CPU 3 (core 3, socket 0)
avril 18 20:40:21 pasokon.maison kernel: Code: 66 0f 1f 44 00 00 f3 0f 1e fa 53 48 89 f8 48 89 f7 48 8b 58 08 e8 fc 63 c9 ff 48 89 df 5b 89 c6 e9 b1 ff ff ff 90 f3 0f 1e fa <48> 8b 47 08 48 8b 80 e8 00 00 00 c3 f3 0f 1e fa 41 55 41 54 55 53
avril 18 20:40:21 pasokon.maison systemd[1]: Started Process Core Dump (PID 408480/UID 0).
avril 18 20:40:21 pasokon.maison systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
avril 18 20:40:22 pasokon.maison systemd-coredump[408481]: elfutils disabled, parsing ELF objects not supported
avril 18 20:40:22 pasokon.maison systemd-coredump[408481]: Process 407398 (plasma-systemmo) of user 1000 dumped core.
avril 18 20:40:22 pasokon.maison systemd[1]: systemd-coredump@7-408480-0.service: Deactivated successfully.
avril 18 20:40:23 pasokon.maison drkonqi-coredump-processor[408489]: Entry doesn't look like a dump. This may have been a vaccum run. Nothing to process.
avril 18 20:40:23 pasokon.maison drkonqi-coredump-processor[408489]: "/usr/bin/plasma-systemmonitor" 407398 "/var/lib/systemd/coredump/core.plasma-systemmo.1000.19c1cd6b786042a3bbdeb3e73dd14f88.407398.1713465621000000.zst"
avril 18 20:40:23 pasokon.maison systemd[1]: drkonqi-coredump-processor@7-408480-0.service: Deactivated successfully.
avril 18 20:40:23 pasokon.maison systemd[2533]: Started Launch DrKonqi for a systemd-coredump crash (PID 408489/UID 0).
avril 18 20:40:23 pasokon.maison drkonqi-coredump-launcher[408565]: Unable to find file for pid 407398 expected at "kcrash-metadata/plasma-systemmonitor.19c1cd6b786042a3bbdeb3e73dd14f88.407398.ini"
avril 18 20:40:23 pasokon.maison drkonqi-coredump-launcher[408565]: Nothing handled the dump :O
avril 18 20:40:23 pasokon.maison plasmashell[408572]: Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice().
avril 18 20:40:23 pasokon.maison systemd[2533]: app-org.kde.plasma\x2dsystemmonitor-25b673c25ace4f908c8318e1e183c539.scope: Consumed 7.026s CPU time.
Comment 1 Julien Delquié 2024-04-18 18:50:29 UTC
Created attachment 168652 [details]
Demo of the issue
Comment 2 Julien Delquié 2024-04-18 18:51:11 UTC
Sorry, that was in journalctl, not dmesg.
Comment 3 Patrick Silva 2024-04-18 19:48:06 UTC

*** This bug has been marked as a duplicate of bug 482169 ***