Bug 456925 - [coreutils] complaint about "Unknown colorls variable `ca' in tcsh"
Summary: [coreutils] complaint about "Unknown colorls variable `ca' in tcsh"
Keywords:
Status: CLOSED DUPLICATE of bug 457342
Alias: None
Product: Fedora
Classification: Fedora
Component: coreutils
Version: rawhide
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-28 17:19 UTC by Joachim Frieben
Modified: 2008-07-31 15:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-31 15:22:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Joachim Frieben 2008-07-28 17:19:17 UTC
Description of problem:
After upgrading to coreutils-6.12-7.fc10, setting LS_COLORS in .cshrc
for the tcsh shell leads to the error message:

   "Unknown colorls variable `ca'."

Shell initalization aborts at this point.

Version-Release number of selected component (if applicable):
coreutils-6.12-7.fc10

How reproducible:
Always.

Steps to Reproduce:
1. Update to coreutils-6.12-7.fc10.
2. Open GNOME terminal using tcsh as login shell.
  
Actual results:
Shell initialization aborts complaining about an unknown colorls
variable `ca'.

Expected results:
Shell is fully initialized and LS_COLORS are applied successfully.

Additional info:
- setting LS_COLORS in .cshrc has been working for the last 10 years ;o)
- applying the 'setenv LS_COLORS ...' command on the command line appears
  to work however.
- according to the RPM changelog, there has been a change related to this:
  "ls: --color now highlights files with capabilities (#449985)".

Comment 1 Christopher Beland 2008-07-31 14:47:30 UTC
I am having the same problem with Fedora 9 after today's update to
coreutils-6.10-28.fc9.i386.  It's preventing me from "su"ing because (root's
shell is set to /bin/tcsh).

I can "source /home/beland/.cshrc" without error.  If I put an "echo" statement
on the first line of that file, I don't see the output when starting an xterm,
leading me to believe it's not a problem with my customizations.

Comment 2 Kamil Dudka 2008-07-31 15:22:38 UTC

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


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