Summary: | How about get rid of ~/.colord and use XDG standard dirs instead? | ||
---|---|---|---|
Product: | colord | Reporter: | lh <jarryson> |
Component: | daemon | Assignee: | Richard Hughes <richard> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | mclasen |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | patch |
Description
lh
2013-09-24 18:08:55 UTC
$ cat ~/.config/color cat: /home/hughsie/.config/color: No such file or directory ~/.color/icc is the deprecated location for icc profiles. It's been replaced by ~/.local/share/icc/ -- both are monitored by the session component. Are you using gnome-settings-daemon, colord-kde or xiccd? (In reply to comment #1) > $ cat ~/.config/color > cat: /home/hughsie/.config/color: No such file or directory > > ~/.color/icc is the deprecated location for icc profiles. It's been replaced > by ~/.local/share/icc/ -- both are monitored by the session component. Are > you using gnome-settings-daemon, colord-kde or xiccd? Hi, I am using Archlinux, gnome 3.10, colord1.02. I tried to find ".color" in colord-gtk, gnome-settings-daemon, gnome-color-manager, seems all irrelevant. I tried many applications, "~/.color/icc" appears after I open "gnome-settings-daemon". I modified the code of colord, removed two lines in cd-icc-store.c, and "~/.color/icc" didn't showed up again. Overall, I don't really know where is the problem. The gsd color plugin calls: ret = cd_icc_store_search_kind (priv->icc_store, CD_ICC_STORE_SEARCH_KIND_USER, CD_ICC_STORE_SEARCH_FLAGS_CREATE_LOCATION, NULL, &error); it explicitly asks to create the location, and from a quick look at the libcolord code, there is no notion of 'create the preferred location, but not the legacy one'. Created attachment 89696 [details] [review] patch Patch applied, thanks! |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.