Ubuntu

font viewer returns "failed" on installing of already existing font instead of "already installed" or something

Reported by Sergey "Shnatsel" Davidoff on 2009-08-25
48
This bug affects 10 people
Affects Status Importance Assigned to Milestone
gnome-font-viewer (Ubuntu)
Low
Unassigned

Bug Description

When I open a font, Font Viewer shows an active button "Install Font", no matter is it already installed or not. If I click the button and the font is already installed, the button changes to "Install Failed". This seems confusing. It's better to check if the font is already installed right after loading preview and offer installation only if the font isn't installed.

arky (arky) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in gnome-control-center.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → gnome-control-center (Ubuntu)
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, what ubuntu version do you use? Could you take a screenshot showing the issue?

Changed in gnome-control-center (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Incomplete

Yes, it isn't fixed till now. I've captured screen video, you may see it
here:
http://www.mediafire.com/?sharekey=3ed8d2ff2904560e0c814df2efeadc50e04e75f6e8ebb871

Jakob Hilden (jakobhilden) wrote :

This bug still seems to be not fixed. Is that correct?

That is correct. It's still not fixed as of Ubuntu Precise will all updates to this day.

affects: gnome-control-center (Ubuntu) → gnome-font-viewer (Ubuntu)
Changed in gnome-font-viewer (Ubuntu):
status: Incomplete → Confirmed
Adolfo Jayme (fitoschido) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in gnome-font-viewer (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
Zippo (zippoxer) wrote :

I'm experiencing the same too. I also noticed that there is no .fonts directory in my home. Maybe it's since I've never successfully installed a font.

Zisu Andrei (matzipan) wrote :

Still experiencing?

gerryk (gerryk) wrote :

Bug still exists on Font Viewer 3.6.0, Ubuntu 12.10

Changed in gnome-font-viewer (Ubuntu):
status: Confirmed → Triaged

I am experiencing this too but I have some further insight into the problem:

As mentioned, gnome-font-viewer fails to install a font if it is already installed. But it ONLY fails if the filename is the same.

In fact, the application fails to install if you try to install ANY font having the same filename as a previously-installed font!

It makes no attempt to determine whether the same font is actually installed. It just blindly copies the file to the ~/.fonts directory when you click "Install".

Steps to reproduce:
1. Clean out your ~/.fonts directory (or not, but might as well)
2. Use gnome-font-viewer to Install a font from a file, perhaps 'webfont.ttf'
3. Try to repeat step 2

Expected behavior:
It should check the (internal) font name, say "Arial". If "Arial" is already installed (from any filename), it should say so. If not, it should allow a user to install the font.

If the font really isn't installed yet, it should automatically rename conflicting files via a standard "append counter" sort of conflict resolution algorithm. That is, if a file called 'webfont.ttf' is already installed (but the enclosed font is not), the newly-installed font should be stored in 'webfont1.ttf', or 'webfont-2.ttf', or something along those lines.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers