debcrafters-packages team mailing list archive

[Charles <1966433@xxxxxxxxxxxxxxxxxx>]

Are you asking for upstream to document how to use systemd in the
pipewire man page? I'm confused what you're asking for here. Those
unfamiliar with systemd services seem very unlikely to read the pipewire
man page.

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to pipewire in Ubuntu.
https://bugs.launchpad.net/bugs/1966433

Title:
  Pipewire services start up on remote (ssh) logins

Status in pipewire package in Ubuntu:
  Won't Fix
Status in pipewire package in Debian:
  Won't Fix

Bug description:
  This concern pipewire 0.3.48-1ubuntu1 in Ubuntu jammy.

  I log into an installed system via ssh, and I see

  skunk@darkstar:~$ ps auxww | grep skunk
  root       13771  0.5  0.1  19772 12224 ?        Ss   07:35   0:00 sshd: skunk [priv]
  skunk      13774  5.4  0.1  17160  9940 ?        Ss   07:35   0:00 /lib/systemd/systemd --user
  skunk      13775  0.0  0.0  25600  5292 ?        S    07:35   0:00 (sd-pam)
  skunk      13782  0.4  0.0  34460  6360 ?        Ssl  07:35   0:00 /usr/bin/pipewire
  skunk      13783  0.4  0.0  18632  6856 ?        Ssl  07:35   0:00 /usr/bin/pipewire-media-session
  skunk      13801  0.0  0.0   8412  4340 ?        Ss   07:35   0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
  skunk      13831  0.0  0.0  19932  8052 ?        S    07:35   0:00 sshd: skunk@pts/0
  skunk      13832  0.0  0.0   5256  4124 pts/0    Ss   07:35   0:00 -bash
  skunk      13854  0.0  0.0   7692  3328 pts/0    R+   07:35   0:00 ps auxww
  skunk      13855  0.0  0.0   4024  2144 pts/0    S+   07:35   0:00 grep --color=auto skunk

  Pipewire is a multimedia service. It should not be running in a
  remote, non-graphical login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1966433/+subscriptions