Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 455352 - Oxygen theme has icon conflict with kdepim
Summary: Oxygen theme has icon conflict with kdepim
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: rawhide
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-07-14 23:46 UTC by G.Wolfe Woodbury
Modified: 2008-07-15 01:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-07-15 01:36:41 UTC

Attachments (Terms of Use)

Description G.Wolfe Woodbury 2008-07-14 23:46:06 UTC
Description of problem:
  gnome-themes contains the oxygen icon theme, which now has a conflict with
kdepim for the "new-appointment" icon.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. rawhide install
2. leave gnome-themes selected
3. select to install kdepim
Actual results:
  conflict detected for one of the "appointment-new" icons

Expected results:
  no conflicts

Additional info: i686 (Coppermine) CPU - rawhide install 20080714

Comment 1 Matthias Clasen 2008-07-15 00:06:12 UTC
The gnome-themes package does not contain the oxygen icon theme.
It is part of the oxygen-icon-theme-package, which I don't know the bugzilla
component for...

Comment 2 Rex Dieter 2008-07-15 00:20:25 UTC
Are you sure?  that was fixed (?) in kdepim-4.0.98-3.

Comment 3 G.Wolfe Woodbury 2008-07-15 01:36:41 UTC
Upon further investigation...
No, It seems to have gone away when I install gnome-themes the conflict did not

closing as rawhide

Comment 4 Kevin Kofler 2008-07-15 01:41:16 UTC
Changing resolution NOTABUG->RAWHIDE, there was definitely a bug there, it's 
just already fixed. :-)

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