Bug 490468

Summary:	No video load using the Piped backend: "[file] Cannot open file '': No such file or directory"
Product:	[Applications] PlasmaTube	Reporter:	Bart Ribbers <bribbers>
Component:	general	Assignee:	Linus Jahn <lnj>
Status:	REPORTED ---
Severity:	normal	CC:	argo5, bmhieserich, espidev
Priority:	NOR
Version First Reported In:	24.04.90
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Bart Ribbers 2024-07-18 19:09:30 UTC

With Plasmatube built from git master today no videos load using the Piped backend.
In the console I see "[file] Cannot open file '': No such file or directory" whenever I click on any video.

Interestingly enough 24.05.0 on my desktop using the same Piped backend and instance loads the video just fine (but then I get https://bugs.kde.org/show_bug.cgi?id=486707 preventing me from playing the video but that's a separate problem).

Comment 1 bmhieserich 2024-08-31 17:51:15 UTC

Confirm this same error happens also using Invidious. Subscriptions also update only sporadically and not accurately as well, but that's also a separate issue and may be related to Invidious itself and not PlasmaTube.

Comment 2 argo5 2024-11-01 11:31:43 UTC

This still happens on 24.08.2 Flatpak. I'm using a functioning Invidious instance.
Here's the error from a random video

[file] Cannot open file '': No such file or directory
Failed to open .
Error for QNetworkReply::ServiceUnavailableError QUrl("https://inv.nadeko.net/api/v1/videos/T3rnBuSTNhY") "Error transferring https://inv.nadeko.net/api/v1/videos/T3rnBuSTNhY - server replied: "
VideoModel::fetch(): Error: "Error transferring https://inv.nadeko.net/api/v1/videos/T3rnBuSTNhY - server replied: " QNetworkReply::ServiceUnavailableError
Failed to fetch comments: "Server returned no valid JSON."

I suspect the issue is somewhere in https://invent.kde.org/multimedia/plasmatube/-/blob/master/src/api/invidious/invidiousapi.cpp
This is specifically a problem with how Plasmatube handles the /videos endpoint I think, because the homepage and such work fine.
Unfortunately I don't have the right environment to try and debug it right now.