From: notthewave <notthewave@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pipewire does not work after suspend
Date: Sun, 23 Jan 2022 21:35:41 +0100 [thread overview]
Message-ID: <20220123203541.y-xa1w4OPpzxezcHBkZwXHAMy7hcr2W1e_qN-G1eCKo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35206@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
New comment by notthewave on void-packages repository
https://github.com/void-linux/void-packages/issues/35206#issuecomment-1019561868
Comment:
The only thing Pipewire reports after suspend is:
```
[W][27921.874134] spa.bluez5 | [ bluez5-dbus.c: 1352 device_update_props()] unknown adapter /org/bluez/hci0
```
dmesg reports:
```
pipewire-media-[28789]: segfault at 44 ip 00007fbe3e59590c sp 00007ffdc6c4c3f0 error 4 in libspa-bluez5.so[7fbe3e56d000+65000]
```
also noticed that my controler does not get detected with bluetooth not sure if it's related
next prev parent reply other threads:[~2022-01-23 20:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 18:28 [ISSUE] pipewire crashes " notthewave
2022-01-23 19:02 ` pipewire does not work " Duncaen
2022-01-23 19:26 ` paper42
2022-01-23 19:43 ` Duncaen
2022-01-23 20:34 ` notthewave
2022-01-23 20:35 ` notthewave [this message]
2022-01-24 11:07 ` ar-jan
2022-01-24 11:23 ` ar-jan
2022-01-24 11:55 ` notthewave
2022-01-24 18:36 ` paper42
2022-01-28 2:07 ` notthewave
2022-01-29 17:42 ` st3r4g
2022-01-29 17:43 ` st3r4g
2022-02-03 3:13 ` tornaria
2022-02-03 18:09 ` ar-jan
2022-02-05 0:18 ` hervyqa
2022-02-05 0:18 ` notthewave
2022-02-05 0:18 ` [ISSUE] [CLOSED] " notthewave
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=20220123203541.y-xa1w4OPpzxezcHBkZwXHAMy7hcr2W1e_qN-G1eCKo@z \
--to=notthewave@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).