Upgrading to 12.10 created a "~/fontconfig" folder but did not delete it

Bug #1074778 reported by Agmenor
134
This bug affects 32 people
Affects Status Importance Assigned to Milestone
fontconfig (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I upgraded from Ubuntu 12.04 to 12.10. In the process, a folder called "~/fontconfig" was created and not deleted. This happened on my two machines.

More information here: http://askubuntu.com/questions/202796/what-is-the-fontconfig-folder-in-my-home-may-i-delete-it

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: fontconfig 2.10.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Sat Nov 3 18:57:29 2012
InstallationDate: Installed on 2012-04-29 (188 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
SourcePackage: fontconfig
UpgradeStatus: Upgraded to quantal on 2012-10-20 (14 days ago)

Revision history for this message
Agmenor (agmenor) wrote :
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in fontconfig (Ubuntu):
status: New → Confirmed
Revision history for this message
Edwin Lee (leeed2001) wrote :

Same exact thing happened to me, deleting that folder now.

Mukil Elango (mukilane)
description: updated
Revision history for this message
Julian Foad (julianfoad) wrote :

This folder got created when I upgraded from 12.04 LTS to 14.04.1 LTS using the software updates tool "upgrade to a new LTS release" method.

Revision history for this message
Alfredo Hernández (aldomann) wrote :

Three years and this bug is still marked just as "Confirmed"? Oh, boy...

Revision history for this message
gualter (gualterio60) wrote :

I'm in a fresh 14.04, not upgraded. Suddenly "fontconfig" folder is created at Home. I deleted, but reapared. I would like to change folder location. Maybe changing path of ignote file configuration

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.