This project is currently in a very early stage of development. Kando is not yet a functional menu but rather a prototype which demonstrates the feasibility of the concept.
Since Kando is still in early development, it might be a good idea to look at the Gnome Extension Fly-Pie. It’s from the same developer and it looks like Kando will be similar.
Dope, thank you for posting. Been using ‘Core CTRL’ for quite awhile but Imma give this a rip. For some reason the former tool never could control the fan curve for my GPU (all the other fans in the box worked fine with it) so this might be profit.
I have been working on Fly-Pie for more than 3 years now and I am very happy with the result. However, I have always wanted to create a similar application for the desktop in general. This is why I started this project.
The big advantage for me is that lact runs as a (systemd) daemon. This is more convenient for me than having to autostart CoreCtrl.
A disadvantage of the daemon is that it can’t be packaged on flathub.
Enable and start the service (otherwise you won’t be able to change any settings): sudo systemctl enable --now lactd
You can now use the GUI to change settings and view information.
The stalebot is most times useless. The only scenario where I can see use of it is a maintainer waiting for the reporter to add information. But closing issues because no maintainer checked on them? That’s garbage and discourages bug reports.
After a extremely long week, I sometimes participate in open source. I have to deal with malicious commits. I have to follow up on issues from misguided individuals who are actually looking for tech support. I have to guide new contributors to how this massive repo works and to submit tests. I have to negotiate with the core team and these convos can often last months/years.
And contributing to open-source is one of the few things that give me pleasure, even if it’s a extremely thankless job.
But I’m tired man.
I’m not dealing with low-quality memers who are providing zero value. Nor should we encourage it.
I do FOSS as well, but I’d rather people have fun punting the stalebot than just keep repeating “this issue still exists”. I will probably get a chuckle out of it.
I actually see a legitimate use case for it and helped add the actions version in a project where I'm a collaborator.
Quite a bit, certain bugs disappear after an update without us targeting it (partially because the logs get fudged a bit after going through dependencies, so sometimes multiple bugs have the same cause or it's actually a dependency issue that got fixed) and sometimes we forget about old feature requests.
The stale reminder doubles as a reminder for us to (re)consider working on the issue. When we know something probably isn't gonna get fixed suddenly, we apply a label to the issue. For enhancements that we'll definitely work on soon™, we apply help wanted. We've configured the action to ignore both. We also patrol notifications from stale to see if something shouldn't go stale. This is a medium-sized project so we can handle patrolling and IMO this helps us quite a bit.
Fair enough; I didn’t consider artifacts like logs and traces. I suppose a stale marker might prompt the original reporter to retest and supply fresh ones (or confirm it’s fixed in the dependency case).
In an ideal world I suppose we’d have automated tests for all bug reports but that’s obviously never going to happen!
Is it possible to get this to work with OBS studio? I see the author mentions OBS as an “Alternative Project” but it seems ideal to have these pieces work together.
Not really. I’ve had to do quite a bit of experimentation.
My setup that I’ve settled on:
Rocm system libraries from Arch Linux
PyTorch nightly for Rocm pip installed into a venv (see instructions on pytorch homepage)
Set HSA_OVERRIDE_GFX_VERSION to 11.0.0. This is just for the RX7600 and it tells it to use the RX7900 code as the pytorch version hasn’t been compiled with 7600 support.
Hmm, that’s weird. I was able to run Stable Diffusion locally with Linux + RX6600.
Probably because I used Easy Diffusion. At first, I couldn’t get the GPU acceleration to work, and I was constantly running out of RAM (Not using VRAM), so my system always froze and crashed.
Turns out it was a ROCM bug, that I don’t know if it’s fixed by now, but I remember “fixing it” by setting an environment variable to a previous version.
Then, it all worked really good. Took between 30 seconds to 2 minutes to make an image.
github.com
Newest