This is a pretty known bug from what I noticed when searching for solutions earlier, and I’m quite sure someone already filed an issue?
I found a way to set the needed env var before Tauri starts, in case Nvidia devices are used. I can’t test it however. Version 0.2.0.r3.ga5d68cb-1 has it.
Works for me w/o any issues.
|Sat Mar 1 19:58:31 2025
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 570.124.04 Driver Version: 570.124.04 CUDA Version: 12.8 |
|-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce GTX 1050 Ti Off | 00000000:01:00.0 Off | N/A |
| N/A 52C P8 6W / 75W | 7MiB / 4096MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 956 G /usr/lib/Xorg 4MiB |
| 0 N/A N/A 19058 G garuda-rani 1MiB |
+-----------------------------------------------------------------------------------------+
╭─nepti@archangel in ~ took 0s
╰─λ pacman -Qs garuda-rani
local/garuda-rani-git 0.2.0.r3.ga5d68cb-1
Garuda's Reliable Assistant for Native Installations
That’s good to hear, thanks!
Yes. Thank you! This is it!)))
Sorry I had to do some stuff around the house.
Yes it works either with the ENV variable set or without on the version 0.2.0.r3.ga5d68cb-1 as mentioned by Nepti
╰─λ sudo pacman -Qs rani
local/garuda-rani-git 0.2.0.r3.ga5d68cb-1
Garuda's Reliable Assistant for Native Installations
╰─λ pacman -Qs rani
local/garuda-rani-git 0.2.0.r5.g9baace5-1
Garuda’s Reliable Assistant for Native Installations
it works …thx
Seems to be working fine now!
Sorry, but I got another one for you:
I tried to add these two features, even though I already have installed virtualbox:
There is no apply button, are all actions supposed to be executed in the provided terminal? When trying to do that, I get this:
And when trying to run only “Add user to group” separately I get this:
Haha, I’m glad for every QA done! The signal one seems like missing () and qemu-kvm… well I could swear this was was in repo. Will check it out tomorrow.
And yes, these are supposed to be executed in terminal. Is it unclear, or should there be another indicator for it?
I’m not sure if these will be needed but I made some place holder buttons? icons? Since that current one is a bit hard to see. They are just 512x512 svgs. For light and dark mode.
Maybe “Apply in terminal”. But idk, I feel like the average Garuda user would figure it out anyway…
Maybe text at the bottom that says something like “*These are being installed then enabled, a restart may be required”
but written better haha.
The app checks for virtualbox-meta rather than virtualbox only. In this case it would install the missing meta pacakge. Also removed the vbox kvm, it was very troublesome as it doesn’t work with the meta package (kernel module package requires the regular one).
Indeed, I passed a signal instead of its value. It is fixed now.
Especially with some dumb like me 
But rani works now, that’s what I call a quick fix, thanks guys !
I must say this notification features and way how its implemented and presented make me really happy
Really like this. Well done!
the autostart on boot is bugged and leaves me with a sweet catpuccin themed square, but the modules wont load.
This is WAY better and a LOT easier for new users!
also, big respect for the intergrated terminal
I have a question about the schedule option.
This is not actually scheduling an autorun, its just putting it as a task to be performed under the Terminal section?
And does the order of the “task” as well decide the order how it will run if Run actions is executed?
That’s correct. Is it better doing it directly?
Yes, that’s indeed the case. Tasks have different priorities internally, and are sorted each time a new one enters the list.
Could you share a screenshot of this possibility?
I’m of course open for suggestions and input, in fact that could help making it even better!
Not at all,
I think the way it is, its totally fine cause those two things I asked are interacting together.
There is “run now” which executes the specific task immediately or “pending” which gives the users possibility to create a chain task that can be run all at once or separately.
Kinda like the way you can do an automation from the provided options. 
However If I may ask for a “feature” It would be nice if we can reorder the “tasks” after there are added as pending in Terminal. Because When creating this I have to have in mind the proper order, once created if I want to switch TASK on position 7 with the one on position 2 I have to remove everything up at 1 > if that gives sense 
It might be better that there is a counter next to terminal or somewhere that lets you know things are there. As it is now you would have to know to look there if you were for instance to try an install tuxcart or something. I see the hour glass but it might be easy to miss maybe it could be a first run dialog or something.
And… I would say… that it is on next level… 
Great work @dr460nf1r3 
