If Plasma started crashing after a Kubuntu 26.04 update, check the crash trace before changing font caches. Reports point to several possible fontconfig-related triggers—including fonts-katex, a proposed cache-regeneration race, and a possible Chrome 154 association—but they do not establish one universal cause or an official fix. Match the evidence on your system to the remedy before applying it.
What the reports show—and what they do not
Kubuntu 26.04 ships with Plasma 6.6, Qt 6.10.2, KDE Frameworks 6.24.0, and Linux kernel 7.0; Plasma Wayland is the default supported session. Those are release-note versions, not a guarantee that every updated system still has those exact package versions. Check your installed versions when comparing your machine with an incident report. Kubuntu 26.04 release notes
Three distinct reports describe crashes involving FcCharSetHasChar, a function in fontconfig. That shared stack-trace clue is useful, but it does not prove the reports have the same root cause. An Ubuntu bug report describes unexpected font matching when fonts-katex is installed; a separate author proposes that Plasma reads a font cache while another process regenerates it; and Chrome 154 has been associated with crashes in a Chromium issue extract and community discussion. Treat each as a lead to test, not a diagnosis of every Plasma crash.
fonts-katex and unexpected font matching
An Ubuntu bug report filed on September 23, 2026 describes two Kubuntu 26.04 installations where plasmashell crashed repeatedly. The report records Plasma 6.6.6, Qt 6.10.2, fontconfig 2.17.1, and kernel 7.0.0-34 on those machines. Its author says fonts-katex was installed and that fc-match sans selected a KaTeX WOFF font. Those details describe the reporter’s two systems; they do not show that the package causes crashes generally. Ubuntu bug report
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match#1 Best Overall
- Chipset: NVIDIA GeForce GT 1030
- Video Memory: 4GB DDR4
- Boost Clock: 1430 MHz
- Memory Interface: 64-bit
- Output: DisplayPort x 1 (v1.4a) / HDMI 2.0b x 1
A proposed cache-regeneration race
A Kubuntu user article describes a login-time race in which Plasma allegedly reads a font cache while another process regenerates it. The author reports seeing a crash in FcCharSetHasChar and says a systemd startup-order workaround worked on their Kubuntu 26.04 setup with Plasma 6.6.6 and kernel 7.0.0-34. This is an individual troubleshooting account, not an official Kubuntu finding. The author also cautions that the workaround is not relevant when the trace does not mention fontconfig. Author’s cache-race account
A possible Chrome 154 association
A Chromium issue search extract associates crashes on Ubuntu 26.04 after running Chrome 154 with segmentation faults in FcCharSetHasChar. The issue page was not available in the record summarized here, and KDE community discussion raises Chrome or Brave as a possible factor without establishing a broad browser-related cause. Record your browser version and whether you ran it before the first crash; do not assume all Chromium-based browsers are affected. Chromium issue search for FcCharSetHasChar KDE community discussion
Rank #2
- Robust 4GB Memory & Quad Display Ready: Equipped with 4GB of fast GDDR5 memory to smoothly handle daily graphics tasks. Features four built-in HDMI ports, enabling a seamless quad-monitor setup directly out of the box—perfect for multi-tasking offices, digital signage, or trading desks.
- Plug-and-Play Installation & Wide Compatibility: Utilizes a standard PCI Express interface for broad compatibility with most desktop PCs. Offers straightforward plug-and-play installation and stable driver support for modern Windows and Linux operating systems, ensuring a hassle-free setup.
- Quiet, Cool & Compact Design: Engineered with a silent fan and efficient cooling system for near-silent operation, making it ideal for noise-sensitive environments. Its low-profile design fits easily into small form factor cases, with both half-height and full-height brackets included for flexible installation.
- Enhanced Multimedia & Everyday Performance: Delivers smooth 1080P video playback and supports hardware-accelerated decoding, offering an excellent experience for home theater PCs (HTPC). Provides capable performance for everyday applications, multimedia tasks.
- Complete Package & Reliable Support: Includes the graphics card, both low-profile and standard brackets, a quick start guide, and screwdriver, which make it simple and quick setup process.
Diagnose the crash before trying a fix
First identify what is actually failing. A plasmashell crash, a screen-locker failure, and a theme or panel problem call for different investigations. Note whether you use Wayland or X11, which versions of Kubuntu, Plasma, Qt, and the kernel are installed, and what changed just before the first failure: a system update, a font package, or a browser update or first launch.
- List recent crash dumps: run
coredumpctl list --since today --no-pager. Look for entries that correspond to the time of the failure. - Inspect the Plasma shell dump: run
coredumpctl info plasmashell --no-pager. Check whether the backtrace includesFcCharSetHasCharor other fontconfig frames. The command may not show a useful dump if no matching core was recorded. - Check user-session warnings: run
journalctl --user -b --no-pager -p warning. Use the timestamp and process names to correlate warnings with the crash. - Check the package and font match if fontconfig appears relevant: use
dpkg -s fonts-katexto see whether the package is installed, then runfc-match sansand, if needed,fc-match -v sansto inspect the selected font. These commands show package state and font matching; neither proves causality by itself. - Record browser context: note the installed Chrome or Brave version and whether that browser ran before the crash began.
If the backtrace points to a different library or process, investigate that component rather than deleting font caches. Exact log and core-dump output varies by machine, so use timestamps and the failing process to connect entries instead of relying on a particular line of output.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Rank #3
- Powered by NVIDIA GeForce GT 730, 28nm GK208 chipset process with 902MHz core frequency, integrated with 4096MB DDR3 memory and 64-bit bus width
- More stable performance, compatible with Win11, can automatically install new driver
- Support NVIDIA Surround technology for 4 screens output by dual HDMI and VGA / DP. HDMI Max Resolution-2560x1600, VGA Max Resolution-2048x1536, DP Max Resolution-2560x1600
- Support DirectX 12, OpenGL 4.6, CUDA, OpenCL, DirectCompute and DirectML
- Original half height bracket matches with the low profile brackets make the Glorto GeForce GT 730 graphics card fit well with all PC tower, small form factor and HTPC(except micro form factor)
Choose a remedy only when the evidence matches
If the fonts-katex report matches your system
The Ubuntu reporter says their workaround was to remove fonts-katex, clear both system and user fontconfig cache contents, and rebuild the system cache:
sudo apt purge fonts-katex
sudo rm -rf /var/cache/fontconfig/*
rm -rf ~/.cache/fontconfig
sudo fc-cache -fThis is a reporter’s workaround for two machines, not an official or universal instruction. Purging removes installed software, and clearing caches affects system and user font configuration. Consider it only if the package is present and the font-matching and crash evidence resembles the report. The reporter says clearing only the user cache fixed one login, but the crash returned; on the two reported systems, clearing the system cache as well was needed. Ubuntu bug report and workaround
Rank #4
- Powered by NVIDIA GeForce GT 610, 40nm chipset process with 523MHz core frequency, integrated with 2048MB DDR3 memory and 64-bit bus width
- Compatible with windows 11 system, no need to download driver manually
- HDMI / VGA 2 ports output available. HDMI Max Resolution-2560x1600, VGA Max Resolution-2048x1536
- Support DirectX 11, OpenCL, CUDA, DirectCompute 5.0
- Original half height bracket matches with the low profile brackets make the Glorto GeForce GT 610 graphics card fit well with all PC tower, small form factor and HTPC(except micro form factor)
If the trace supports the proposed cache-race scenario
The author describes a temporary recovery sequence that clears user and system font caches, rebuilds them, resets a failed user service, and restarts Plasma. The account then proposes a user-level systemd drop-in to run fc-cache before the Plasma shell service starts. Because this changes service startup behavior and is based on one author’s system, do not apply it solely because Plasma crashes after an update. Read the author’s complete procedure and verify the fontconfig frames first. The article reports that its drop-in persisted across reboots and updates in that author’s environment, but that is not a guarantee for other installations. Full cache-race workaround and service drop-in
If you add the author’s user-level drop-in and it causes problems, remove the drop-in file you created and reload the user systemd manager before restarting the session. Follow the article’s exact unit and file names; they are specific to its proposed workaround.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
If Chrome 154 may be involved
Record the version and test whether the timing matches: did the first crash follow running Chrome 154? KDE discussion suggests temporarily avoiding Chrome while investigating, but the available reports do not verify an official Chromium or Ubuntu resolution. Do not generalize the association to every browser based on a shared engine, and do not delete arbitrary browser or system cache directories as a blanket fix. Chromium issue search KDE discussion
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When the problem is a theme or layout, not a crash
Kubuntu’s release notes separately warn that upgraders may encounter theme, panel, layout, or widget problems after the Plasma 6.6, Qt 6.10, and Frameworks changes. For those configuration symptoms, the release notes suggest reapplying the global theme first; resetting ~/.config is described as a last resort after making a backup. That advice concerns upgrade-related appearance and configuration issues, not a fontconfig crash, so do not substitute it for crash diagnosis. Kubuntu 26.04 release notes
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
