$ optimus-manager --status
Traceback (most recent call last):
File "/usr/bin/optimus-manager", line 33, in <module>
sys.exit(load_entry_point('optimus-manager==1.4', 'console_scripts', 'optimus-manager')())
File "/usr/bin/optimus-manager", line 22, in importlib_load_entry_point
for entry_point in distribution(dist_name).entry_points
File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 919, in distribution
return Distribution.from_name(distribution_name)
File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 518, in from_name
raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for optimus-manager
Edit: Resolved by uninstalling optimus-manager, rebooting, re-installing optimus-manager and rebooting again.
Previous Xorg-Server upgrade made everything huge (or at least kde plasma) because of a regression.
I didn’t want to do the -dpi 96 in /etc/sddm.conf trick that was mentioned everywhere, but wait for the next upgrade instead.
Xorg 21.1.2 is supposed to fix this but after upgrade and reboot I still see kde plasma huge. Do I have to do something?
Just in case it is relevant, this was on a fresh OS install so I didn’t have a working xorg and then an upgrade made it huge, but instead the fresh install was already huge, but still I was hoping the upgrade would fix it automatically.
@jpalko Thank you for your help in the previous topic.
Apparently it was not a smart idea of me to remove an old video-nvidia-3xx driver and use the generic(?) video-nvidia driver and update the system afterwards rightaway.
Happy New Year , and thank you for another smooth update! Only thing “odd” I noticed was a downgrade to manjaro-hello.
I have questions about the Python 3.10 upgrade and “leftovers” I found in ~/.local/lib/python3.9 and /usr/lib/python3.9 I’ve asked @ Python 3.9 to 3.10 validation and cleanup
EDIT: I did notice I had a bluetooth “issue” in journalctl after the update reboot:
$ journalctl --priority err --boot 0
Jan 02 10:34:30 AM4-5600X-Linux bluetoothd[791]: Failed to set mode: Blocked through rfkill (0x12)
Now, this might have been because I had bluetooth “disabled” in the KDE plasma panel… but I performed the following commands just to be sure:
This does not give all Python packages from AUR only, it gives all Python packages from AUR and from the repos.
Wouldn’t it better to do this instead ?
Had to remove Green With Envy and reinstall so it reinstalled its dependencies properly, but other than that went smoothly. Only 1 thing to upgrade to Python 3.10 - patool
Yes, the thing is that it shouldn’t be necessary. This happened because of a regression and this update should fix this, but for some reason it doesn’t in my case, so I’m wondering why