Bug 484602 - Plasmashell crash when cycling through grouped task in Task Manager
Summary: Plasmashell crash when cycling through grouped task in Task Manager
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 6.0.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-03-27 14:09 UTC by marco.magliona
Modified: 2024-06-17 17:21 UTC (History)
1 user (show)

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


Attachments
New crash information added by DrKonqi (147.39 KB, text/plain)
2024-03-27 14:09 UTC, marco.magliona
Details

Note You need to log in before you can comment on or make changes to this bug.
Description marco.magliona 2024-03-27 14:09:20 UTC
Application: plasmashell (6.0.2)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.8.1-zen1-1-zen x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 6.0.2 [CoredumpBackend]

-- Information about the crash:
While "scrolling" with the mouse on top of a grouped task in the task manager widget in the panel, plasma shell crashed completely.
The "preview when hovering" of the task manager stayed visible until the restart of plasma.
I cannot reproduce it anymore. Tried multiple times.
I had a similar crash while moving through windows, but I do not remember what I was doing more in detail.

The crash does not seem to be reproducible.

-- Backtrace (Reduced):
#5  0x00007f21cbe31441 in core_event_add_mem (data=0x5ce948ded260, id=102, type=3, fd=-1, flags=0) at ../pipewire/src/pipewire/core.c:84
#6  0x00007f21a6b29bcc in core_event_demarshal_add_mem (data=<optimized out>, msg=<optimized out>) at ../pipewire/src/modules/module-protocol-native/protocol-native.c:443
#7  0x00007f21a6b20162 in process_remote (impl=impl@entry=0x5ce948dedf40) at ../pipewire/src/modules/module-protocol-native.c:1037
#8  0x00007f21a6b20940 in on_remote_data (data=0x5ce948dedf40, fd=93, mask=5) at ../pipewire/src/modules/module-protocol-native.c:1071
#9  0x00007f21d0aa2646 in loop_iterate (object=0x5ce948dcced8, timeout=<optimized out>) at ../pipewire/spa/plugins/support/loop.c:496


Reported using DrKonqi
Comment 1 marco.magliona 2024-03-27 14:09:20 UTC
Created attachment 167848 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 2 Akseli Lahtinen 2024-06-14 12:29:06 UTC
I can't reproduce this either on Plasma 6.1

Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.80
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.1
Kernel Version: 6.8.11-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6600

However, do you remember what application it was that you were scrolling over?
Comment 3 Akseli Lahtinen 2024-06-14 12:29:17 UTC
.
Comment 4 marco.magliona 2024-06-15 15:25:25 UTC
(In reply to Akseli Lahtinen from comment #2)
> I can't reproduce this either on Plasma 6.1
> 
> Operating System: Fedora Linux 40
> KDE Plasma Version: 6.1.80
> KDE Frameworks Version: 6.4.0
> Qt Version: 6.7.1
> Kernel Version: 6.8.11-300.fc40.x86_64 (64-bit)
> Graphics Platform: Wayland
> Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
> Memory: 15.5 GiB of RAM
> Graphics Processor: AMD Radeon RX 6600
> 
> However, do you remember what application it was that you were scrolling
> over?

I usually have a couple of Clion windows opened and it was quite glitchy before (I used to have this https://bugs.kde.org/show_bug.cgi?id=483162, https://youtrack.jetbrains.com/issue/JBR-6921/Plasma-6-Cannot-click-on-one-IDE-instance-when-a-second-one-is-running).
I think it was Clion, since minimizing and switching windows with scrolling would kind of momentary "fix" with the old bugs above.
I've updated Plasma soon after this report and I've not seen any more occurrences.
Comment 5 Akseli Lahtinen 2024-06-17 17:21:38 UTC
I'm setting this as fixed, since it seems to work for you now. If it reoccurs, feel free to open this bug report again :) Thanks!