| 19 Mar 2026 |
|  Miles Dyson set a profile picture. | 18:06:43 |
 πΌπ. π±ππ πππ π π·ππ | looks like some characters are from emoji font | 21:07:39 |
 eliasp | using NeoChat as Flatpak - just dug through ~/.var/app/org.kde.neochat but found nothing font/look&feel related at allβ¦
maybe something changed due to an update in the underlying KDE runtime? but then again, other Kirigami applications like Marknote (via Flatpak as well) look just fine π€· | 21:10:23 |
| eliasp | I'll give NeoChat from nixpkgs a try to see, whether it's also affected | 21:10:46 |
| 20 Mar 2026 |
 Khalil Santana | Hi, various applications but overwhelmingly GTK-based stuff seems to display all fonts empty squares/rectangles. This happens on Libreoffice and Virt-manager for example. My desktop environment is plasma 6 wayland | 05:46:49 |
| Khalil Santana | 
Download Captura_de_tela_20260320_025310.png | 05:54:51 |
| Khalil Santana | Oh, figured out the "solution" -> nuking ~/.cache/fontconfig =p | 05:57:01 |
| Khalil Santana | fc-cache -rf did not work though | 05:57:17 |
| Khalil Santana | Probably related to whatever caused libreoffice to break a few weeks ago, and the weird font issues around the same time in KDE too | 05:57:50 |
| 23 Mar 2026 |
 K900 | Trying to build Qt 6.11 | 13:12:44 |
| K900 | pyside changed a lot :( | 13:15:12 |
| K900 | Ooooffff | 13:23:40 |
| K900 | We might have to go with a monolithic build for pyside now... | 13:23:49 |
| K900 | OK never mind | 14:12:41 |
| K900 | It does build separately | 14:12:43 |
| K900 | Just Weird | 14:12:45 |
| K900 | OK booting entire system on 6.11 | 17:52:19 |
| K900 | Let's see how many things are on fire | 17:52:23 |
| K900 | OK uhhh | 17:55:58 |
| K900 | None? | 17:55:59 |
| K900 | That's cool | 17:56:04 |
| eliasp | Does anyone have further information on this issue? Since I'd prefer finding a universal fix for this and not having everyone run into the same issue which then requires either a lot of luck or persistence to find this specific "solution" to the problem. | 22:48:05 |
| 24 Mar 2026 |
| Khalil Santana | Best hope would be testing commits from, say, January in nixos-unstable. Starting it up with a clean cache, then opening an affected app like virt-manager. Then bump the flake version to the current and re-use the initial cache. If it reproduces the issues then this is bissectable. If it doesn't show up then it is somewhere in between then and now but may or may not require "carrying forwards" the cache from the first january version to now. | 00:39:06 |
| Khalil Santana | I have never fiddled with nixos tests or the VM framework it has, but presumably that has enough of a harness that it could be less tedius | 00:40:09 |
| Khalil Santana | Like a mini VM with just plasma, autologin for convinience, auto-open virt-manager take a screenshot and ping the user about it so they can y/N the bissect. Or some kind of vision harness | 00:42:08 |
| Khalil Santana | * | 00:43:11 |
| K900 | Woo Krita 6.0.0 stable | 11:56:48 |
| K900 | Time to delete another like half of KF5 | 11:56:57 |
| K900 | CMake Error at CMakeLists.txt:366 (message):
Building Krita with Qt6 is not yet production-ready. Please don't package
this and ship it as a stable version of the software.
If you want to continue regardless, pass:
-DALLOW_UNSTABLE=QT6
| 12:34:02 |
| K900 | Sigh | 12:34:02 |
