Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 102164 - gnome-theme-manager shows corrupted screenshots
Summary: gnome-theme-manager shows corrupted screenshots
Keywords:
Status: CLOSED DUPLICATE of bug 100494
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: control-center
Version: beta1
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Jonathan Blandford
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-11 23:18 UTC by Kyle R Maxwell
Modified: 2013-04-02 04:18 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:58:04 UTC
Embargoed:


Attachments (Terms of Use)
screenshot showing the problem (deleted)
2003-08-11 23:20 UTC, Kyle R Maxwell
no flags Details

Description Kyle R Maxwell 2003-08-11 23:18:47 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030729
Mozilla Firebird/0.6.1

Description of problem:
When viewing themes in the Theme manager, the screenshots look corrupted, as if
on a TV channel with lots of static. I will submit a screenshot as soon as the
bug processes.

Version-Release number of selected component (if applicable):
control-center-2.2.2-1

How reproducible:
Always

Steps to Reproduce:
1. Open Themes from the Preferences menu.
2.
3.
    

Additional info:

Comment 1 Kyle R Maxwell 2003-08-11 23:20:02 UTC
Created attachment 93598 [details]
screenshot showing the problem

Comment 2 Bill Nottingham 2003-08-12 02:13:38 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 18:58:04 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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