| Summary: | plasmashell: Fontconfig error: Cannot load default config file: No such file: (null) | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | vindicator <nroycea+kde> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.21.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
vindicator
2021-04-05 23:02:05 UTC
What log has this error in it? It was just the journal. Is there any other place that plasmashell may log to with more detail? Full disclosure, I had to rebuild my os partition because of a previous catastrophic failure to that partition, so I started over from scratch EXCEPT for my /home which was safe on a different drive. Also, when rebuilding, I got more selective with what I installed rather than just the entire "plasma" group, I'd narrow down to what was required (like plasma-desktop) and then added what was then needed for things that were not functioning like widgets needed ksysguard installed. Otherwise they were just blank. Plasma consists of so many different pieces scattered across repos that in my opinion doing that is a recipe for sadness and breakage that yo will be chasing down for months and months. It's best to bite the bullet and install the mesa-package/group/whatever provided by your distro. The packagers generally know what they're doing. :) Especially on Arch. They have great KDE packaging overall. Cannot reproduce FWIW. I get that, but can you tell me if it's "plasmashell" that is looking for a "default config file"? I'm going with the thought there is a kde/plasmashell config setting containing a key/name/variable that is currently empty or non-existent meant to be passed to fontconfig to do whatever magic it does. (eg. "~/.config/plasmashell_primary.config" containing/expecting "Fontconfig="). The reason this "bug" is open is because the error doesn't give me enough to go on to fix the issue because I don't know where to look. I see "plasmashell" making me think plasmashell looked up something it was expecting, which then passes it on to fontconfig a value that is "null". I guess a better/real example would be "plasmashellrc". That contains "[KTextEditor Renderer]" which contains "Font=<actual font>". If it just contained "Font=" or that key didn't exist, THEN I'd expect this type of error. But I'd also expect the error would tell me it was related to "[KTextEditor Renderer]" in "plasmashellrc". That would be descriptive enough for me to act on. Maybe this is something I should be tossing to the "fontconfig" folks, but I'm thinking this is the right place. I don't know, sorry. More likely the issue is in Qt rather than fontconfig, or caused by missing packages on your system. I'm not sure there's anything we can do here. At the time this bug report was submitted, your system was in a non-deterministic state and it's as likely that it was set up wrong as it is to have been affected by a bug somewhere. There isn't rally a way to know without the system itself being in a known good/clean/supported state. I'd recommend using a distro that isn't Arch, since it's geared for technical experts and people who want hyper-detailed control over every aspect of their systems. If you're more of an "I want it to just work" person, Arch is probably not the right distro for you. I'm going to close this bug report now, but if you manage to get your system into a supported state, such as reinstalling from scratch from a non-DIY distro--or if you've already done this--and you can still reproduce the issue, feel free to re-open the bug. If you still encounter it while using Arch, I would recommend that you ask for help in an Arch-specific forum first, as there isn't any indication of a bug in KDE code yet. |