Description of problem: mga8-rc /usr/lib/tmpfiles.d/pipewire.conf:2: Line references path below legacy directory /var/run/, updating /var/run/pipewire â /run/pipewire; please update the tmpfiles.d/ drop-in file accordingly. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. journalctl --no-hostname | grep pipewire 2. 3.
Source RPM: pipewire-0.2.6-1.mga7.src.rpm => pipewire-0.3.16-3.mga8
Hi, i installed pipewire, but i don't see any /usr/lib/tmpfiles.d/pipewire.conf file.
CC: (none) => mageia
Ah, balderdash. I am sorry, I have a self healing script that detects missing home directories, and creates /usr/lib/tmpfiles.d/ conf file if missing directory and had completely forgot about it. I have deleted /usr/lib/tmpfiles.d/pipewire.conf and rebooted. # pwck -r user 'pipewire': directory '/var/run/pipewire' does not exist pwck: no changes So, the question is, close this bug report and open a new one about missing home directory or modify the title to missing home directory, Also found this # journalctl --no-hostname | grep pipewire Jan 09 18:33:09 systemd[9681]: pipewire.socket: Succeeded. Jan 09 18:34:05 pipewire[2057]: Could not get portal pid: Argument 0 is specified to be of type "uint32", but is actually of type "string" Jan 09 18:34:27 pipewire[2362]: Could not get portal pid: Argument 0 is specified to be of type "uint32", but is actually of type "string" # systemctl status pipewire.service Unit pipewire.service could not be found. # systemctl status pipewire.socket Unit pipewire.socket could not be found.
Latest pipewire rpm might need a post-intall trigger to change home directory from /var/run to /run. Manually changed /etc/passwd, cleared journal, reboted # journalctl --no-hostname | grep pipewire Jan 10 00:00:04 pipewire-media-session[2366]: core 0xfd7bb0: proxy 0xfd7bb0 id:0: bound:-1 seq:28 res:-32 (Broken pipe) msg:"connection error" Jan 10 00:00:04 systemd[2349]: pipewire.service: Succeeded. Jan 10 00:00:04 systemd[2349]: pipewire.socket: Succeeded. Jan 10 00:00:04 systemd[2010]: pipewire.service: Succeeded. Jan 10 00:00:04 systemd[2010]: pipewire.socket: Succeeded. Jan 10 00:00:59 pipewire[1941]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name Jan 10 00:01:17 pipewire[3632]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name ]# systemctl status pipewire.service Unit pipewire.service could not be found. ]# systemctl status pipewire.socket Unit pipewire.socket could not be found.
Source RPM: pipewire-0.3.16-3.mga8 => pipewire-0.3.19-1.mga8
See the same: pipewire[1941]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name with pipewire-0.3.19-1.mga8 Change the title bug.
Keywords: (none) => TriagedSummary: pipewire.conf: Line references path below legacy directory /var/run => pipewire complains at boot twice "Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name"Target Milestone: --- => Mageia 8Assignee: bugsquad => thierry.vignaudCC: (none) => ouaurelienVersion: 8 => Cauldron
As there have not been more activity here i assume problem is no more. And mga8 is since long EOL.
Status: NEW => RESOLVEDResolution: (none) => FIXEDCC: (none) => fri