Description of problem: When changing a 'default user directory' gvfs fails to change correct icon attributes and the icon attributes can not be manually set. Trying to manually set gives: 'Error setting attribute: Setting attribute standard::icon not supported' ================================================== $ cat ~/.config/user-dirs.dirs # This file is written by xdg-user-dirs-update ... # XDG_TEMPLATES_DIR="$HOME/Templates" ... XDG_DOWNLOAD_DIR="$HOME/../Downloads" $ gvfs-info ~/../Downloads | grep icon standard::icon: folder standard::symbolic-icon: folder-symbolic, folder $ ================================================== $ cat ~/.config/user-dirs.dirs # This file is written by xdg-user-dirs-update ... # XDG_TEMPLATES_DIR="$HOME/Templates" ... XDG_DOWNLOAD_DIR="$HOME/Downloads" $ gvfs-info ~/Downloads | grep icon standard::icon: folder-download, folder standard::symbolic-icon: folder-download-symbolic, folder-symbolic, folder-download, folder metadata::nautilus-icon-position: $ ================================================== Version-Release number of selected component (if applicable): $ rpm -qa gvfs gvfs-1.28.3-1.fc24.x86_64 How reproducible: always Steps to Reproduce: 1. Change ~/.config/user-dirs.dirs 2. Change not reflected by gvfs-info as above 3. Actual results: wrong icons on folders Expected results: correct icons on folders Additional info: interestingly, the correct icon and location are displayed under 'Places' in Files/Nautilus and File Chooser Dialogue - yet, 'standard::symbolic-icon' is wrong
Thanks for your bug report. The icons are set by GLib/GIO, not by GVfs, so let's change the component. However, I see some possible causes: - Maybe those variables need to be specified as absolute paths. Does it work if you specify the download dir as the following? XDG_DOWNLOAD_DIR="/home/Downloads" - Xdg relevant code uses cache, does it work when you reboot your computer?
I've had my folders arranged like this for years - I just got tired of this aesthetic bug so decided to follow it... So, no, many boots and not a chache issue. But, the other suggestion is much more positive - yes, using an absolute path does provide the correct icons: ================================================== $ cat ~/.config/user-dirs.dirs # This file is written by xdg-user-dirs-update ... XDG_DOWNLOAD_DIR="/home/Downloads" XDG_TEMPLATES_DIR="$HOME/Templates" ... $ gvfs-info ~/../Downloads | grep icon standard::icon: folder-download, folder standard::symbolic-icon: folder-download-symbolic, folder-symbolic, folder-download, folder ==================================================
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.