Bug 1049677 - color is not known to server 'black'
Summary: color is not known to server 'black'
Alias: None
Product: Fedora
Classification: Fedora
Component: freenx-server
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Mosaab Alzoubi
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-01-08 02:03 UTC by Tom Horsley
Modified: 2015-06-29 14:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-29 14:15:07 UTC
Type: Bug

Attachments (Terms of Use)

Description Tom Horsley 2014-01-08 02:03:16 UTC
Description of problem:

The server running under freenx seems to be missing a color database, all sorts of programs I try to run under freenx give errors about unknown colors like 'black' and 'gray'.

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

How reproducible:
every time

Steps to Reproduce:
1.run under NX server on a fedora 20 system
2.try to use an app that references a color by name

Actual results:
perfectly ordinary colors not found

Expected results:
standard rgb.txt available from somewhere.

Additional info:

Comment 1 Tom Horsley 2014-01-08 02:37:35 UTC
Making a symlink to /usr/share/X11/rgb.txt in the directory /usr/share/nx
seems to fix this. I don't know what it has against its own rgb file in /usr/NX/share/rgb (perhaps it doesn't like the comment).

Comment 2 Fedora Admin XMLRPC Client 2015-03-03 13:14:33 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2015-05-29 10:22:50 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 4 Fedora End Of Life 2015-06-29 14:15:07 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

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.