Repository navigation
Description
Summary
Launching Codex Desktop on Kubuntu 24.04 reproducibly rewrites my user
fontconfig cache in ~/.cache/fontconfig using cache format 12 and creates
compatibility symlinks from older cache filenames (cache-9, cache-10,
cache-11) to the cache-12 files.
After this happens, KDE Plasma and other Qt/KDE applications begin crashing
with SIGSEGV in fontconfig. plasmashell crashes shortly after startup,
leaving a black desktop with only the mouse cursor visible.
Removing the corrupted cache and regenerating it with the system
/usr/bin/fc-cache immediately restores the desktop.
Launching Codex Desktop again reproduces the corruption and the crashes.
This is therefore reproducible A/B on the same machine.
Environment
- OS: Kubuntu 24.04.4 LTS
- Architecture: x86_64
- Desktop: KDE Plasma
- Codex / ChatGPT Desktop package:
chatgptamd64 - Current package version: 26.924.20706
- Previous package version: 26.917.71314
- GPU: NVIDIA RTX 4080 SUPER
- Package installed from the official OpenAI Linux repository
Additional environment information can be provided if needed.
Reproduction
-
Make sure Codex Desktop is not running.
-
Remove/move the existing user fontconfig cache and regenerate it with
the system fontconfig:mv ~/.cache/fontconfig ~/.cache/fontconfig.backup mkdir -p ~/.cache/fontconfig /usr/bin/fc-cache -f
-
Verify that there are no cache-format-12 files or compatibility symlinks:
find ~/.cache/fontconfig -maxdepth 1
( -name '*.cache-12' -o -type l )
-printf '%TY-%Tm-%Td %TH:%TM:%TS %y %f -> %l\n' | sortOutput is empty.
-
At this point KDE Plasma and Qt applications work normally.
-
Launch Codex Desktop.
-
Immediately after launching Codex, the following files appear in
~/.cache/fontconfig:
4c599c202bc5c08e2d34565a40eac3b2-le64.cache-12
4c599c202bc5c08e2d34565a40eac3b2-le64.cache-9
-> 4c599c202bc5c08e2d34565a40eac3b2-le64.cache-12
4c599c202bc5c08e2d34565a40eac3b2-le64.cache-10
-> 4c599c202bc5c08e2d34565a40eac3b2-le64.cache-12
4c599c202bc5c08e2d34565a40eac3b2-le64.cache-11
-> 4c599c202bc5c08e2d34565a40eac3b2-le64.cache-12The same pattern is created for multiple font directories.
-
KDE/Qt applications then begin crashing. plasmashell reproducibly
terminates with:
Signal: Segmentation fault (11)
Executable: plasmashellThe desktop becomes black, although KWin/the X session remains alive
and a Konsole window can still be opened by keyboard shortcut. -
Stop Codex, delete/move the fontconfig cache again, and regenerate it:
mv ~/.cache/fontconfig ~/.cache/fontconfig.bad
mkdir -p ~/.cache/fontconfig
/usr/bin/fc-cache -fPlasma and other Qt/KDE applications immediately become stable again.
-
Launching Codex Desktop once more reproduces steps 6-7.
Actual behavior
Codex appears to use a newer bundled fontconfig/cache implementation and
writes format-12 cache files into the host user's shared
~/.cache/fontconfig.
It additionally creates older-format filenames as symlinks to the
format-12 files.
The host system fontconfig subsequently appears to consume those files as
its own cache format, resulting in invalid memory access / SIGSEGV in
applications using the system fontconfig library.
The impact is system-wide: it is not limited to Codex itself. Plasma,
Kate, KRunner and other KDE/Qt applications are affected.
Expected behavior
Codex and its bundled runtime must not write an incompatible fontconfig
cache into the host user's shared fontconfig cache directory.
If the bundled runtime requires a newer fontconfig cache format, it should
use an isolated cache location, for example a Codex-specific
XDG_CACHE_HOME / fontconfig cache directory.
Launching Codex must not be capable of making unrelated host desktop
applications crash.
Recovery
The machine can be recovered without reinstalling KDE or NVIDIA drivers by: -
terminating Codex;
-
moving/removing ~/.cache/fontconfig;
-
rebuilding the cache specifically with /usr/bin/fc-cache -f.
After this, Plasma is stable until Codex Desktop is launched again.
Notes
This was reproduced multiple times.
The timestamps of the cache-12 files and the cache-9/10/11 -> cache-12
symlinks correspond to the Codex launch.
Before launching Codex after a clean cache rebuild, the files are absent.
Immediately after launching Codex, they appear and KDE starts crashing.
There are already Codex issues discussing bundled fontconfig runtimes and
the need for isolated XDG_CACHE_HOME, but I could not find an existing
report describing this host-cache corruption and system-wide KDE crash.
Activity
ocaiev101 commentedon Sep 26, 2026
Same issue observed on Kubuntu 26.04. Adding more info below.
Title: Bundled sharp/libvips (fontconfig 2.18.3) writes v12 caches and cache-9/10/11 symlinks into shared ~/.cache/fontconfig, breaking system fontconfig 2.17.1
Environment
Kubuntu 26.04.1 LTS, kernel 7.0.0-34-generic, KDE Plasma 6.6.6 (Wayland)
System fontconfig: fontconfig 2.17.1-3ubuntu1 (fc-cache -V → fontconfig version 2.17.1)
Qt 6.10.2 (libqt6gui6 6.10.2+dfsg-7), Konsole 25.12.3
codex --version → codex-cli 0.157.0
chatgpt --version → 26.915.31945 (problem started after the auto-update to 26.924.20706 on 2026-09-25; rolling back to 26.915.31945 did not help, and that version ships the same library)
Bundled library, identical in both products: sharp 0.35.4, libvips 8.18.6, fontconfig 2.18.3, pango 1.58.2, freetype 2.14.3
~/.cache/codex-runtimes/codex-primary-runtime/dependencies/node/node_modules/@img/sharp-libvips-linux-x64/lib/libvips-cpp.so.8.18.6
/usr/lib/chatgpt/resources/cua_node/lib/node_modules/@img/sharp-libvips-linux-x64/lib/libvips-cpp.so.8.18.6
Minimal repro (cache corruption, deterministic)
R=~/.cache/codex-runtimes/codex-primary-runtime/dependencies/node
mkdir -p /tmp/fc-repro
XDG_CACHE_HOME=/tmp/fc-repro NODE_PATH=$R/node_modules $R/bin/node
-e "require('sharp')({text:{text:'hello'}}).png().toBuffer()"
ls -l /tmp/fc-repro/fontconfig | head -50
Expected: either no writes to the shared user cache, or caches in the format the system fontconfig uses (cache-9).
Actual: 32 *-le64.cache-12 files, plus cache-9, cache-10 and cache-11 symlinks for each one pointing at the v12 file:
lrwxrwxrwx 1 user user 46 Sep 26 03:29 0bd3dc0958fa2205aaaa8ebb13e2872b-le64.cache-10 -> 0bd3dc0958fa2205aaaa8ebb13e2872b-le64.cache-12
lrwxrwxrwx 1 user user 46 Sep 26 03:29 0bd3dc0958fa2205aaaa8ebb13e2872b-le64.cache-11 -> 0bd3dc0958fa2205aaaa8ebb13e2872b-le64.cache-12
-rw-rw-r-- 1 user user 556864 Sep 26 03:29 0bd3dc0958fa2205aaaa8ebb13e2872b-le64.cache-12
lrwxrwxrwx 1 user user 46 Sep 26 03:29 0bd3dc0958fa2205aaaa8ebb13e2872b-le64.cache-9 -> 0bd3dc0958fa2205aaaa8ebb13e2872b-le64.cache-12
lrwxrwxrwx 1 user user 46 Sep 26 03:29 188ac73a183f12857f63bb60a4a6d603-le64.cache-10 -> 188ac73a183f12857f63bb60a4a6d603-le64.cache-12
...
counts by suffix: 32× cache-9 (symlinks), 32× cache-10 (symlinks), 32× cache-11 (symlinks), 32× cache-12 (files)
The symlinks come from the bundled fontconfig; libvips-cpp.so.8.18.6 contains FcDirCacheWrite: symlink %s -> %s failed. With no XDG_CACHE_HOME set, the files go into the real ~/.cache/fontconfig, which every system application also reads.
Observed impact
About 30 Konsole SIGSEGVs, plus several in System Settings, over roughly 10 hours after the update. Konsole crashed whenever a CLI tool such as codex or claude printed Unicode symbols. Every crash had the same stack:
#4 libfontconfig.so.1 + 0xc4fc
#5 FcCharSetHasChar (libfontconfig.so.1)
#6 QFontEngineMultiFontConfig::shouldLoadFontEngineForCharacter (libQt6Gui.so.6)
...
#13 Konsole::TerminalDisplay::paintEvent (libkonsoleprivate.so.25.12.3)
Deleting ~/.cache/fontconfig stopped the crashes only until ChatGPT or Codex ran again and recreated the v12 files and symlinks.
Rebuilding the cache with the system fc-cache -f and then running chmod 555 ~/.cache/fontconfig ~/.fontconfig stopped the crashes completely.
Caveat: I couldn't trigger the crash on demand by pointing a fresh Konsole at a freshly corrupted temporary cache (XDG_CACHE_HOME). The cache corruption is certain; the exact trigger for the crash in system fontconfig isn't confirmed.
Suggested fix
Isolate the bundled fontconfig's cache from the user's shared cache, for example with a private FONTCONFIG_FILE whose points to an app-owned directory. Alternatively, stop it from creating backward-compatible cache-N symlinks, or link against the system fontconfig on Linux.
halfdecay commentedon Sep 26, 2026
Update: reproduced after a completely clean OS reinstall, and isolated XDG_CACHE_HOME prevents host cache corruption
I completely reinstalled the system and the problem is still reproducible.
New environment:
Before applying the workaround, the system fontconfig state was already broken:
fc-match sans
KaTeX_AMS-Regular.woff: "Noto Sans" ""
and ~/.cache/fontconfig contained cache-12 files plus symlinks such as:
*.cache-9 -> *.cache-12
*.cache-10 -> *.cache-12
*.cache-11 -> *.cache-12
After removing/rebuilding the host fontconfig cache with /usr/bin/fc-cache, the host cache contained no cache-12 files/symlinks and KDE was stable.
I then launched the GUI explicitly with an isolated cache:
env XDG_CACHE_HOME="$HOME/.cache/chatgpt-isolated" chatgpt
Result:
~/.cache/fontconfig
no cache-12 files or compatibility symlinks
~/.cache/chatgpt-isolated/fontconfig
*.cache-12
*.cache-9 -> *.cache-12
*.cache-10 -> *.cache-12
*.cache-11 -> *.cache-12
With this isolation in place, KDE Plasma remains stable.
This appears to confirm that the ChatGPT/Codex Desktop process is creating the format-12 fontconfig caches and that the system-wide crashes occur because those caches are normally written into the shared host ~/.cache/fontconfig.
A practical workaround is to launch the app with a private XDG_CACHE_HOME. Ideally the Linux desktop package should isolate its bundled fontconfig cache itself rather than sharing the host user's fontconfig cache.
skup04 commentedon Sep 27, 2026
I hit what appears to be the same issue on Fedora 44, with a different desktop/toolkit stack.
Environment
fontconfig-2.17.0-4.fc44.x86_64/usr/bin/fc-cache -V:fontconfig version 2.17.0Impact
Sota Connect stopped showing its GUI.
The process itself stayed alive:
and its system daemon (
sotad) was healthy and responding normally, so this was not a daemon/VPN failure.The application emitted no fatal error; it simply stayed running without displaying a window.
Repair
I was able to isolate the failure to the user fontconfig cache.
With the normal cache:
the GUI did not appear.
With a completely fresh cache:
the GUI opened normally.
I then tested the old fontconfig cache in isolation:
The GUI stopped appearing again.
So the old
~/.cache/fontconfigalone was sufficient to reproduce the failure.Corrupted cache structure
The old cache contained:
*-le64.cache-12filesFor each cache hash, the following pattern existed:
This matches the cache layout described in this issue.
The files and symlinks were created in a very narrow time window on September 25, 2026.
Recovery
Removing the affected cache and rebuilding it specifically with the Fedora system fontconfig fixed the issue:
rm -rf ~/.cache/fontconfig /usr/bin/fc-cache -r -vAfter that, Sota Connect launched normally again.
Additional observation
This shows that the impact is not limited to KDE/Qt.
In this case an unrelated Flutter/GTK3 application was also affected by the shared fontconfig cache corruption.
I also had an Anaconda installation containing an older
fc-cache(2.15.0) earlier in$PATH. I have since disabled automatic activation of the Conda base environment, and verified that the cache rebuild above used Fedora's/usr/bin/fc-cache2.17.0.I have not intentionally re-triggered the corruption after recovery yet, but the cache structure I found matches the
cache-9/10/11 -> cache-12pattern reported here.HYLi360 commentedon Sep 28, 2026
This appears to be related to this bug: https://issues.chromium.org/issues/565132857, and has been fixed today.
xuhengjing020504 commentedon Sep 30, 2026
Confirming this still reproduces with the installed Linux chatgpt 26.928.20755 package, despite the earlier comment about an upstream fix.
Environment: Ubuntu 26.04.1, Plasma/KWin 6.6.6 (Wayland), system fontconfig 2.17.1. The app-bundled sharp reports 0.35.4, libvips 8.18.6, and fontconfig 2.18.3.
Using the isolated sharp text-rendering test described above, with the Node/sharp under
/usr/lib/chatgpt/resources/cua_nodeand a fresh temporaryXDG_CACHE_HOME, produced:cache-12files;cache-9,cache-10, andcache-11, all pointing to format-12 files.File headers confirmed version 12; the real desktop cache was unchanged by the test.
Additional impact on this machine: September 29 crash records show 12 plasmashell and 7 kwin_wayland crashes during a 25-minute interval. Sampled stacks include
FcCharSetHasChar; the final KWin crash followed repeated lock-screen greeter failures and involved text drawing inlibKScreenLocker. Display connections were lost andksmserverrequired separate recovery. The exact writer during that historical incident was not traced.Please check the shipped sharp/libvips dependency, not only Chromium. Also, a private app cache protects the host desktop, but native Qt child processes may inherit it; mixed bundled/system-fontconfig consumers need consideration.
yuzhu-oai commentedon Sep 30, 2026
Thanks for the reports, and sorry for the disruption. We traced this to font-cache handling in our bundled Chromium and Sharp/libvips dependencies. Fixes are available upstream, and we’re working to include them in the app and will release soon.
To recover now, fully quit Codex/ChatGPT Desktop, then run this in a system terminal without sudo:
/usr/bin/fc-cache -rRestart affected applications afterward. This rebuilds the cache without deleting your fonts.
If the issue comes back before we release the fixes, please repeat these recovery steps. The fixes will prevent it from recurring, though an already affected cache may need one final rebuild after updating.
korypostma commentedon Oct 1, 2026
Additional Fedora 44 evidence for issue #48217
I encountered the same cache layout and desktop failure on Fedora 44 KDE/Wayland with
chatgpt-26.924.50649-1.x86_64(/usr/lib/chatgpt/ChatGPT). System Fontconfig is2.17.0-4.fc44; Qt is6.11.2-2.fc44; Plasma is6.7.5-1.fc44.The preserved user font cache contains 121 version-12 files and 363 symlinks from version-9/10/11 filenames to those files. For the Logix cache, the file and aliases have timestamp 2026-09-30 15:55:23.910875 CDT. The application journal records ChatGPT launching at 15:55:24.974026 CDT, followed by its startup initialization. A later recurrence and application-specific cache-isolation test are described below. The exact process making the original write/symlink calls has not been traced.
Additional diagnostic evidence:
fc-cache.logix.wofffrom the old cache and getsFcResultNoMatchfor its charset.0xfefefefefefefefetoFcCharSetHasChar.The installed Qt function lacks the check in the existing upstream correction:
qt/qtbase@80ddc8dee6a0
The Chromium-side related report is:
https://issuetracker.google.com/issues/565132857
Could you confirm whether this desktop build includes the shared Fontconfig cache-writing fix, and which application release prevents these cross-version aliases or isolates the bundled runtime's font cache? A Qt crash fix and an application-side cache fix address different parts of this failure.
I have a reduced good/bad cache pair, a safe metadata probe, its output, and a short crash/disassembly excerpt available. Full cores and user session transcripts are excluded.
Recurrence later the same day
After the cache-only recovery, it was overwritten again at 19:10:50 CDT with 121 version-12 files and the 363 aliases. ChatGPT startup was recorded at 19:10:51.289265 CDT. KWrite and System Monitor then crashed at 19:11:56 and 19:12:06 with the same Fontconfig/Qt stack. A second native cache rebuild restored both applications. This is a second startup/cache timestamp correlation, still without a syscall trace identifying the writer.
A per-user launcher workaround was installed and activated: launch ChatGPT with
XDG_CACHE_HOME=$HOME/.cache/chatgpt-isolated. The configuration/profile location remains unchanged.Successful isolation test after restarting ChatGPT
Before restarting the app, both normal and private cache directories contained 121 native version-9 files. After restarting ChatGPT with the isolated-cache launcher, a check at 19:46:19 CDT found:
$HOME/.cache/fontconfig: still 121 regular version-9 files, all headers matching, last changed at 19:14:53.$HOME/.cache/chatgpt-isolated/fontconfig: 121 version-12 files and 363 version-9/10/11 aliases, last changed at 19:42:56.kde-font-cache-bug-report-2026-09-30.zip
The problematic cache layout followed the application's redirected cache location while the normal desktop cache stayed intact. This strongly identifies the ChatGPT runtime as the trigger, beyond the earlier startup timestamp correlations. A syscall trace identifying the exact internal writer has not been captured.
Please see the attached
post-restart-cache-check.txtand incident report. This is a verified local workaround; it is not a claim that the installed application build has received a vendor fix.HYLi360 commentedon Oct 6, 2026
The latest Chrome Stable can generate font cache with .cache-12, Codex Desktop can use these cache directly, so has no chance to make synlink. :)
yuzhu-oai commentedon Oct 7, 2026
Fixes have been merged and will be released soon.
Gpiovesana commentedon Oct 12, 2026
Additional Linux findings: Sharp/libvips fontconfig cache and MCP child environment
Environment: Zorin OS 18.1, host Fontconfig 2.15.0, ChatGPT/Codex Desktop 26.1007.21434.
This report was prepared with assistance from Codex Desktop, which performed local diagnostic tests, and ChatGPT, which helped review the findings and draft this comment.
Observed crashes. Kdenlive 26.08.1 crashed with SIGSEGV in its bundled libfontconfig, with a GDB stack including
FcCharSetHasChar()during Qt text rendering. PCSX2 2.8.2 also crashed upon opening settings (initial SIGSEGV followed by application SIGABRT); the original PCSX2 faulting function was not symbolized. Regenerating the host fontconfig cache restored operation on three occasions.Controlled Sharp/libvips test. The library shipped with Desktop (libvips 8.18.6), executed with an isolated temporary cache, generated 92
cache-12files and 276 compatibility symlinks (cache-9/10/11pointing tocache-12). All symlink names and targets and all 92 cache filenames matched a preserved problematic backup; 79 of the 92 cache files were byte-for-byte identical.straceconfirmed symlink creation. The host cache was unchanged. This demonstrates the bundled dependency can produce the observed layout, but does not establish which process wrote the historical files.Partial mitigation. A per-user desktop launcher now sets
XDG_CACHE_HOME=$HOME/.cache/chatgpt-isolado. After relaunch, the Codex app-server and exec-server inherited the value. The private directory containscache-12files, while the shared~/.cache/fontconfigretained the same 93 entries, timestamps, metadata and SHA-256 hashes during the observed session. No new crashes were observed.Remaining concern. Four
node_replMCP auxiliary processes, spawned directly by app-server or throughcua-repl.mjs, did not receiveXDG_CACHE_HOME. Their environment was reduced (19–24 variables, versus 77 for app-server). They retainHOME, can access the bundled Sharp/libvips modules, and have permission to write to the shared cache. No such write by these processes has been observed. The MCP stdio environment logic uses a reduced default set plus explicitenv_vars/enventries; Desktop-generated MCP configurations did not forwardXDG_CACHE_HOME. See also #42454 and #21713.Could maintainers clarify:
node_replandcua_replMCP auxiliary processes?XDG_CACHE_HOMEbe preserved in their reduced environment, or could users receive a documented persistent override for Desktop-managed MCP configuration?The private launcher mitigated the observed startup behavior, but full isolation of MCP children remains unverified.
yuzhu-oai commentedon Oct 13, 2026
Thanks for the detailed follow-up. We checked the packaging: 26.1007.21434 includes part of the fix, but still bundles the older sharp 0.35.4 with libvips 8.18.6 that can cause this problem. Your results are therefore consistent with the known issue.
The remaining fix has merged but still needs to ship in the Linux release.