"Go to Fonts Folder" button and fonts:/// URL scheme broken in Hardy

Bug #193897 reported by Jeremy Visser
102
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gvfs
Won't Fix
Medium
gvfs (Ubuntu)
Won't Fix
Wishlist
Ubuntu Desktop Bugs
nautilus (Ubuntu)
Invalid
Wishlist
Unassigned

Bug Description

Binary package hint: nautilus

I presume as a result of the new GVFS/GIO integration in Nautilus, the fonts:/// URL scheme is now broken.

In <= Gutsy, if you type fonts:/// in the location bar, you will be presented with all the fonts installed in the system. In Hardy, it simply complains that "Nautilus cannot handle fonts: locations".

This has the effect of breaking the "Go to Fonts Folder" in the Appearance control panel. Go to System → Preferences → Appearance → Fonts → Details, and click "Go to Fonts Folder". You will get the same error as if you typed "fonts:///" into a Nautilus window.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Not a nautilus bug, the fonts method has just not be rewritten for gvfs yet

Changed in nautilus:
importance: Undecided → Wishlist
status: New → Invalid
Changed in gnome-control-center:
assignee: nobody → desktop-bugs
importance: Undecided → Wishlist
status: New → Triaged
Changed in gvfs:
status: Unknown → New
Revision history for this message
Savvas Radevic (medigeek) wrote :

There is a backend waiting for a month or so:
http://bugzilla.gnome.org/show_bug.cgi?id=517632#c2

Can someone take a look at it?

Revision history for this message
Jon N. (jonnicc) wrote :

This is my workaround for installing my fonts:

Open your location with your fonts folder. If your fonts are not in a folder, put your TTF fonts into a folder with a special marking such as "MyBestFonts". make sure that the folder has no spaces, or has dashes separating the words. I chose no spaces.

Goto Places> Computer> Filesystem> usr> share> fonts

Drag the "MyBestFonts" folder into the fonts folder. Ubuntu should start to copy them over. It might ask you a question. If it says "cannot do this, you don't have permission", then copy the file to your Desktop, open your terminal and tyoe:

   cd Desktop
   sudo mv MyBestFonts /usr/share/fonts
Password for ? (Type in your password)

After a couple of seconds, your command line cursor should come back.

   Type:
   cd /usr/share/fonts

If the new file is in there, you've done it!

   Type:
   sudo fc-cache -f
   exit

From the desktop, go to Places> Computer> Filesystem> usr> share> fonts> MyBestFonts

All of your fonts should be in the file, and if they have a lock on them, you can change that by changing their permissions to read and write.

I hope this helps.

Revision history for this message
Jon N. (jonnicc) wrote :

I should have said "Folder" and not "file". The fonts are considered files, and the folder is "MyBestFonts". Sorry for the mix up.

Revision history for this message
A. Walton (awalton) wrote :

That's a very convoluted work around. Just put the files in ~/.fonts/ and run fc-cache again, that's all the fonts:// backend ever did anyways. It's part of the reason some of us don't mind if it doesn't come back; we really need a new font installation utility instead of a silly VFS backend.

Revision history for this message
Jon N. (jonnicc) wrote :

Thanks A. Walton. I'm a noob at this. Anything to simplify this helps. Thanks.

Revision history for this message
fjgaude (tanzen) wrote :

Yes, yes... easy to create the .fonts folder in the home directory, and then just add fonts to the folder. But, what then shows is the font file name and not the font name. A small issue but still an issue. Certainly the gvfs structure will add the font names when it gets fully converted over.

Revision history for this message
Tien Nguyen (tienhn) wrote :

Walton,
Thanks for the tip but by putting font files in ~/.font, will these fonts available to other users to use?

Revision history for this message
fjgaude (tanzen) wrote :

Yes, in all my cares, the fonts show up in programs, in Nautilus, gEdit, etc.

Revision history for this message
Jeremy Visser (jeremy-visser) wrote :

No, any other users on the system will not be able to use the fonts if they are put in ~/.fonts. Only you.

Revision history for this message
Jon N. (jonnicc) wrote :

that is why I did it the way I did, so that you not only could have the fonts in the shared folder, but you could add or copy your personal fonts whenever you wanted to. Just the way I did it, i guess.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you guys move to the support tracker or a mailing list for user discussions? you are spamming people who get a lot of bug mails already when you add comment there, the bug tracker is a tool to work on fixing bugs not to give user workarounds and discuss those

Revision history for this message
old_toby (simon-hornweb) wrote :

It's a long time since anything happened here ...

Does someone know what's going about that topic at gnome? Is Fontilus running now?

Revision history for this message
Nicolas Spalinger (yosch) wrote :

AFAICT upstream is leaning towards having a separate utility to handle fonts.
There was a fonts vfs patch but it wasn't complete and has now been dropped.

Hopefully something like gnome-specimen can be extended to provide the needed fonctionalities.

There's some discussion at the end of http://bugzilla.gnome.org/show_bug.cgi?id=407605

BTW, some work is also going on with the font selector itself:
http://aruiz.typepad.com/siliconisland/2008/08/font-selectio-1.html

Changed in gvfs:
status: New → Won't Fix
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Upstream aren't fixing this. From the upstream report:

"I think per the discussions in IRC surrounding these backends that it's
probably safe to close this as WONTFIX; fonts:// and themes:// are going the
way of the dodo in favor of better management tools (appearances capplet,
fontilus?) We can reopen if we change our minds at a later date."

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

In light of the upstream response to this, and the fact that they are planning improved management tools for fonts and themes, I'm going to close this bug report as Won't Fix.

Changed in gvfs:
status: Triaged → Won't Fix
Revision history for this message
DarkRedman (darkredman-deactivatedaccount) wrote :

It does the same in nautilus If I launch it like this : alt+f2 then "nautilus fonts:///"

Changed in gvfs:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.