Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Pipewire error

Graphical Environments, Managers, Multimedia & Desktop questions.
Post Reply
Message
Author
mm3100
Posts: 336
Joined: 2020-10-21 21:39
Has thanked: 8 times
Been thanked: 13 times

Pipewire error

#1 Post by mm3100 »

Hello everyone,
After upgrading to Bullseye I started getting this error

Code: Select all

pipewire[1242]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
Googling didn't help me much, but I tried to install xdg-desktop-portal and xdg-desktop-portal-kde as I use KDE. After that I would get these messages

Code: Select all

pipewire[1242]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
org.freedesktop.impl.portal.desktop.kde[1480]: xdp-kde: Desktop portal registered successfully
I am asking if there are some misconfiguration or missing components on my end, as I am unfamiliar with both of those? After some time I would randomly get pipewire errors in journal complaining about having a broken pipe, which is obvious since it failed to start.

kedaha
Posts: 3521
Joined: 2008-05-24 12:26
Has thanked: 33 times
Been thanked: 77 times

Re: Pipewire error

#2 Post by kedaha »

Hi
Have you looked at the wiki about PipeWire? Looks like there have been a few installation changes in Bullseye.
I simulated installing it on a testing system which shows it needs these packages:

Code: Select all

# apt install -s pipewire
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  alsa-topology-conf alsa-ucm-conf libasound2 libasound2-data libopus0 libpipewire-0.3-0 libpipewire-0.3-modules libsndfile1
  libspa-0.2-modules pipewire-bin
Suggested packages:
  libasound2-plugins alsa-utils opus-tools
The following NEW packages will be installed:
  alsa-topology-conf alsa-ucm-conf libasound2 libasound2-data libopus0 libpipewire-0.3-0 libpipewire-0.3-modules libsndfile1
  libspa-0.2-modules pipewire pipewire-bin
0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
DebianStable

Code: Select all

$ vrms

No non-free or contrib packages installed on debian!  rms would be proud.

seeker5528
Posts: 61
Joined: 2021-09-18 00:37
Been thanked: 2 times

Re: Pipewire error

#3 Post by seeker5528 »

In addition to xdg-desktop-portal make sure you have dbus-user-session installed, dbus-user-session is the default dependency when xdg-desktop-portal gets installed, but if for some reason you already had dbus-x11 that also satisfies the dependency so dbus-user-session would not get pulled in.

There is a bug report that looks like the same issue that provides this information.

https://bugs.debian.org/cgi-bin/bugrepo ... bug=982853

mm3100
Posts: 336
Joined: 2020-10-21 21:39
Has thanked: 8 times
Been thanked: 13 times

Re: Pipewire error

#4 Post by mm3100 »

Looking it up I already have dbus-user-session installed, so no luck on that side. I don't use pipewire for audio, it was automatically installed with KDE.

seeker5528
Posts: 61
Joined: 2021-09-18 00:37
Been thanked: 2 times

Re: Pipewire error

#5 Post by seeker5528 »

The things KDE that look like they depend on pipewire stuff is kwin-wayland and krfb which depend on libpipewire-0.3-0 which depends on libspa-0.2-modules.

Unless there is an indirect dependency I missed or you have other software that depends on pipewire stuff, everything else related to pipewire that was pulled in as a recommended package could be purged, to see if that gets rid of the errors.

When you are not using it for audio, pipewire only gets used for some remote desktop/screen sharing stuff, and if you are not running in a Wayland session, these probably will allow use of other options.

My journalctl-fu is a bit lacking some relevant things here seem to be..

Code: Select all

journalctl --no-hostname --user -eg pipewire
journalctl --no-hostname --user -u pipewire
journalctl --no-hostname --user -eg desktop-portal
journalctl --no-hostname --user -eg dbus
See if one of these shows something telling.

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 462 times

Re: Pipewire error

#6 Post by sunrat »

Code: Select all

journalctl -b -p3 | grep pipewire
Sep 26 09:40:25 bullseye-brain pipewire[689]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
I get that same error. Pipewire is not running by default in Bullseye so it is inconsequential.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

Post Reply