I'm on the new Kubuntu Beta 1. When I go to system settings / Fonts and try to add/remove a font (TTF) I'm asked for authentication. I enter my password. Afterwards a dialog is shown: "Font setup is updated. Please wait..." (actual text in German). The bar immediately shows "100%" and that's it. Nothing happens. The dialog never closes. Reproducible: Always Steps to Reproduce: 1. Open "System Settings" 2. Go to Fonts, Font Management (German version, actual names might be slightly different) 3. Click on "add", Select a TTF file 4. When asked, select to install as "system font" 5. When asked, enter password 6. Wait... and wait a bit... and wait even more :-( Actual Results: Wait dialog box never closes Expected Results: The dialog box should close after some time
also happens in fedora22 / kde 5.10.0, if it does not crash beforehand ('...error happend in the backend...')
I can confirm this here too, on openSUSE 13.2 with KF 5.11 and Plasma 5.3.2. Some more details: - it works fine if you install as "Personal Font". - even though the dialog hangs, the font actually does get installed successfully. - it also happens when running kfontinst manually in Konsole. - you cannot even cancel the dialog, you have to kill systemsettings5 or kfontinst.
I can also confirm this problem. Furthermore, by trying to add several fonts at the same time in System Settings' Font Management, I am able to force out the error message that I suspect is responsible here: [img]http://i.imgur.com/bVplyaY.png[/img] It seems the backend dies while waiting for the root password, which again leaves the Font Installer dialog hanging.
I can also confirm it on ArchLinux with plasma 5.3.2
(In reply to Tore Havn from comment #3) > Furthermore, by trying to add several fonts at the same time in System Settings' Font Management, I am able to force out the error message that I suspect is responsible here: Right, I can reproduce this too. The first of the fonts does get installed though before the error message occurs. The question though is, whether this is related to the original bug or it's a different one... > It seems the backend dies while waiting for the root password, which again > leaves the Font Installer dialog hanging. It's not dying when waiting for the root password here. It does ask for the password, then installs the first font, and then crashes.
*** Bug 352017 has been marked as a duplicate of this bug. ***
*** Bug 349673 has been marked as a duplicate of this bug. ***
*** Bug 353115 has been marked as a duplicate of this bug. ***
Git commit 7ebe57aa74cd99ff81c4d0be9f1423a47b94d64b by David Edmundson. Committed on 26/10/2015 at 22:32. Pushed by davidedmundson into branch 'Plasma/5.4'. Port KAuth return code error checking in fontinst Someone whilst porting had simply commented it out This causes the install dialog to freeze if there's a problem. Related: bug 344473, bug 300951 REVIEW: 125555 M +16 -15 kcms/kfontinst/dbus/FontInst.cpp http://commits.kde.org/plasma-desktop/7ebe57aa74cd99ff81c4d0be9f1423a47b94d64b
Git commit 335ad976ac9f11cd51a838a7ae7dcb38d948bfcf by David Edmundson. Committed on 29/10/2015 at 14:22. Pushed by davidedmundson into branch 'master'. Wait for async call starting helper to finish before checking the reply Otherwise the check is effectively useless. This meant in the case where the helper could not be started the job would never finish and clients would stuck idle or blocked. Related: bug 344473, bug 300951 REVIEW: 125859 M +15 -7 src/backends/dbus/DBusHelperProxy.cpp http://commits.kde.org/kauth/335ad976ac9f11cd51a838a7ae7dcb38d948bfcf
Today I've tried to install a font. Looks like bug still exist in version 5.5.2 so this bug needs to be reopened.
(In reply to Ongun Kanat from comment #11) > Today I've tried to install a font. Looks like bug still exist in version > 5.5.2 so this bug needs to be reopened. And what version of KDE Frameworks are you using? One part of the fix is in KAuth IIUIC. The issue doesn't occur here any more (with Plasma 5.5.2 and Frameworks 5.17.0).
I'm using Plasma 5.5.2 & Frameworks 5.17.0 Arch Linux packages. The font files I tried to install are here: https://www.dropbox.com/s/f8ykprsywtpx5ec/caviar_dreams.zip?dl=0
I still have the issue. KAuth 5.17.0-1 package of ArchLinux have been already installed on my pc. Did you tried instaling fonts with the System option after the commit went upstream (I know it's a silly question though), since installing with Personal option works but System option causes dialog wait forever. I removed the configs releated to kcmfontinst in the folder ~/.config ,hoping it might fix things, but I couldn't achieve further improvements.
(In reply to Ongun Kanat from comment #14) > Did you tried instaling fonts with the System > option after the commit went upstream Yes. The "Personal" option does not need root privileges and never had this problem (as I mentioned myself in comment#5). Maybe it's a more general problem with kauth in your case. Do other actions work that require root privileges, like e.g. changing the system time/date? Do you get a root password dialog at all? If not, check that it's not hidden behind another window e.g. (even kfontinstall's progress dialog) As long as you don't enter the root password, kfontinstall obviously will not continue (although it actually times out after a while here).
Confirm still a problem on Kubuntu 15.10 - fully up-to-date. Two separate computers. Attempt to install 2 of more fonts systemwide - asks for sudo and then crashes on the second font. 1. Add 2. Select two TTF files 3. "Do you wish to install the font(s) for personal use (only available to you), or system-wide (available to all users)?" - select SYSTEM 4. "Modifying the system-wide font configuration requires privileges." - enter password and OK 5. "Error Backend died, but has been restarted. Please try again." observed - first font in selection has been expected - no error message at (5) and all fonts installed at once. This bug reported 2015-03 but I'm pretty sure it was going on years before that. (I don't install fonts very often). Since commit was to Plasma 5.4, then seems iike that it will be solved in Kubuntu 16.04 (which ships Plasma 5.5) . Here's hoping.
(In reply to Walter Nicholls from comment #16) > Since commit was to Plasma 5.4, then seems iike that it will be solved in > Kubuntu 16.04 (which ships Plasma 5.5) . Here's hoping. This bug report was about the progress dialog being shown forever (and systemsettings5 being completely frozen) in the KF5 version, even when only installing *one* font. And this should be fixed in 5.4 and up. The problem you describe with multiple fonts is still reproduceable here with 5.6.2. But it's probably a completely different bug and should be reported separately.
Christoph Feck marked bug 349673 as a dupe of this one, and I just accepted it, but indeed the description doesn't match up. I should have read more closely than just accepting. Reposting on that other bug , although I don't have the rights to mark it as "unresolved".
(In reply to Walter Nicholls from comment #18) > Christoph Feck marked bug 349673 as a dupe of this one Thanks for point to that bug report, I wasn't aware of that one. I've added a comment and reopened it.
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 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 ..
I can confirm it's still a problem with Kubuntu 16.04 and KDE 5.6.5. The font seems to get installed even though the dialog hangs.
(In reply to Joe Dai from comment #22) > I can confirm it's still a problem with Kubuntu 16.04 and KDE 5.6.5. The > font seems to get installed even though the dialog hangs. It works fine here, as long as I install only one font. And this bug report is closed, further comments are useless. There are other similar bug reports that are still open though: E.g.: bug#349673 bug#361960 bug#364493 (In reply to orbayo from comment #20) > 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 is now useless. This doesn't sound related at all though.
(In reply to Wolfgang Bauer from comment #23) > (In reply to Joe Dai from comment #22) > > I can confirm it's still a problem with Kubuntu 16.04 and KDE 5.6.5. The > > font seems to get installed even though the dialog hangs. > > It works fine here, as long as I install only one font. > > And this bug report is closed, further comments are useless. > > There are other similar bug reports that are still open though: > E.g.: > bug#349673 > bug#361960 > bug#364493 > > (In reply to orbayo from comment #20) > > 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 is now useless. > > This doesn't sound related at all though. Thank you. Do I open a new thread explaining it better?
(In reply to orbayo from comment #24) > Thank you. > Do I open a new thread explaining it better? Depends. If an existing (open) bug report matches your problem, there's no need to file a new one. OTOH, if I understand you correctly, your problem also occurs if you copy your font to /usr/share/fonts/ manually. This is definitely not a problem of KDE's font installer then, as it is not even involved. And actually it might not even be related to KDE at all.
The same problem happens when you install fonts in ubuntu (unity), linux mint 18 KDE and also linux mint 18 MATE, then the problem does not seem to be KDf 5. I think the problem is the kernel, versions 4 or higher . With openSUSE and a v3 kernel, it never happened to me.
(In reply to orbayo from comment #26) > The same problem happens when you install fonts in ubuntu (unity), linux > mint 18 KDE and also linux mint 18 MATE, then the problem does not seem to > be KDf 5. I think the problem is the kernel, versions 4 or higher . With > openSUSE and a v3 kernel, it never happened to me. No, this is definitely not related to the kernel. That it never happened to you in openSUSE is likely because you were using KDE4 then. And the current problems are tracked in other bug reports anyway, see comment#23.
Community.. I have installed many types of fonts, about 1200, and I have been testing. I can say that the biggest problem is in one of the truetype font types .ttc