As of from what I’ve seen I’d say this issue has nothing to do with Rani.
All which this application does concerning handling service management is running plain systemd commands, there is no fancy custom logic involved whatsoever.
Using close to the exact words as the previous poster and somewhat overusing “those” “little” “signs” without “real” “reason” makes it hard to take “serious” without providing proper diagnostic “information” or instructions on how to reproduce (especially if the poster has already been suspended in the past), sorry. Maybe its just me though. Anyway, let’s get back to topic.
I’ve taken a look at the thread. Relevant information are:
I can confirm the UI hints about missing modules and headers weren’t fully accurate in some cases, as I’ve just found out. Rectified some of it regarding headers right now.
Hints towards this indeed being an issue with kernel version and nvidia-dkms package version used. There is nothing we can do here. The application simplifies attempting the reinstallation (as it: in runs the appropriate commands for you once applying the actions in the terminal), but it can’t magically fix NVIDIA’s long-known issues of keeping their drivers working for all kernel versions.
Well yes, unless there’s something else going on, this won’t magically work without NVIDIA fixing their stuff. To verify it is indeed the thing I hinted at earlier, we’d need the terminal output of Rani. As Duke pointed out, we can have application logs, and even better in this particular case: logs from the command executions.
As seen above, there is a button for copying the terminal output or uploading it straight to our PrivateBin instance and copying the link to the clipboard.
The way it works is that it it places a .desktop in ~/.config/autostart, and removes it.
I just verified that it indeed works this way. Does your folder contain such a file? I have a certain assumption, haha. org.garudalinux.rani.desktop or similar exists maybe?
ive deleted those file but i was on normal rani because ive installed on new other ssd. I did installed afterwards the git version and it wrote those file again in so i deleted it again and now its working. Thanks for that hint again would not expect that comes back
It might be best to not have bottles in rani or the other garuda tools. I can only see it being dropped from the aur and other places in time. OBS might end up like that down the line as well but, they are being a bit better about it for now. Less they start getting more bug reports like bottles was flooded with.
Debian and anyone else that pkgs old. even the aur they don’t want bug reports from as they should go to the aur pkger but they wont. And i can’t blame them its to random and a burden on the team.
(have you tried turning it off and on again?)
