codema.in
Thu 15 May 2025 8:22AM

FreeTube display issues with flatpak (might be GTK4 dropping GLES 2 support)

PP Pirate Praveen Public Seen by 8

FreeTube works well on FLX1 but broken on Librem 5. More details in https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/11

I think a native youtube app is an important part of being able to daily drive gnu/linux on mobile. Android has NewPipe and PipePipe which works well. Being able to play audio only makes it a music player for many.

This would likely need adding missing GLES 3 features to mesa etnaviv driver.

Update: This looks like an upstream bug with the flatpak build https://github.com/FreeTubeApp/FreeTube/issues/5919

Or it might actually be GTK4 issue if flatpak has switched to newer GTK

G

Guido Thu 15 May 2025 9:05AM

I think you're mostly asking for "Please support GLES3 on the Librem 5" which is something Purism should help to support not primarily the community as without it the device becomes pretty unusable soon.

EDIT: This is becoming more and more a "let's keep the Librem 5 alive" tracker which is fine in the first place but shouldn't that then be written on the tin (rather than branding it a s Mobian / Debian / Phosh ) ?

PP

Pirate Praveen Thu 15 May 2025 9:59AM

@Guido I use both Librem 5 and FLX1 and it is natural I will be reporting issues I see on these devices only (and FLX1 being more powerful, I don't see as many issues with it). If other people using other devices don't see any issues worth prioritizing through this effort, how is that a problem with Purism. Isn't it natural for community to step in when Purism is not doing it/taking a long time? Isn't that the whole spirit of Free Software?

BS

Badri Sunderarajan Fri 16 May 2025 2:39AM

@Guido just wanted to chime in to say I do plan to report things I come across on the Poco F1 too, just that I haven't had (made?) time to engage here of late.

I think it's a diversity issue, i.e. @Pirate Praveen is the most active here and he has a Librem 5, so naturally tends to report issues related to that. Perhaps this is a cue to encourage more people with varied devices to participate here? It is a chicken-and-egg situation, I agree, and hopefully completing some of the current "priority projects" would help there.

Edit: I meant "diversity" in terms of devices people use, in case that wasn't clear

G

Guido Sat 17 May 2025 9:32AM

@Badri Sunderarajan My point is/was that I thought this project was meant to collect funding for certain shortcomings affecting Mobile Linux not as a yet another bug tracker. And I wouldn't see how "Let's fix GLES3 in the Librem 5" fits in here due to the reasoning outlined above (and the probably more important fact that Christian is on it already) would fit in here. I would understand it, if we'd had someone interested on working on GLES3 on etnaviv but lacking funding but that doesn't seem to be the case. Anyway, as I failed several times to grasp what this is about and I don't want to derail discussions I'll just keep quiet from now on.

PP

Pirate Praveen Sun 18 May 2025 10:09AM

@Guido yes, but we first need to decide which projects need funding. This is part of that process. First stage is collecting bugs / missing features that people consider a blocker for daily driving the phone. There is no restriction here what types of bugs or missing features can be proposed. Each person participating in this group makes a personal prioritization. In second stage, we take all the suggested items to a poll and make a priority list. Once we have the priority list, we analyze each item and see if it needs funding. Some projects may already be in progress or has funding (like alarm waking up the phone from suspend or unified push). So those who come in the top priority list and need funding, we start a bounty and look for people to work. If people vote this issue as top priority and Christian is already working on it, we will just document that here as already in progress. So it is a curated list of bugs that are voted on by the community. Just proposing a bug for inclusion does not guarantee it will come to the top, only if majority of the people participating in the group consider a bug is a priority, that will get attention for funding. We will do priority polls periodically (no fixed schedule yet, currently if we see already identified issues are done or in progress and people have proposed new issues, then we can do another poll)

G

Guido Thu 15 May 2025 10:04AM

(and FLX1 being more powerful, I don't see as many issues with it)

It's not about the FLX1 being more powerful here it is about the FLX1 using proprietary GL drivers. To me this is a huge difference, especially when you talk about Free Software in the next sentence.

Isn't it natural for community to step in when Purism is not doing it/taking a long time? Isn't that the whole spirit of Free Software?

My understanding is that this project here is primarily about raising funding and I think Purism should be part of this when it would benefit largely from the efforts. They're marketing their devices at a premium price because the say this helps software development so I think they should be involved in supporting their hardware. (I'm of course not telling where people should spend their money, I'm still trying to figure out what dephcom is about)

PP

Pirate Praveen Thu 22 May 2025 10:49AM

@Guido As mentioned in previous comment, this is only first stage of the process (individuals proposing bugs or features that are important). We will move to next step of the process only after a poll that gives a chance to everyone in dephcom to vote and arrange the proposed bugs or features based on priority like we did earlier in https://codema.in/p/hcApNrxT/arrange-the-following-issues-based-on-priority. Purism is currently focusing on PureOS crimson and only when it moves to dawn, PureOS will be affected by this issue. Purism actually have to sell enough phones to be able to make a profit and invest in development.