Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #57325 > unrolled thread

Bug#858824: Disrupting messages to tty

Back to article view | Back to linux.debian.kernel

Contents

  Bug#858824: Disrupting messages to tty Leon Meier <Leon.Meier@yandex.ru> - 2017-03-27 12:20 +0200
    Bug#858824: marked as done (Disrupting messages to tty) owner@bugs.debian.org (Debian Bug Tracking System) - 2017-03-27 16:00 +0200
    Bug#858824: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#858824: Disrupting messages to tty) Leon Meier <Leon.Meier@yandex.ru> - 2017-03-27 16:20 +0200
      Bug#858824: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#858824: Disrupting messages to tty) Ben Hutchings <ben@decadent.org.uk> - 2017-03-27 17:10 +0200

#57325 — Bug#858824: Disrupting messages to tty

[Multipart message — attachments visible in raw view] — view raw

Package: firmware-iwlwifi
Version: 20161130-2

When I'm doing whatever tasks in tty..., following messages get printed 
to the screen every couple of minutes:

iwlwifi ... L1 Enabled - LTR Disabled

along with a bunch of other, mostly iwlwifi-related messages.

They disrupt my workflow, overwriting the current screen contents. This 
is annoying. Are these messages important? Could these messages better 
go somewhere else?

Thanks is advance
Leon

[toc] | [next] | [standalone]

#57327 — Bug#858824: marked as done (Disrupting messages to tty)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 27 Mar 2017 14:50:11 +0100
with message-id <1490622611.2634.9.camel@decadent.org.uk>
and subject line Re: Bug#858824: Disrupting messages to tty
has caused the Debian Bug report #858824,
regarding Disrupting messages to tty
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
858824: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858824
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#57328 — Bug#858824: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#858824: Disrupting messages to tty)

 > This is not a bug.  Use a support channel to ask questions about
 > managing console output:
 > https://www.debian.org/support

Thanks, Ben.  Do you mean an IRC channel?

Btw., I searched the documentation there. If the answer is there, it is 
not easy to find. That site seems (partially) unmaintained.

Other options listed there regarding asking don't work:

- The site ask.debian.net did not list my posted question.
- The site www.debianhelp.org says it's under maintenance.
- forums.debian.net rejects to register me using my e-mail address.

[toc] | [prev] | [next] | [standalone]

#57329 — Bug#858824: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#858824: Disrupting messages to tty)

[Multipart message — attachments visible in raw view] — view raw

On Mon, 2017-03-27 at 16:13 +0200, Leon Meier wrote:
>  > This is not a bug.  Use a support channel to ask questions about
>  > managing console output:
>  > https://www.debian.org/support
> 
> Thanks, Ben.  Do you mean an IRC channel?

You could use any of IRC, mailing list (e.g. debian-user) or
forums.debian.net.

> Btw., I searched the documentation there. If the answer is there, it is 
> not easy to find. That site seems (partially) unmaintained.
> 
> Other options listed there regarding asking don't work:
> 
> - The site ask.debian.net did not list my posted question.
> - The site www.debianhelp.org says it's under maintenance.
> - forums.debian.net rejects to register me using my e-mail address.

Well that's strange.  That leaves at least two options.

Ben.

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web