Bug 491118 - Ugly icons in Thunar, when selected "Fedora", "Mist", "GNOME", ... icon-sets
Summary: Ugly icons in Thunar, when selected "Fedora", "Mist", "GNOME", ... icon-sets
Keywords:
Status: CLOSED DUPLICATE of bug 489402
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-icon-theme
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-19 14:34 UTC by Michal Nowak
Modified: 2013-03-08 02:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-03-25 10:54:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Ugly icons in Thunar (100.07 KB, image/png)
2009-03-19 14:34 UTC, Michal Nowak
no flags Details

Description Michal Nowak 2009-03-19 14:34:54 UTC
Created attachment 335859 [details]
Ugly icons in Thunar

Description of problem:

When using icon sets "Fedora", "Mist", "GNOME" there are pretty ugly icons, see the screen-shot, but some are quite nice.

Comment 1 Michal Nowak 2009-03-19 14:37:57 UTC
"""
(Thunar:3627): Gtk-WARNING **: Error loading theme icon 'gnome-fs-home' for stock: Icon 'gnome-fs-home' not present in theme
"""

is emitted to .xsession-errors

Comment 2 Kevin Fenzi 2009-03-24 19:35:05 UTC
Yeah, "Fedora" should be the default. 

I agree the generic file icon is kind of ugly, but I think the only option here is to switch to 
Tango, and I don't know that it's quite ready. ;( 

So, not sure what to do with this bug... perhaps close it for now and revisit switching to nodoka in F12? Do you agree?

Comment 3 Michal Nowak 2009-03-25 10:54:56 UTC
Thanks for the tip, Tango is quite nice, but neither do I know whether is ready, or not. Closing for now. Thanks!

Comment 4 Christoph Wickert 2009-03-25 17:27:09 UTC
Re-closing as duplicate of bug # 489402. Let's track all icon theme issued there.

*** This bug has been marked as a duplicate of bug 489402 ***


Note You need to log in before you can comment on or make changes to this bug.