From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Possibly missing shared object file in wireplumber package
Date: Sat, 04 Feb 2023 00:11:20 +0100 [thread overview]
Message-ID: <20230203231120.xLFVFCm0OpAV2gXdQHewxl8I-D5FfO_YCU9unue3rtU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42056@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
Closed issue by Adailoe on void-packages repository
https://github.com/void-linux/void-packages/issues/42056
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.8_1 x86_64 AuthenticAMD uptodate FFFFFFF
### Package(s) Affected
wireplumber-0.4.13_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
The package might be missing the libwireplumber-module-logind.so - file.
It is present in the Arch Linux version but not in Void.
### Actual behaviour
Wireplumber is complaining about that missing file when trying to connect to pipewire and fails to connect.
```
m-lua-scripting ../modules/module-lua-scripting/api/config.c:80:load_components: Failed to open module /usr/lib64/wireplumber-0.4/libwireplumber-module-logind: /usr/lib64/wireplumber-0.4/libwireplumber -module-logind.so: cannot open shared object file: No such file or directory.
Failed to connect to PipeWire
```
The pipewire media-session is not active. ( difference to issue https://github.com/void-linux/void-packages/issues/37683 )
### Steps to reproduce
1. Install wireplumber
2. Change the pipewire-configuration according to https://github.com/void-linux/void-docs/pull/738/files
3. Reboot
4. Open terminal and execute `$ wireplumber`
next prev parent reply other threads:[~2023-02-03 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 17:21 [ISSUE] " Adailoe
2023-02-03 17:25 ` paper42
2023-02-03 19:00 ` Adailoe
2023-02-03 22:34 ` paper42
2023-02-03 23:11 ` [ISSUE] [CLOSED] " paper42
2023-02-03 23:11 ` paper42 [this message]
2023-02-04 5:42 ` oreo639
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230203231120.xLFVFCm0OpAV2gXdQHewxl8I-D5FfO_YCU9unue3rtU@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).