-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
optimus-manager cannot be loaded #541
Comments
I think I have a similar issue. I just updated, with a lot of python updates. I am actually able to boot normally, but when I try to switch to my Nvidia card with optimus-manager, I get the following Traceback:
|
I faced the same issue and was able to solve it by rebuilding the package with the new python version (3.11) following this:
|
Thank you @staust |
Just to make sure: This does not rebuild the optimus package with python 3.10. Basicly what should help is: |
Yes, thank you @staust, but also for me this problem persists after following your suggestion, also when using Update: Okay, I found out what the issue was in my case. I installed my system a long time ago using an installer from one of the arcolinux distributions. Even though I kinda stripped most of the arcolinux stuff away since then, I still have their repositories in my list, and optimus-manager was installed from one of their repos instead of the AUR. This apparently means that the package does not actually get rebuilt when using the suggested command. I uninstalled the arcolinux version and reinstalled using the AUR and now it works fine again. Thanks again for the suggestion @staust! |
Same issue here. Using arch/cinnamon. Couldn't even get graphical interface of lightdm with optimum-manager installed after python 3.11 upgrade. |
Have you tried @staust's suggested fix? I think the core of the issue is that your installed version of optimum-manager will be built against an earlier version of python, so the trick is to rebuild it against the updated version. If you cannot even get in the ligthdm or sddm login interface, you'll have to boot into command line mode (I am not sure that this is actually the correct terminology), as described here: https://www.baeldung.com/linux/boot-linux-command-line-mode. |
@staust , @WouterSpekkink |
Yeah, so I tried that command above, but it didn't work. It must've been automatically installing the package from the cache (which I cleared but it didn't make a difference) or the chaotic repository even though I specified AUR. I solved by downloading the pkgbuild from the aur websites manually, building, and installing with pacman -U. But I would rather not have to do it this way if you have any ideas. |
You've probably done the following already, but just to be sure, I think the following should work:
I actually think that this should probably be enough? I am not 100% sure about any of this, but I think this works because |
Fixed! Thank you very much @staust, saved me quite some time. I noticed the huge amount of python package updates today, but the issue appeared only when I made a few changes to my Arch system many hours later and rebooted. Took me a while to get to the culprit, which was the same as #541 (comment) |
I've encountered the same issue.
(yes I have both, but manly I use paru) |
470xx and older drivers may not function correctly on Linux 5.18 (or later) on systems with Intel CPUs 11th Gen and newer due an incompatibility with Indirect Branch Tracking. You can disable it by setting the ibt=off kernel parameter from the boot loader. Be aware, this security feature is responsible for mitigating a class of exploit techniques. |
I am still having this issue even after running all these steps. Uninstalled optimus-manager-git and optimus-manager-git-qt. Cleaned pacman, trizen, yay cache. Reinstalled both applications. Ran yay -S optimus-manager --answerclean All. I still get this error... During handling of the above exception, another exception occurred: Traceback (most recent call last): |
Same issue, black screen on boot after paru/pacman update with the above errors.
After the last command it does indeed rebuild it, and simply rebooting afterwards fully recovered my system. Thanks ffarps! |
For those like me that are using None of the previous options worked until I changed my global python version first. # Running this
pyenv which python
# has to give you this result
/usr/bin/python
# if it doens't, then run this command
pyenv global system
# and check again... |
Setting |
Sup @PunkUnity . Is this still an issue to you? In my case it got solved by using Since this issue isn't active for the last year and a lot has changed in many aspects of multiple software, we'll keep this case opened for some days and close it if no further comments are provided. We're dealing with backlog here to try to keep Have a nice week ahead. |
Describe the bug
After rebooting Arch Linux, SDDM doesn't start and the screen is black. Yesterday there were some updates like Python to 3.11.3 and Linux kernel 6.3.1.
Logs are attached to the issue ticket.
System info
Logs
optimus-manager status log.txt
optimus-manager systemctl status.txt
The text was updated successfully, but these errors were encountered: