[ISSUE] DBUS messages on tty1 (stderr?)

[ISSUE] DBUS messages on tty1 (stderr?)

[voidlinux-github]

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

New 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!

Re: [ISSUE] [CLOSED] DBUS messages on tty1 (stderr?)

[voidlinux-github]

[-- 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!