@fiacco: In general, bugs should be reported by issues at Github. Otherwise, it is by chance that I discover them. OK, looks like Mapbox map is not working. Can you try some raster map tiles? Like HERE or OpenCycleMap?
I did move Pure Maps to Qt 5.15 a day or two ago. I wonder if we are again hitting some Mesa issue or something is terribly wrong in the build. (Working to fix OSM Scout Server build on the same Flatpak runtime).
As for Debian packaging, so far I have only heard of interest but haven’t seen it packaged. There is a significant amount of dependencies that actually allow me to deliver such map application.
@fiacco: thank for testing. Would you mind testing with offline mode as well using OSM Scout Server? Mapbox and offline maps use vector tiles and could stress GLES more than raster maps. So, would be interesting to know whether it is only Mapbox (more complicated style) or OSM Scout Server maps as well.
In addition, check if with raster maps you can see
POIs (such as search results)
routes (after routing calculation)
Would be great if someone could check your breakage with Pure Maps. As in your case, without the cache if something is broken.
Using OSM Scout Server I get the same map (with different font).
With raster map (tried OpenCycle and OpenTopo) I get POIs after a search, but I cannot see graphically a route, even if apparently has been calculated it, because I can see “circles” POI along the route.
@fiacco: thanks for testing! This sounds like a bug coming from GLES stack (Mesa, kernel) which got triggered by a new Flatpak platform.
Have you tested with LIBGL_ALWAYS_SOFTWARE=1?
If my suspicion is right, it is not something I can fix on Pure Maps side but has to be fixed in L5 drivers (or interaction with Mesa on Flatpak). So, there is no point in opening an issue at Pure Maps Github repo.
Please do the test with software-based rendering and then let’s report an issue via Matrix L5 channel.
Running from terminal LIBGL_ALWAYS_SOFTWARE=1 flatpak run io.github.rinigus.PureMaps PureMaps starts with the usual nice map. But it’s very slow, almost unusable.
@fiacco: thanks a lot for testing. Yes, HW acceleration is needed to be able to show the map. I have a feeling sometimes that Pure Maps is an only app that is pushing GLES on L5 or PinePhone as it is regularly hitting some bugs in drivers. I’ll notify L5 devs.
Could you tell us where you posted? Maybe as more PureMaps users get their L5s, we could lend our support. (I looked for an issue on Purism’s GitLab, but couldn’t find anything.)
May be worth it to open an issue on Purism’s GitLab?
I am particularly interested in solving this issue, and so should Purism be. Pure Maps is an app that makes the difference. A popular question asked by people when I show my L5 is: “yes, nice, but … do you have a replacement for Maps?”
I’m not suited to open the request, not knowing exactly what to ask, so I’d have a volunteer do it
