Bug 428059 - Nautilus uses random background color on each launch
Summary: Nautilus uses random background color on each launch
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus   
(Show other bugs)
Version: 8
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-01-08 22:41 UTC by condor
Modified: 2015-03-03 22:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 05:44:32 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 506336 None None None Never

Description condor 2008-01-08 22:41:11 UTC
Description of problem:

Since a week or two, each time I launch Nautilus it provides another
background color in the file view. Changing the color via menu doesn't really
help, because the colors seem to be mapped wrongly: currently for example,
Nautilus started with a black background. Assinging a white background results
in a black one, assigning a yellow background results in a blue one, and so on.
Using the "reset" background randomizes it again.

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


Comment 1 Alexander Koenig 2008-01-30 13:23:36 UTC
I have a similar (probably the same) color issue. It is not related to starting
nautilus, however. Every new nautilus window I open uses a random new background
color. I use the same build of nautilus.

As a workaround creating small white (or whatever non-random color you prefer)
PNG image, adding that to the nautilus patterns and using it as the folder
background will behave as expected. This might have minor performance and memory
usage implications - it is much easier on my eyes though.

Comment 2 Bug Zapper 2008-11-26 09:20:59 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 3 Bug Zapper 2009-01-09 05:44:32 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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