Bug 588273 - Ships incorrect icon for 32x32
Summary: Ships incorrect icon for 32x32
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-color-manager   
(Show other bugs)
Version: 13
Hardware: All Linux
low
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-03 11:32 UTC by Michael Monreal
Modified: 2010-05-04 23:49 UTC (History)
2 users (show)

Fixed In Version: gnome-color-manager-2.30.1-2.fc13
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-04 08:18:22 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
32x32 g-c-m icon (2.31 KB, image/png)
2010-05-03 11:32 UTC, Michael Monreal
no flags Details

Description Michael Monreal 2010-05-03 11:32:15 UTC
Created attachment 410944 [details]
32x32 g-c-m icon

The gnome-color-manager-2.30.1-1.fc13.i686 package still ships the old 32x32 icon. I will attach the correct icon here.

The package also ships a 64x64 version (of the old icon), which is not really a needed size and can be dropped.

I did not yet check upstream git, if this is already fixed there, just roll a new rpm for F13.

Comment 1 Richard Hughes 2010-05-04 08:18:22 UTC
Duping for my sanity, but I know what you mean. Please see Mo's bug. Thanks.

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

Comment 2 Fedora Update System 2010-05-04 09:21:44 UTC
gnome-color-manager-2.30.1-2.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/gnome-color-manager-2.30.1-2.fc13

Comment 3 Fedora Update System 2010-05-04 23:49:03 UTC
gnome-color-manager-2.30.1-2.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.


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