Installing font seemingly never finishes

Hi,

I downloaded a zip file containing a font in OTF format. I opened the zip, clicked on the OTF and got a dialog that offered to install the font. I clicked on install and a progress bar reached 100% after a short while, but never “finished”. Eventually I closed the dialog.
The good part is, that the font apparently was installed successfully and I can now select it and use it.

Is this related to OpenSUSE or the Desktop I am using (Plasma 5.3)?

And what is the openSUSE version?

openSUSE 13.2

Is it repeatable? ie install another font the same way and get the same result?? if so maybe a bugzilla post is in order. Plasma5 is still very much a work in progress.

AIUI, this is not related to the desktop at all. Plasma5 itself does not install any fonts.

How exactly do you open the zip file? Where did you click on the OTF file?
How does the install dialog look like?

Also, if it is KDE’s kfontview (which is actually part of the plasma5-desktop package), do you install it as “Personal Font” or as “System Font”? Might make a difference…

Well no put it may provide the prompts and show the progress

It doesn’t, except the application that installs the font would explicitely ask it to (like a file copy progress notification e.g.).

And that’s why it might help if the OP would show a screenshot of the progress dialog that he means.

PS: I just tried to install an OTF font with Plasma5’s kfontview as personal font here and saw no problem whatsoever, and this also doesn’t use any Plasma notifications.

On 2015-06-22 14:16, gogalthorp wrote:
>
> Is it repeatable? ie install another font the same way and get the same
> result?? if so maybe a bugzilla post is in order. Plasma5 is still very
> much a work in progress.

There is a report (bug) with expanding zip archives in tw, and I
understand, would also affect plasma 5 in 13.2. There is a thread
somewhere in the beta forum about this, IIRC.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

I remember choosing to install it as a system font. Unfortunately I don’t have access to the machine at the moment, so I cannot make a screenshot.

I clicked on the zip in dolphin, which probably opened ark. From there I clicked on the OTF, but I don’t know what the program is called that opens this font by default. I think it was trying to show a preview of the font, but I only saw empty lines.

Ok, if you got that question, you probably did use kfontview.
Have you been asked for the root password?

Where did you install Plasma 5.3 from? 13.2 only has 5.2.2.
If you used my repo, installing fonts as system fonts doesn’t work at the moment, as it uses the KDE4 version of the KAuth helper by mistake (to gain root privileges) which just hangs.

I am fixing this right now. (Haven’t noticed that problem before as it worked fine in the systemsettings5 module, and nobody reported a problem either)

But if that is your problem, it should actually hang at 50% and never install anything at all.

I clicked on the zip in dolphin, which probably opened ark. From there I clicked on the OTF, but I don’t know what the program is called that opens this font by default. I think it was trying to show a preview of the font, but I only saw empty lines.

You should maybe try to extract it first then, and that’s meant in general. There might be a problem with the temporary files that get created when you open files inside an archive directly in Ark (e.g. they might get deleted too soon, or necessary files might be missing).

You mixed something up.

Extracting files from RARarchives doesn’t work with unrar5 at the moment if the destination file already exists, ark would just hang in that case. That’s a problem in Ark (cause by a change of the output in unrar) which is only available as KDE4 version at the moment, and not at all related to Plasma5.

ZIP files should work fine though.

On 2015-06-22 15:56, wolfi323 wrote:

> You mixed something up.
>
> Extracting files from RARarchives doesn’t work with unrar5 at the
> moment if the destination file already exists, ark would just hang in
> that case. That’s a problem in Ark (which is only available as KDE4
> version at the moment), and not at all related to Plasma5.
>
> ZIP files should work fine though.

Oops :slight_smile:


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

I installed Plasma 5.3 from http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_13.2/. I got the url from this page SDB:KDE repositories - openSUSE Wiki.
Is this a bug with Ark or intended that way?

So you didn’t add my repo (home:wolfi323:branches:KDE:Frameworks5), right?
That would exclude this particular problem…

Ok, but did you add KDE:Qt5 too? That’s what KF5 builds against, not having that can cause weird problems.

And to avoid other weird problems because of mixed versions, please run something like this:

sudo zypper dup --from *KF5* --from *Qt5*

where you should replace “KF5” and “Qt5” with the actual names or numbers of your repos (“zypper lr” should tell you).

Is this a bug with Ark or intended that way?

What do you mean now? The problem with RAR archives?
That’s a bug, or rather an incompatibility with newer unrar versions, as they made a change there. Should get fixed in the August release.
See here for more details: Extract compressed file function not working anymore in kde5 (plasma 5) in tumbleweed. - Install/Boot/Login - openSUSE Forums

If you mean the thing I mentioned with temporary files, that was just a guess, and might not be the problem at all.

So, have you tried to uncompress the archive first?
Does installing as “Personal Font” work?

Yes, I have the Qt5 one as well, but I have not added the wolfi repository.
What should I expect from dup? When I originally added the two repositories I clicked on “Switch system packages…” in YaST, because I had problems with this in the past that don’t appear this way.
I just looked up this page SDB:Vendor change update - openSUSE Wiki and it sounds as if zypper dup and “Switch system packages…” do the same thing, right?

Actually I have not tried installing the font again, because apparently the installation was successful in the first place. I just unzipped the font and opened it with kfontview. Again I don’t see any actual preview but this time the install button is disabled, so maybe it is detecting the previous installation.

Ok, then you shouldn’t be affected by this particular problem.

What should I expect from dup? When I originally added the two repositories I clicked on “Switch system packages…” in YaST, because I had problems with this in the past that don’t appear this way.
I just looked up this page SDB:Vendor change update - openSUSE Wiki and it sounds as if zypper dup and “Switch system packages…” do the same thing, right?

Yes.
You should be fine then regarding this.

Actually I have not tried installing the font again, because apparently the installation was successful in the first place. I just unzipped the font and opened it with kfontview. Again I don’t see any actual preview but this time the install button is disabled, so maybe it is detecting the previous installation.

Yeah, I noticed the same as well with the install button disabled. And it even did not get enabled for other fonts either.
I had to logout and login again.
Might be related here to the problem I mentioned, maybe not. I haven’t investigated further yet

But has the installation succeeded now for you?
And was this as “Personal Font” or “System Font” now?
The former works fine here, as mentioned. Haven’t tried the latter yet, as it doesn’t work here anyway with my packages installed (tomorrow maybe… :wink: ).

Well, the font is available on my system now, so the installation apparently was a success, although I just closed the install dialog after 100 % never went away. I selected system font.

Ok, but that doesn’t help in investigating the (possible) problem.

Can you try with another font, please? Maybe installing it as “User Font”?
Or with the same font after removing it. It should be somewhere below /usr/share/fonts/. Just delete it.

Otherwise, I would just “close” this thread as unreproducible.
As you please… :wink:

I will give it a try this evening.
Is copying (or deleting) the font to /usr/share/fonts/ all that happens during installation? I’m curious how the desktop environment (or is it on a deeper level?) gets to know about the font.

Not really necessary any more, I can reproduce the problem you describe.
Installing as “Personal Font” works fine as mentioned, but installing as “System Font” hangs as you wrote.

Seems to be a bug in kfontinst then, it doesn’t seem to notice that the actual install process (running as root) finished…

Is copying (or deleting) the font to /usr/share/fonts/ all that happens during installation?

Basically yes.
And personal fonts are copied to ~/.fonts/.

I’m curious how the desktop environment (or is it on a deeper level?) gets to know about the font.

Well, this is handled by the package/library fontconfig, which is used by most desktop environments/applications AFAIK.
See “man fonts-conf” for more information if you are interested… :wink: