Sebastian Krzyszkowiak @dos@librem.one

@jwz This one is a simple nested compositor indeed, as that's what was easy to do with the available ready-made building blocks :) But technically it doesn't even have to be a "compositor" at all to do this. Wayland itself is a buffer-passing protocol with some optional extras on top after all, so it could pass the client's wl_buffer straight to the server.

@pup Sure, as soon as I tame the build system and move what's hardcoded to config options.

@jwz This is Plasma specific - it's effectively making kscreenlocker outsource its background rendering to another process, which doesn't even have to be aware that it's being used as a screensaver (or a wallpaper, it's the same there). That said, there's no reason other DEs couldn't handle it the same way. A ext-session-lock-v1 locker could also become a simple compositor like this and just pass the buffer forward.

How it works? It's a Plasma wallpaper plugin which is an extremely simple QtWayland compositor that only handles a single fullscreen window and draws it - so any Wayland window can be drawn as a background. This window can of course also belong to Xwayland 😄

This means we can go beyond xscreensaver. How about... Wine? 😁

#plasma #kde #xscreensaver #wayland #x11 #qtwayland #qml #qtquick #gnu #linux #wine

I had a random thought - "what would it take to support arbitrary old screensavers in Plasma 6 again?" 🤔 So here's xscreensaver safely rendered as a background for Plasma screen locker, working on both Wayland and X11 sessions. Turned out so much simpler than I expected 😁 Just some 70 lines of pure QML and a tiny glue to launch the process.

#plasma #kde #xscreensaver #wayland #x11 #qtwayland #qml #qtquick #gnu #linux

@debacle @opensourceopenmind @jonah It's the PinePhone Pro that's discontinued, not the regular PinePhone, isn't it?

taking daily pills be like:

(drawing from @holypangolin's game Karambola)

@pocketvj It's for Teseo LIV3F.

@pocketvj @opensourceopenmind @enriquericos OLS doesn't make GPS fixes faster, it just provides alternative methods to estimate location (just like Geoclue does with BeaconDB as well).

@agx @ev Yeah, that's the one thing I miss in git gui. I find what's there to be enough most of the time, but sometimes it just stubbornly doesn't want to put the line where it belongs when splitting a bigger change into smaller commits 😄 But it's still valuable to me to be able to quickly browse both staged and unstaged changes and to non-destructively switch between authoring a new commit and amending the previous one with a single checkbox click.

@opensourceopenmind @enriquericos It's not integrated in the OS, but you can get fast fixes by uploading fresh AGNSS data to the module manually: https://source.puri.sm/-/snippets/1207 #librem5

@agx @ev That's what I typically use for interactive staging (right-clicking on diffs) - I think it's the only git operation that's usually more comfortable to do from a GUI for me

@robot @ipg Slightly less horrifying when you remember that Lumia 800 inhabits N9's body.

@fizzo (although many other devices have a dedicated piece of hardware to do this and more for you)

@fizzo Nothing sensor-specific there (except calibration data of course), just doing very basic stuff that you need to do in order to get a proper image from any Bayer sensor (unless it does parts of it for you already). See the description at https://source.puri.sm/-/snippets/1223 for details.

scratchy scratchy #catsofmastodon #shotonlibrem5

@hoolis @sos You may want to grab the version from https://github.com/TheSos/allegrojs/pull/25 which fixes some crashes and lets you use raf-based mainloop