Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] DBUS messages on tty1 (stderr?)
Date: Sun, 26 Jan 2020 01:25:55 +0100	[thread overview]
Message-ID: <20200126002555.9djcA5GvtDhdlwbW5DvLg99iLC6ryYqv7OXgT_Gg7mk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18505@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

Closed issue by Henry-Wilson on void-packages repository

https://github.com/void-linux/void-packages/issues/18505

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void 5.4.13_2 x86_64 GenuineIntel uptodate rFFF
* package:  
  dbus-1.12.16_1

### Expected behavior
  Stop printing error messages to tty1 when I enable the --syslog-only option

### Actual behavior
  Continue printing error messages to tty1 when I enable the syslog-only option.

### Steps to reproduce the behavior
  nm (network manager) normally. mess around with nmcli on tty1 until dbus throws an error to stderr. For me, this happens when I enable and disable (some) connections.

  Edit /var/service/dbus/run to include the --syslog-only option. The prints should still happen.

  For the record: I have socklog-void installed, and that cuts down on some of the messages that get printed to stderr, but apparently does not fix all of them.

  Let me know if any of you all have any idea of what to do. Thank you!



      reply	other threads:[~2020-01-26  0:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 18:19 [ISSUE] " voidlinux-github
2020-01-26  0:25 ` voidlinux-github [this message]

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=20200126002555.9djcA5GvtDhdlwbW5DvLg99iLC6ryYqv7OXgT_Gg7mk@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).