Where does Font Manager store its collection info? (lost all collections)

[GoogleCodeExporter]

Hi there. This isn't a bug report (although if you think it's an issue, I 
suppose you could keep it as a bug report). This was the only way I could find 
to contact you -- can't seem to find your e-mail address, and Google's CAPTCHA 
service protecting your e-mail is being flaky right now.

Anyhow, all my collections disappeared today, and I'm not sure where they've 
gone. I have a relatively recent backup on a hard drive, but I'm not sure where 
to look to find the database of collections. Where is it stored?

Also, I can't give a list of steps to reproduce this problem, but if you think 
it is a bug, here are a couple details: I loaded up Font Manager, installed a 
couple fonts, closed it, ran fc-cache -r (for some reason, nothing else I do 
can make an installed font show up -- not in Font Manager, FontMatrix, 
gnome-font-viewer, or simply copying the font file into ~/.fonts)... then 
opened up Font Manager again. All the collections had disappeared, even though 
I've run fc-cache -r a number of times without this happening.

Any wisdom you could give me would be greatly appreciated!

Thanks,
Paul

Original issue reported on code.google.com by amillion...@gmail.com on 14 Jun 2011 at 9:21

[GoogleCodeExporter]

Collection data is stored in two places.

~/.config/fontgroups.xml - (for compatibilty with the KDE font manager)
~/.local/share/font-manager/Collections.xml

and there may be a ~/.local/share/font-manager/Collections.xml.bak also.

Original comment by JerryCasiano on 15 Jun 2011 at 2:16

• Changed state: Accepted

[GoogleCodeExporter]

And yes I definitely consider this a bug, a critical one, so I'm leaving this 
open as a reminder. ;-)

This is something that will definitely need to be addressed in the next version.

Original comment by JerryCasiano on 15 Jun 2011 at 2:28

• Added labels: Milestone-Release1.0, Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

This should be fixed in SVN.

Please test using the latest revision.

Original comment by JerryCasiano on 27 Apr 2014 at 8:26

• Changed state: Fixed