https://bugs.kde.org/show_bug.cgi?id=525304
Krzysztof Łastowski <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|kcm_fontinst crashes (exit |fontinst exits with 255 |255) on D-Bus activation, |because Font Management |triggered by merely opening |starts it twice |the Fonts KCM; replaces |(startDetached plus D-Bus |symlinked fontconfig conf.d |activation) |files with plain copies as | |a side effect | --- Comment #9 from Krzysztof Łastowski <[email protected]> --- Measured cause of the exit 255, Plasma 6.8.1. It reproduces every time: open System Settings -> Font Management. The window does not crash; a redundant second fontinst instance exits. journal + `busctl --user monitor org.kde.fontinst`: 01:36:38.774171 systemsettings: Service org.kde.fontinst not registered, starting ".../libexec/fontinst" 01:36:38.774596 systemsettings calls org.kde.fontinst.list (auto-start allowed) 01:36:38.776442 systemd: Started dbus-:[email protected] 01:36:38.784844 :1.274 RequestName("org.kde.fontinst") -> acquired, serves the KCM 01:36:38.802167 :1.275 RequestName("org.kde.fontinst") -> NameLost 01:36:38.802996 dbus-:[email protected]: Main process exited, status=255/EXCEPTION CJobRunner::startDbusService() (kcmfontinst/JobRunner.cpp:74-81) starts fontinst with QProcess::startDetached(), and the next list() call also D-Bus-activates it. The instance that registers second hits ::exit(-1) in FontInst::FontInst(). So it is not a stale instance as I guessed in comment 6, and it is harmless apart from the failed unit. The symlink replacement I tied to this in the description is a separate issue, now in bug 525445 (kcm_fonts). Retitled accordingly. -- You are receiving this mail because: You are watching all bug changes.
