Bug 72098 - Theme manager default theme screenshot is incorrect, other themes should be removed / replaced
Summary: Theme manager default theme screenshot is incorrect, other themes should be r...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdebase
Version: 8.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-08-21 04:14 UTC by Mike MacCana
Modified: 2007-04-18 16:45 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-04 20:06:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Mike MacCana 2002-08-21 04:14:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020809

Description of problem:
The screenshot used in kcontrol theme manager window for default doesn't
actualyl describe Red Hat default KDE theme that will be applied when this is
enabled.

In addition, the `Eclipse' `MGBriezh' `Nostalgy' and `Wood' themes are very low
quality KDE1 themes which look quite poor. Perhaps replace them with a
Crystal/Keramik theme, a Redmond theme, and somethign else that uses the inbuilt
KDE3 icons, widget styles, decorations, etc?

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


How reproducible:
Always

Steps to Reproduce:
1.Run the KDE Control Center, visit Look & Feel - Theme Manager
2. Change your theme to one of the KDE 1 themes
3.Notice the screenshot for default. Apply the default style, and return to Red
Hat's new KDE theme (ratehr than the one in the screenshot).

	

Additional info:

Comment 1 Ngo Than 2002-08-31 18:42:08 UTC
i fixed a bug in default KDE theme and added a new Bluecurve theme.
kdebase-3.0.3-8 or newer has this fix.

Comment 2 Bill Nottingham 2006-08-04 20:06:38 UTC
Red Hat Linux and Red Hat Powertools are currently no longer supported by Red
Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED
state for these products.

However, we do want to make sure that nothing important slips through the
cracks. If, in fact, these issues are not resolved in a current Fedora Core
Release (such as Fedora Core 5), please open a new issues stating so. Thanks.


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