Created attachment 325232 [details] Vcard icons in Nautilus, Thunar and KDE Description of problem: When displaying a vcard (i. e., a file with the mime type "text/directory"), Nautilus displays a very generic icon (text/*?) without any hint that this file an Electronic Business Card, thus making user's life harder Version-Release number of selected component (if applicable): Gnome 2.24-1 How reproducible: Always How to Reproduce: Open a folder containing a vcard (a text/directory file). Actual results: Generic icon without any hint that this is a vcard, making user's life harder. Expected results: Some kind of specific icon indicating that this is a vcard, making user's life easier. Additional info: The card is correcly identified as a vcard, verified with the context menu. This is true even when I install a fallback icon for the mime type "text/directory" in /usr/share/icons/hicolor using xdg-icon-resource install... Thunar displays the icon I have installed for the vcards. KDE (konqueror, Dolphin) displays a themed icon showing that this is vcard. This most likely related to the discussion in http://bugzilla.gnome.org/show_bug.cgi?id=528320. As I see it, this can be handled in at least three ways: - This is the intended behaviour i. e. not a bug. This is not my opinion... - The fact that vcard icons are missing from the default Fedora theme is a bug or an RFE for specific vcards icons. - The fact that the the generic text/* (?) is used instead of the installed "text/directory" icon is a bug, as indicated in the upstream bug. Possibly this means that the upstream bug should be reopened? I just presume that the patches applied upstream are present in the Fedora 10 release. Otherwise, the explanation is simple... I had this prooblem for some time, and presumed that it should be resolved in Fedora 10/Gnome 2.24.
Created attachment 325245 [details] Simple test vcard file, the same as in the the icons display attachment Simple test vcard file, the same as in the the icons display attachment
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 WONTFIX if it remains open with a Fedora 'version' of '10'. 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 prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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. Thank you for reporting this bug and we are sorry it could not be fixed.