[JamesIs]

As per title. I've upgraded (through my release repository) to 21.0-4, and not changed anything else, but now nothing will play (no films, no music). These are local files on either the same drive as Kodi is installed.

I've tried clearing the cache, I've deleted and rebuilt all the databases, deleted advancedsettings.xml (just in case), reverted to the default skin unmodified, removed all add-ons (except those installed as part of a fresh install).

It's nothing wierd about my profile because I have two separate user accounts on my PC and Kodi is having the same error on both.

I've enabled debudding, but all I'm getting in the log is

Code:

CPipewireStream: failed to connect stream: Unknown error -22

which isn't very helpful. I've checked my Pipewire settings just in case, but they all are as before and other sound output is working fine.

[Hitcher]

To receive meaningful assistance you will need to provide a full debug log.

The instructions are here... debug log (wiki)

If you are using the Basic Method, then ensure the following is applied...
1.Enable debugging in Settings>System Settings>Logging,
2.Restart Kodi
3.Replicate the problem.
4.Upload the log to Kodi Paste Site manually or use the Kodi Logfile Uploader. (wiki) With either method post the link to the log back here.

If you are using the Advanced Method ensure you have correctly created and applied the advancedsettings.xml file (wiki)

In both instances, you should see the word DEBUG throughout the log.

Note: Full logs only. No partial or redacted logs
Do NOT post your logs directly into the forum. Use the Kodi Paste Site. Post the link to your pasted log in the forum

[JamesIs]

OK. Well thanks for the offer anyway. I prefer not to post full logs as they contain information I'd rather keep private and/or information which I don't know whether I want made public or not.

I appreciate you have your preferred methods and restrictions.

[jjd-uk]

Where exactly do you get Kodi from? does it happen to be the Flatpak version? As there been issues with Pipewire using the Flatpak Kodi version on Ubuntu.

[JamesIs]

Where exactly do you get Kodi from? does it happen to be the Flatpak version? As there been issues with Pipewire using the Flatpak Kodi version on Ubuntu.

Interesting. I just upgraded directly from my distro repositories (Manjaro), so no, not Flatpak. But it seems an odd coincidence. I checked out the bugs and it seems likely. From https://github.com/xbmc/xbmc/pull/25019 I get

> Due to multiple reports on the forum it seems the certain pipewire installations (ARCH Linux, flatpak users) do not cope very well with the pipewire setup.

Manjaro is an Arch-based distro, so...

[jjd-uk]

Yes that's exactly the issues I was thinking of, I thought it had been primarily Flatpak affected, but I'm not a Linux user so not fully aware of all the ins and outs. The change that happened with v21 is Pipewire would be used as default if detected, but my very limited understanding is not all distros that include Pipewire as standard have it setup in a manner compatible with Kodi.

[JamesIs]

Yes that's exactly the issues I was thinking of, I thought it had been primarily Flatpak affected, but I'm not a Linux user so not fully aware of all the ins and outs. The change that happened with v21 is Pipewire would be used as default if detected, but my very limited understanding is not all distros that include Pipewire as standard have it setup in a manner compatible with Kodi.

Well, it was worth a try. I started kodi with ALSA

Code:

kodi --audio-backend=alsa

and the settings confirmed no PipeWire, but the problems persisted. With ALSA I could select any number of different devices, but none of them made any difference. I think the issue might only be a coincidence. Oh Well.

[jjd-uk]

Then I'm not sure we can do much to help without a Debug Log. Note that we do attempt to redact anything that appears to be personal infomration such as passwords in the logs, and if you're still worried then can't you check it before uploading? if you shut Kodi down and then restart Kodi to start a fresh log and then immediately try to play something to replicate problem and then close Kodi down again, then the log shouldn't be too many lines for you to sanity check of any personal info.

[JamesIs]

Then I'm not sure we can do much to help without a Debug Log. Note that we do attempt to redact anything that appears to be personal infomration such as passwords in the logs, and if you're still worried then can't you check it before uploading? if you shut Kodi down and then restart Kodi to start a fresh log and then immediately try to play something to replicate problem and then close Kodi down again, then the log shouldn't be too many lines for you to sanity check of any personal info.

I appreciate that. I'm happy to check though, but then I'd have a "redacted log", which the instructions forbade. I've made the cleanest log I can, just a single operation (trying to play a film). I've replaced a bit of personal information. Kodi wouldn't exit properly, so I had to kill the window, but that was all after the film failed. Left click on the film title is at line 592, if that helps.

I've posted the log here then, if anyone is still able to help despite redactions...

[jjd-uk]

The "redacted log" thing is for where people attempt to hide their piracy addons by removing the statup portion of the log where installed addons are displayed. As long as there are not big time gaps in the log suggesting something fishy might be going on, then small redactions are perfectly fine.

[JamesIs]

Thanks for explaining. It may have been missed in my previous post but I have done as suggested and posted a redacted log.

http://paste.kodi.tv/tutexazemu.kodi

Does this provide any ideas?

[Hitcher]

Is it the same for non-ISO videos?

[JamesIs]

Is it the same for non-ISO videos?

Some. I've checked some other file types -  .avi and .mov both work, but other movies don't (I don't know what they're called, I'm afraid, but they're the ones where there's a {file}.vob inside a folder with audio - recorded directly from a dvd).

So it seems anything originating from a DVD doesn't work.

[JamesIs]

So following your lead on the file types, I found this

https://github.com/xbmc/xbmc/issues/24955

and looking there I have the same issue with dll_fstatvfs64 as they have (line 644 in my log)

[emveepee]

Try new source after this merge https://github.com/xbmc/xbmc/pull/24964

Martin