1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL

  • systemd-user and ssh

    From Russell Coker@21:1/5 to All on Fri Aug 1 01:40:01 2025
    Below is part of the output of needrestart on a server I run. A login manager probably doesn't need audio access, I don't recall hearing sddm make sounds
    but it could be needed in different configurations. The other accounts are
    all accessed via ssh for text mode stuff. Should we have systemd work differntly in this regard? I know it's too late for Trixie but for the next release.

    I ask here because the systemd maintainers are really busy and request that upstream issues be reported upstream and the upstream developers are probably happy with the current situation.

    User sessions running outdated binaries:
    kvm @ session #3324: screen[1327858]
    kvm @ user manager: (sd-pam)[1232012]
    kvm @ user service: dbus-broker.service[1232026], dbus.service[3430682], pipewire-pulse.service[3430687], pipewire.service[3430685], wireplumber.service[3430686]
    ml @ session #9101: sshd-session[3577113,3577152]
    ml @ user manager: (sd-pam)[3577120]
    ml @ user service: dbus.service[3577140], filter-chain.service[3577144], pipewire-pulse.service[3577149], pipewire.service[3577141], wireplumber.service[3577146]
    sddm @ session #10816: sddm-helper[138841]
    sddm @ user manager: (sd-pam)[2592481]
    sddm @ user service: dbus.service[2592498], filter-chain.service[2592501], pipewire-pulse.service[2592504], pipewire.service[2592500], wireplumber.service[2592502]
    yifei @ session #10828: mosh-server[139466]
    yifei @ session #11207: bash[284215], mosh-server[284214]
    yifei @ user manager: (sd-pam)[139359]
    yifei @ user service: dbus.service[139378], filter-chain.service[139381], pipewire-pulse.service[139388], pipewire.service[139379], wireplumber.service[139386]

    --
    My Main Blog http://etbe.coker.com.au/
    My Documents Blog http://doc.coker.com.au/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Simon Richter@21:1/5 to All on Fri Aug 1 03:10:01 2025
    Hi,

    login managers typically need audio access for accessibility functions.

       Simon

    <html>
    <head>
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    </head>
    <body>
    <span dir="ltr" style="margin-top:0; margin-bottom:0;">Hi,</span>
    <br>
    <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">login managers typically need audio access for accessibility functions.</span>
    <br>
    <br><span dir="ltr" style="margin-top:0; margin-bottom:0;">&nbsp;&nbsp; Simon</span>
    <br>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bastian Blank@21:1/5 to Russell Coker on Fri Aug 1 09:30:01 2025
    On Fri, Aug 01, 2025 at 09:08:17AM +1000, Russell Coker wrote:
    Below is part of the output of needrestart on a server I run.

    Please describe in your own words what you think you see.

    A login manager
    probably doesn't need audio access, I don't recall hearing sddm make sounds but it could be needed in different configurations.

    You've never heard blind people working on technology? Sound is a large
    part of accessibility.

    The other accounts are all accessed via ssh for text mode stuff.

    In that output I see several users running dbus and pipewire. Those both
    are per-user and not per-session services. Both are not restricted to graphical stuff.

    Should we have systemd work differntly in this regard?

    systemd just does what you or the software tells it to do, aka you are
    barking up the wrong tree here.

    You can disable pipewire for all users:
    rm /etc/systemd/user/default.target.wants/pipewire*

    Maybe the pipewire services could be switched to socket activation, but
    I don't see much to gain here.

    Bastian

    --
    War is never imperative.
    -- McCoy, "Balance of Terror", stardate 1709.2

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)