Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 56039

Summary:	Nautilus doesn't know how to draw embossed logo
Product:	[Retired] Red Hat Linux	Reporter:	Alfredo Ferrari <alfredo.maria.ferrari>
Component:	nautilus	Assignee:	Havoc Pennington <hp>
Status:	CLOSED DUPLICATE	QA Contact:	David Lawrence <dkl>
Severity:	low	Docs Contact:
Priority:	medium
Version:	7.2
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-02-11 21:09:18 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:

Description Alfredo Ferrari 2001-11-11 16:04:45 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.9-13.1 i686)

Description of problem:
The "embossed logo" option in background-properties-capplet does not work.
It behaves like the "centered" option. Actually, in the preview window it
works correctly, and while starting gnome it seems to work correctly until
the nautilus icons come up and suddendly the "embossed logo" becomes a
"centered" logo. Maybe a problem bewteen gnome and nautilus? However
disabling nautilus from painting the background does not help. It worked
fine in RH7.1... Actually also the "scaled" option does not work properly.

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


How reproducible:
Always

Steps to Reproduce:
1.Click "Start here" in the gnome/nautilus control center or fire up the
gnome control-center
2.Navigate to the "background" setting option menu
3.select an icon, ie redhat-emboss.png, set the "emboss" option and apply
	

Actual Results:  a "centered" icon is drawn

Expected Results:  an "embossed" one, like in the preview and in RH7.1

Additional info:

Comment 1 Havoc Pennington 2002-02-27 19:14:00 UTC


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