Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#24879 - [initscripts] /sbin/rc.d doesn't clear text colors on nonexistent script error

Attached to Project: Arch Linux
Opened by Jacob Okamoto (Okomokochoko) - Saturday, 25 June 2011, 17:54 GMT
Last edited by Tom Gundersen (tomegun) - Tuesday, 26 July 2011, 11:06 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture x86_64
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When using /sbin/rc.d the script doesn't print ${C_CLEAR} to reset the text to the terminal default color/weight if the script doesn't exist.


Steps to reproduce:
$ rc.d start zflkasj

which prints

:: Error: Daemon script zflkasj does not exist.

The prompt following (and presumably any output until the next use of terminal colors) will be bold.

I attached a tiny patch, just adds a line to print ${C_CLEAR}.
This task depends upon

Closed by  Tom Gundersen (tomegun)
Tuesday, 26 July 2011, 11:06 GMT
Reason for closing:  Fixed
Comment by Tom Gundersen (tomegun) - Sunday, 26 June 2011, 17:31 GMT
I don't think the patch got attached properly...? If you send a git-formatted patch to arch-projects@archlinux.org, that would be appreciated.

@Seblu: I think you wanted to change that error message anyway, maybe this is a good opportunity?
Comment by Sébastien Luttringer (seblu) - Sunday, 26 June 2011, 17:33 GMT
you'r right. I will do this when the sun has stopped shining. ;)
Comment by Tom Gundersen (tomegun) - Monday, 25 July 2011, 21:29 GMT
@Jacob: can you verify that this has been fixed with initscripts from [testing]?
Comment by Jacob Okamoto (Okomokochoko) - Tuesday, 26 July 2011, 04:02 GMT
Yup, it's fixed.

Loading...