[bluez/bluez] b0e1cb: mpris-proxy: Line-buffer stdout

["Seonggon, Cho" <noreply@github.com>]

  Branch: refs/heads/1175715
  Home:   https://github.com/bluez/bluez
  Commit: b0e1cb166c363cdba07910caac8f8d436ac8cdf4
      https://github.com/bluez/bluez/commit/b0e1cb166c363cdba07910caac8f8d436ac8cdf4
  Author: Seonggon Cho <jmsmg1@me.com>
  Date:   2026-09-29 (Tue, 29 Sep 2026)

  Changed paths:
    M tools/mpris-proxy.c

  Log Message:
  -----------
  mpris-proxy: Line-buffer stdout

mpris-proxy reports adapter and player changes with printf() but never
flushes stdout. When it runs as a service (tools/mpris-proxy.service)
stdout is a pipe to the journal, so glibc fully buffers it and nothing
is written until 4 KiB have accumulated or the process exits.

On a system whose Bluetooth adapter went away and came back every two
minutes, the "Bluetooth Adapter /org/bluez/hci0 removed" and "... found"
messages reached the journal in bursts of exactly 100 lines (about
4096 bytes), all carrying the timestamp of the flush rather than of the
event, i.e. up to about 80 minutes late.

Set stdout to line buffered at startup, as bt_shell_init() already does,
so every message reaches the journal with an accurate timestamp.

Assisted-by: Claude:claude-fable-5-1



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications