| Summary: | kfontinst freezes adding fonts to system | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Enol P. <enolp> |
| Component: | kcm_fontinst | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | arcooke, carlosab85, decedion, koloberdin, mark.pearson0, psychonaut |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/plasma-desktop/690570a4cefd786db5113ca237e9bdb48cd50812 | Version Fixed In: | |
| Sentry Crash Report: | |||
|
Description
Enol P.
2016-04-19 11:10:38 UTC
Are you still seeing this issue? It could be a duplicate of bug 345234, which has since been fixed. (In reply to Christoph Feck from comment #1) > Are you still seeing this issue? It could be a duplicate of bug 345234, > which has since been fixed. This issue still persists, i have just checked it I am seeing the same problem on Kubuntu 16.04 exactly as described in the initial bug report Install new fonts makes very slow system, as root (make system useless) or as a user. Making a manual installation or with system settings. KDE 5 BUG. I copied my folder with my collection of type fonts on the route /usr/share/fonts/personalfonts Now the whole system is super slow, my opensuse 42.1 KDE 5.5 is now useless. I tried to do it with systemsettings5 and the same problem. If you install the fonts only for a single user the laggy is less. And the same problem with Linux Mint KDE 18. if you add new fonts you lose the system, I need the fonts to work . If you delete the installed fonts you recover the system speed. I am experiencing the same issue. ("Updating font configuration. Please wait..." dialog hangs forever and can't be closed)
This happens when I try to install or delete a font system wide.
Arch Linux, plasma 5.8.4.
I played with it a little bit more. This bug does not occur every time. Sometimes it does, sometimes it does not. Possible duplicates: Bug 357337 (possibly filed to the wrong product/component), Bug 371772 As a workaround, you can use kdesu (or su -) to launch kfontinst from the command line, passing as arguments the filenames of the fonts you want to install: $ kdesu kfontinst somefont.otf *** Bug 371772 has been marked as a duplicate of this bug. *** *** Bug 357337 has been marked as a duplicate of this bug. *** I can confirm that: 1) The problem still exists with Plasma 5.12.5 2) The problem occurs not just for installing fonts, but also uninstalling fonts 3) The workaround I posted in Comment #8 works only for installing fonts, not for uninstalling fonts. (It seems there is no command-line tool for uninstalling fonts.) Git commit 60c895758f20bd2cb17ab12e57cf34cc37197098 by Mathias Tillman. Committed on 31/07/2018 at 10:40. Pushed by mathiastillman into branch 'master'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379524, bug 379324, bug 349673, bug 392267 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 M +4 -0 kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/60c895758f20bd2cb17ab12e57cf34cc37197098 Git commit 690570a4cefd786db5113ca237e9bdb48cd50812 by Mathias Tillman. Committed on 02/08/2018 at 07:33. Pushed by mathiastillman into branch 'Plasma/5.12'. fontinst quits after KJob is done Summary: As the summary says, when installing/removing multiple fonts to system the expected behaviour would be for fontinst to keep running after the first font has been installed or removed, instead it quits which causes a bunch of issues. fontinst uses KJob to authorize and internally KJob uses a QEventLoopLocker which causes the main event loop to quit when it's done. I'm not entirely sure why the event loop locker is enabled by default for KJob, but the patch I have attached works around this by completely disabling that functionality for fontinst. There's a timer that runs in the background which checks for any connected clients, so it will quit after a little while regardless. Related: bug 379524, bug 379324, bug 349673, bug 392267 Test Plan: Make sure fonts are still installed and removed properly. Reviewers: #plasma, dfaure, aacid, gateau Reviewed By: dfaure Subscribers: wbauer, ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D14493 (cherry picked from commit 60c895758f20bd2cb17ab12e57cf34cc37197098) M +4 -0 kcms/kfontinst/dbus/Main.cpp https://commits.kde.org/plasma-desktop/690570a4cefd786db5113ca237e9bdb48cd50812 |