All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Hofstaedtler <zeha@debian.org>
To: "Thomas Weißschuh" <thomas@t-8ch.de>
Cc: util-linux@vger.kernel.org, Axel <axel.scheepers76@gmail.com>,
	1094283@bugs.debian.org
Subject: Re: Bug#1094283: util-linux: dmesg shows color when /etc/terminal-colors.d/disable is present (and no override in xdg locations)
Date: Sun, 26 Jan 2025 23:19:31 +0100	[thread overview]
Message-ID: <Z5a08yD10L1J8AIa@per.namespace.at> (raw)
In-Reply-To: <173791554931.11406.7776184826380347386.reportbug@teal.home>

Hello Thomas,

it appears commit 4bdf22803f9a41329694e0c3c82189635dccdcd0 breaks
disabling colors using the documented mechanism of touching
/etc/terminal-colors.d/dmesg.disable. See below for a user report.

On Sun, Jan 26, 2025 at 07:19:09PM +0100, Axel wrote:
> Package: util-linux
> Version: 2.40.4-1
> 
> Running dmesg after upgrading to trixie started showing color. The manpage
> mentions creating /etc/terminal-colors.d/disable which should disable colors
> for all. Creating the also mentioned /etc/terminal-colors.d/dmesg.disable
> doesn't disable color output also. I had /etc/terminal-colors.d/disable
> configured which did disable colors on -stable.

From what I can tell, the new rc = -ENOENT in colors_readdir
introduced in 4bdf22803f9a41329694e0c3c82189635dccdcd0 bubbles up to
colors_init:

	int rc = colors_read_configuration(cc);  // calls colors_readdir, now returns -2
	if (rc)
		cc->mode = UL_COLORMODE_DEFAULT;
    else {
Evaluating color scores is skipped, effectively ignoring the
"disable" file.

Could you please take a look?

Reverting 4bdf22803f9a41329694e0c3c82189635dccdcd0 fixes the problem
for me.

Debug output from TERMINAL_COLORS_DEBUG=0xffff ./dmesg

| 321357: termcolors:     CONF: terminal is ready (supports 256 colors)
| 321357: termcolors:     CONF: reading dir: '/root/.config/terminal-colors.d'
| 321357: termcolors:     CONF: reading dir: '/etc/terminal-colors.d'
| 321357: termcolors:     CONF: item 'dmesg.disable': score=21 [cur: 0, name(5): dmesg.disable, term(0): (null)]
| 321357: termcolors:     CONF: setting 'disable' from 0 -to-> 21
| Colors:
| 	utilname = 'dmesg'
| 	termname = 'xterm-256color'
| 	scheme file = '(null)'
| 	mode = auto
| 	has_colors = 1
| 	disabled = 0
| 	configured = 1
| 	cs configured = 0
| 
| 	score disable = 21
| 	score enable = 0
| 	score scheme = 0


After reverting 4bdf22803f9a41329694e0c3c82189635dccdcd0:

| 321318: termcolors:     CONF: terminal is ready (supports 256 colors)
| 321318: termcolors:     CONF: reading dir: '/root/.config/terminal-colors.d'
| 321318: termcolors:     CONF: reading dir: '/etc/terminal-colors.d'
| 321318: termcolors:     CONF: item 'dmesg.disable': score=21 [cur: 0, name(5): dmesg.disable, term(0): (null)]
| 321318: termcolors:     CONF: setting 'disable' from 0 -to-> 21
| Colors:
| 	utilname = 'dmesg'
| 	termname = 'xterm-256color'
| 	scheme file = '(null)'
| 	mode = never
| 	has_colors = 0
| 	disabled = 0
| 	configured = 1
| 	cs configured = 0
| 
| 	score disable = 21
| 	score enable = 0
| 	score scheme = 0


Thanks,
Chris


       reply	other threads:[~2025-01-26 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <173791554931.11406.7776184826380347386.reportbug@teal.home>
2025-01-26 22:19 ` Chris Hofstaedtler [this message]
2025-02-03 20:53   ` Bug#1094283: util-linux: dmesg shows color when /etc/terminal-colors.d/disable is present (and no override in xdg locations) Thomas Weißschuh
2025-02-03 21:07     ` Chris Hofstaedtler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z5a08yD10L1J8AIa@per.namespace.at \
    --to=zeha@debian.org \
    --cc=1094283@bugs.debian.org \
    --cc=axel.scheepers76@gmail.com \
    --cc=thomas@t-8ch.de \
    --cc=util-linux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.