Bug 491477 - plasmashell crashes after upgrade from Fedora 39 to Fedora 40 when connected remotely using TigerVNC
Summary: plasmashell crashes after upgrade from Fedora 39 to Fedora 40 when connected ...
Status: RESOLVED NOT A BUG
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (show other bugs)
Version: 6.1.3
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-09 10:32 UTC by Piotr Dobrogost
Modified: 2024-08-27 15:19 UTC (History)
1 user (show)

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

Attachments
Log fragment from the journal with information about plasmashell crash (56.16 KB, text/x-log)
2024-08-09 10:32 UTC, Piotr Dobrogost 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Piotr Dobrogost 2024-08-09 10:32:49 UTC 
Created attachment 172435 [details]
Log fragment from the journal with information about plasmashell crash

After upgrading from Fedora 39 to Fedora 40 plasmashell started to crash from time to time.
This is when I'm being connected remotely using TigerVNC, under X11 session (TigerVNC does not support Wayland).
See the attached log fragment from the journal.

Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.9.12-200.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-3240 CPU @ 3.40GHz
Memory: 7,7 GiB of RAM
Graphics Processor: llvmpipe
Comment 1 Nate Graham 2024-08-09 20:08:59 UTC 
Could you please install debug symbols and attach a new symbolicated backtrace generated by using `coredumpctl gdb` in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this. Thanks!
Comment 2 Bug Janitor Service 2024-08-24 03:47:36 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Piotr Dobrogost 2024-08-27 15:19:19 UTC 
It looks like the reason is memory leak in TigerVNC (https://github.com/TigerVNC/tigervnc/issues/1553) and Plasma and other processes are killed by oomkiller.