Bug 82882

Summary:

need bluecurve-looking icon

Product:

[Retired] Red Hat Public Beta

Reporter:

Tammy Fox <tammy.c.fox>

Component:

redhat-config-bind

Assignee:

Daniel Walsh <dwalsh>

Status:

CLOSED RAWHIDE

QA Contact:

Severity:

medium

Docs Contact:

Priority:

medium

Version:

phoebe

CC:

garrett, mitr

Target Milestone:

---

Target Release:

---

Hardware:

All

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2003-03-12 22:44:51 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
Icon for redhat-config-bind.	none

Description Tammy Fox 2003-01-28 02:22:47 UTC

The icon for redhat-config-bind that appears in the menus and at
system-settings:///Server in Nautilus does not match the other 3-D,
Bluecurve-looking icons. I am cc'ing Garrett to see if he has any
plans to make one for this release.

Comment 1 Garrett LeSage 2003-01-28 16:12:59 UTC

Similar to bug #82883, I made the icon and I'm not 100% sure why it's not
showing up. Quick guess: it might be due to the way the icon is specified in the
.desktop file. It could be possible that it's not referenced in such a way that
allows the icon theme to do its magic.

Comment 2 Daniel Walsh 2003-01-28 20:03:13 UTC

I went looking for the Icon and didn't find any for redhat-config-bind.

Comment 3 Garrett LeSage 2003-01-28 20:03:35 UTC

Created attachment 89655 [details]
Icon for redhat-config-bind.

Here's the icon for redhat-config-bind. Looking again, I don't think this was
actually added to redhat-artwork. It *could* be, but here it is nonetheless.

Comment 4 Daniel Walsh 2003-01-28 21:18:08 UTC

Fixed in redhat-config-bind-0.8.3-13

Comment 5 Daniel Walsh 2003-01-28 21:20:50 UTC

Should read 

Fixed in redhat-config-bind-1.9.0-13

Comment 6 Tammy Fox 2003-03-12 22:44:51 UTC

This looks fixed so I am closing this bug.