Sam Black

~/code/git/<org name>/<project>

Mostly a holdover from when I regularly pulled svn/hg/cvs repos and needed reminding what tool to use for which project.

No idea why I still do it.

Sorry for not replying sooner, life stuff.

I’ve had problems with the 555 driver like KDE’s lock screen would freeze for up to 30 seconds whilst trying to unlock and resuming from suspend resulted in a black screen.

So I went back to the 550 driver - I’ve uploaded the RPMs/SRPMs that I use; https://misc.lapwing.org/rpms/nvidia-550/

Please note this is just a dump of RPMs/SRPMs and not a repo, so it’s just a stop gap until 560 arrives and (hopefully) fixes my issues.

You will probably have to fight dnf a bit to get it to actually replace the 555 RPMs, but I’ve not had a recurrence and the akmod dance works just as jankily well as before.

The GNOME extension appears to get the currently focused window information (ie name, title, PID and executable name) and make this information available over DBUS for the client binary.

The client binary calls gnome-screenshot -f and I assume gives a path that the client binary then sends to Hubstaff servers.

A janky suggestion would be to create a Kwin Script that pulls the active window information, sends it (somehow) to a DBUS service that can provide it to the client binary and create a wrapper script around spectacle to pretend to be gnome-screenshot (eg spectacle -b -f $@)

I don’t know if this would work fully though as the client binary strings seem to hint it checks the running version of GNOME Shell, and without an account I can’t see if this is a hard requirement or a “Hey, this is broken, we’ll try our best!” type thing.

I found CryFS, the default encryption used, to become unusable if the vault is more than a few gigs in size* - gocryptfs works without issue.

* No, you dirty minded people, I use Vaults for client information at work, not what you were thinking of.

You can start it with systemctl start podman-auto-update.service It’ll auto update daily at 00:00.

Be aware you need to enable and start podman-auto-update.timer for this to work automatically (ie systemctl enable --now podman-auto-update.timer), this command will just update the images once only.

I don’t think this works for non-system podman images, so you’d have to do systemctl --user enable --now podman-auto-update.timer for each user.

You can use RequiresMountsFor= (eg RequiresMountsFor=/media/storage-volume1) instead of manually adding .mount to After/Requires - you can then use .mount files or fstab as you’re stipulating the path rather than a potentially changeable systemd unit name.

The systemd.mount manpage also strongly recommends using fstab for human added mount points over .mount files.

The 6.5 kernel should have the fix for this included, so you could try using that kernel instead of 6.1?