๐Ÿ’พ Archived View for station.martinrue.com โ€บ gnuserland โ€บ 3433c297fd234855a686f21e14429b20 captured on 2024-05-10 at 13:12:34. Gemini links have been rewritten to link to archived content

View Raw

More Information

โฌ…๏ธ Previous capture (2023-01-29)

๐Ÿšง View Differences

-=-=-=-=-=-=-

๐Ÿ‘ฝ gnuserland

Lagrange 1.4 (Flatpak, Debian Testing, XFCE, default Fireforx) gets stuck while try to open a HTTP/HTTPS link, are you experiencing the same?

3 years ago

Actions

๐Ÿ‘‹ Join Station

4 Replies

๐Ÿ‘ฝ skyjake

Glad to hear you like it! ๐Ÿ™‚ Properly supporting Flatpak would be much easier for, say, a GTK app. Since I've chosen to forge my own path, so to speak, it's going to require more work to get everything working in the sandbox. These adaptations will be generally useful for improved FreeDesktop compatibility, but in practice there are many other things on the todo list that take priority. ยท 3 years ago

๐Ÿ‘ฝ gnuserland

@skyjake Thank you very much! I was thinking the same, anyway I love Lagrange! Thank you very much for this great Gemini Client! ยท 3 years ago

๐Ÿ‘ฝ skyjake

Did some testing. For me it seems the Flatpak sandbox is blocking the opening of the default browser (via an `xdg-open` subprocess), but it doesn't get stuck. Looks like this is another case where Flatpak will need a special workaround (the other being the IPC mechanism that is also broken under Flatpak). I'll have to see if it's possible to get an exception that allows executing `xdg-open`.

In the meantime, I recommend using the AppImage if that works for you. It doesn't have sandbox restrictions so both IPC and `xdg-open` should work just fine. ยท 3 years ago

๐Ÿ‘ฝ krixano

@skyjake ยท 3 years ago