Github messages for voidlinux
 help / color / mirror / Atom feed
From: jconnolly837 <jconnolly837@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] MPV '!impl->polling' failed at ../spa/plugins/support/loop.c:872 impl_clear()
Date: Tue, 29 Nov 2022 23:14:35 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40849@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]

New issue by jconnolly837 on void-packages repository

https://github.com/void-linux/void-packages/issues/40849

Description:
### Is this a new report?

Yes

### System Info

Void 6.0.10_1 x86_64 GenuineIntel uptodate rFFFFF

### Package(s) Affected

mpv-0.35.0_1 pipewire-0.3.58_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://github.com/mpv-player/mpv/issues/10859

I suggest the Pipewire package on Void be updated to 3.60, as mentioned in the other issue on the MPV github. 

### Expected behaviour

MPV opens and follows instructions

### Actual behaviour

MPV outputs the following:

```
[james@Void9020 ~]$ mpv 'https://www.youtube.com/watch?v=8VoVjNlL_FI'
 (+) Video --vid=1 (*) (vp9 1920x1080 30.000fps)
 (+) Audio --aid=1 --alang=eng (*) (opus 2ch 48000Hz)
File tags:
 Uploader: Brodie Robertson
 Channel_URL: https://www.youtube.com/channel/UCld68syR8Wi-GY_n4CaoJGA
[ao/pipewire] Could not connect to context '(null)': Host is down
'!impl->polling' failed at ../spa/plugins/support/loop.c:872 impl_clear()
Aborted
```
Applies to local media files too. 

### Steps to reproduce

1. Make sure MPV and Pipewire are on the specified versions in this ticket.
2. Attempt to open media with MPV
3. MPV fails with the above error. 

             reply	other threads:[~2022-11-29 22:14 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 22:14 jconnolly837 [this message]
2022-11-30 10:11 ` zenny
2022-11-30 12:12 ` kruceter
2022-12-01 10:15 ` zenny
2022-12-01 10:18 ` zenny
2022-12-01 10:19 ` zenny
2022-12-01 11:25 ` kruceter
2022-12-01 12:53 ` zenny
2022-12-01 12:54 ` zenny
2022-12-01 12:59 ` paper42
2022-12-01 13:34 ` zenny
2022-12-01 13:40 ` zenny
2022-12-01 13:51 ` zenny
2022-12-01 14:24 ` zenny
2022-12-01 14:27 ` zenny
2022-12-01 14:33 ` paper42
2022-12-01 14:58 ` zenny
2022-12-01 14:59 ` zenny
2022-12-01 14:59 ` paper42
2022-12-01 15:10 ` zenny
2022-12-02  9:26 ` zenny
2022-12-03  6:17 ` kruceter
2022-12-03 15:29 ` [ISSUE] [CLOSED] " jconnolly837
2022-12-03 15:29 ` jconnolly837

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40849@inbox.vuxu.org \
    --to=jconnolly837@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).