My best guess is that you forgot the -f parameter to qemu-img.
My best guess is that you forgot the -f parameter to qemu-img.
You are giving me the impression that Waypipe is an extension to Wayland like XRANDR is to the X11 protocol. I didn’t get that impression from the blogpost. I’m not trying to place value on them being an extension or a separate tool. I’m just trying to figure out if it was a shortheaded response or if Waypipe is an extension to the Wayland protocol.
An AppImage can be sandboxed.
Just to clarify. The gi://
resources are GObject Introspection modules which are used for multilanguage bindings to native libraries. On my system, GI modules are found in /usr/share/gir-1.0/
. They’re just imported by name and sometimes version using gi://
(there are examples in the link in my first comment).
As I don’t have Gnome installed I can’t be sure of the path to gnome shell modules imported using resource://
, but it’s probably the path I wrote, but without js/
.
It is very likely the wrong path, I just extrapolated the path from the gnome-shell git repo. I don’t use Gnome myself, I’m on the enemy team using LXDE on Devuan ;)
I edited my comment with an example for your code and my best advice for figuring out the path of gnome shell imports is by browsing /usr/share/gnome-shell/js/
, the docs are not very helpful.
GNOME Shell 45 moved to ESM (ECMAScript modules). That means you MUST use the standard import declaration instead of relying on the previous imports.* approach.
https://gjs.guide/extensions/upgrading/gnome-shell-45.html
So the imports in your extensions is changed from:
const Clutter = imports.gi.Clutter;
const Gio = imports.gi.Gio;
const Main = imports.ui.main;
const Volume = imports.ui.status.volume;
to
import Clutter from 'gi://Clutter';
import Gio from 'gi://Gio';
import * as Main from 'resource:///org/gnome/shell/ui/main.js'
import * as Volume from 'resource:///org/gnome/shell/ui/status/volume.js';
You want Gobby
That’s the funniest thing I’ve heard in a -1 years!
Hey I thought you we’re going to use it on an N900! :P
…and which one would that be?
You’re looking for what’s called reproducible builds.
One shitty thing can be better than another shitty thing.
If you’re thinking of the EU, it’s probably just the vogonlike bureaucracy, so in about the time that Windows 12 comes out, they’ll be ready. Can’t say it bothers me, if Microsoft is attempting to take marketshare from Google, though.
I must admit I copy paste the link to the terminal, so it’s not a seamless experience. I don’t watch enough videos to have done anything other than write a wrapper script with my preferred settings for youtube videos and to convert invidious links to youtube links.
I just tried running mpv --idle=yes --force-window=yes
from the terminal and drag a youtube link to the window. It plays like it should. yt-dlp
is installed locally for my user in ~/.local/bin
and that directory is appended to the PATH
environment variable. I also have yt-dlp
symlinked to youtube-dl
for mpv to pick it up. I guess what’s missing is my preferred options for youtube videos, which I could set up in ~/.config/mpv/mpv.conf
. Everytime some site breaks, you run yt-dlp -U
to update and cross your fingers.
Yes, use what you know. Neither LXLE nor LXDE are end of life as claimed in other comments. The latest LXLE release is supported until 2030, which is five years longer than Windows 10.