[Bug]: fontconfig cache gets corrupted upon Helium launch, causing other applications to crash

Open
#402 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, shell
Domain
desktop

Research direction

Start by checking how Helium is packaged and launched on Linux, then trace which bundled or system fontconfig libraries and cache settings it uses. Reproduce on Fedora with a freshly rebuilt font cache and compare the cache changes after launching Helium 0.18.1.1 with those from 0.17.2.1. Done means Helium no longer corrupts the cache or causes affected applications to crash.

Written by the indexing model from the issue text.

Description

bug upstream
Version

0.18.1.1 (Official Build, Chromium 154.0.8037.57) rpm (x86_64)

Have you tested that this is not an upstream issue or an issue with your configuration?
  • I have tried reproducing this issue in Chrome and it could not be reproduced there
  • I have tried reproducing this issue in ungoogled-chromium and it could not be reproduced there
  • I have tried reproducing this issue in Helium with a new and empty profile using --user-data-dir command line argument and it could not be reproduced there
Description

fontconfig cache gets corrupted upon Helium launch, causing other applications to crash

How to Reproduce?
  1. Clear and rebuild the font cache:
user@fedora:~$ rm -rf ~/.cache/fontconfig
user@fedora:~$ fc-cache -rv

Inspect the ~/.cache/fontconfig directory to confirm there are only .cache-9-type files.
2) Launch Helium. Observe it making changes in the cache directory, specifically creating .cache-12 files and symlinks.
3) Launch an affected application (I mostly saw Qt-based apps being affected).

Actual behavior

The launched app crashes with a segfault:

user@fedora:~$ dolphin
KCrash: Application 'dolphin' crashing... crashRecursionCounter = 2
Segmentation fault         (core dumped) dolphin
user@fedora:~$ 

Inspecting the core dump confirms that the crash occurs in libfontconfig:

                Stack trace of thread 14742:
                #0  0x00007f195f67bccc __pthread_kill_implementation (libc.so.6 + 0x74ccc)
                #1  0x00007f195f620e8e raise (libc.so.6 + 0x19e8e)
                #2  0x00007f19625cd0d4 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x50d4)
                #3  0x00007f195f620fb0 __restore_rt (libc.so.6 + 0x19fb0)
                #4  0x00007f195e85783c FcCharSetFindLeafForward.lto_priv.0 (libfontconfig.so.1 + 0x483c)
                #5  0x00007f195e858262 FcCharSetHasChar (libfontconfig.so.1 + 0x5262)
                #6  0x00007f1960aa3f2c _ZNK26QFontEngineMultiFontConfig32shouldLoadFontEngineForCharacterEij (libQt6Gui.so.6 + 0x6a3f2c)
                #7  0x00007f1960835766 _ZNK16QFontEngineMulti12stringToCMapEPK5QChariP12QGlyphLayoutPi6QFlagsIN11QFontEngine10ShaperFlagEE (libQt6Gui.so.6 + 0x435766)
                #8  0x00007f19608cb81b _ZNK11QTextEngine9shapeTextEi (libQt6Gui.so.6 + 0x4cb81b)
                #9  0x00007f19608cec0b _ZNK11QTextEngine5widthEii (libQt6Gui.so.6 + 0x4cec0b)
                #10 0x00007f19608396f6 _ZNK12QFontMetrics17horizontalAdvanceERK7QStringi (libQt6Gui.so.6 + 0x4396f6)
Expected behavior

This should not be happening. I really don't know what else to write here.

Additional context

Observed on Fedora 44 KDE after updating Helium from 0.17.2.1 to 0.18.1.1.
This issue can make the entire system unusable until the font cache is rebuilt, since system processes - including KDE itself - rely on it too and crash when attempting to read it. In my case, I thought a reboot would fix the problem when I first encountered it, but instead it broke the DE because plasmashell failed to start with the same segfault.
Downgrading back to 0.17.2.1 showed that this version was also modifying the font cache, but using .cache-11 type files with no symlinks, which didn't cause any issues.

Dominant language
Shell
Stars
1.1k
Forks
63
Avg merge
28m
Merged PRs (30d)
11

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from imputnet/helium-linux

All issues in imputnet/helium-linux

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.