Bug 501781

Summary: Random Plasmashell crash
Product: [Plasma] plasmashell Reporter: Mark <mark>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: crash CC: nate
Priority: NOR    
Version First Reported In: 6.3.3   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Full backtrace
Backtrace default fonts

Description Mark 2025-03-20 08:23:37 UTC
Created attachment 179595 [details]
Full backtrace

SUMMARY
I was using my laptop when suddenly the desktop stopped responding and crashed.

STEPS TO REPRODUCE
Unsure.

OBSERVED RESULT
Crash.

EXPECTED RESULT
No crash.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.7-200.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i7-11390H @ 3.40GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Xe Graphics


ADDITIONAL INFORMATION
Comment 1 Nate Graham 2025-03-21 17:25:03 UTC
Hmm, it appears to be crashing deep in font handling code:

#11 FcPatternObjectGetBool (p=0x7f5054024110, object=<optimized out>, id=0, b=0x7ffd9cca5420) at /usr/src/debug/fontconfig-2.15.0-8.fc41.x86_64/src/fcpat.c:1095
#12 IA__FcPatternGetBool (p=0x7f5054024110, object=0x7f509906f209 "variable", id=0, b=0x7ffd9cca5420) at /usr/src/debug/fontconfig-2.15.0-8.fc41.x86_64/src/fcpat.c:1107
#13 0x00007f5098e2ad50 in QFontconfigDatabase::setupFontEngine (this=this@entry=0x5644d76d46e0, engine=engine@entry=0x5644d86dd090, fontDef=...) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/gui/text/unix/qfontconfigdatabase.cpp:1047

Are you using any non-default fonts or font sizes, by any chance?
Comment 2 Mark 2025-03-21 18:19:34 UTC
(In reply to Nate Graham from comment #1)
> Hmm, it appears to be crashing deep in font handling code:
> 
> #11 FcPatternObjectGetBool (p=0x7f5054024110, object=<optimized out>, id=0,
> b=0x7ffd9cca5420) at
> /usr/src/debug/fontconfig-2.15.0-8.fc41.x86_64/src/fcpat.c:1095
> #12 IA__FcPatternGetBool (p=0x7f5054024110, object=0x7f509906f209
> "variable", id=0, b=0x7ffd9cca5420) at
> /usr/src/debug/fontconfig-2.15.0-8.fc41.x86_64/src/fcpat.c:1107
> #13 0x00007f5098e2ad50 in QFontconfigDatabase::setupFontEngine
> (this=this@entry=0x5644d76d46e0, engine=engine@entry=0x5644d86dd090,
> fontDef=...) at
> /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/gui/text/unix/
> qfontconfigdatabase.cpp:1047
> 
> Are you using any non-default fonts or font sizes, by any chance?

I am using Inter 12pt.

I can consistently reproduce it when using Bleachbit (in rootless mode) to clean the System > Cache.
Comment 3 Nate Graham 2025-03-21 18:42:57 UTC
General recommendation: don't use BleachBit. It will *create* problems where none previously existed, and this may be one of them.

For testing purposes, does the crash still happen if you do the same thing in BleachBit with default fonts in use?
Comment 4 Mark 2025-03-21 18:59:13 UTC
(In reply to Nate Graham from comment #3)
> General recommendation: don't use BleachBit. It will *create* problems where
> none previously existed, and this may be one of them.
> 
> For testing purposes, does the crash still happen if you do the same thing
> in BleachBit with default fonts in use?

It does.

Understood but for what it's worth, running Bleachbit (System > Cache only) on my desktop does not cause the same issue. For completeness, this is my desktop:

Operating System: openSUSE Tumbleweed 20250319
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.13.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER
Comment 5 Mark 2025-03-21 18:59:30 UTC
Created attachment 179638 [details]
Backtrace default fonts
Comment 6 Nate Graham 2025-03-21 19:15:15 UTC
Maybe don't do that, then! :D It seems like Fontconfig isn't happy about this happening on a logged-in system. Feel free to report it to the Fontconfig folks.
Comment 7 Mark 2025-03-21 19:21:17 UTC
(In reply to Nate Graham from comment #6)
> Maybe don't do that, then! :D It seems like Fontconfig isn't happy about
> this happening on a logged-in system. Feel free to report it to the
> Fontconfig folks.

That's what I thought! Thanks. 👍