Manjaro, like many other open-source projects, relies on the generosity of its community through donations and corporate sponsorships to support its growth and development. These donations are essential in covering the various expenses incurred in the operations of the project such as server costs, software development tools, infrastructure expenses, training, flying people to events or conferences and the salaries of key developers. With the help of these donations, Manjaro is able to secure the necessary financial stability that allows the project to continuously improve and remain active. If you love Manjaro, consider to donate!
As you might have seen some of our team were able to attend FOSDEM 2023 and the conference proved to be incredibly productive for us. See our blog post for more.
Finding information easier about Manjaro always has been a topic that needed to be solved. With our new search we have put all Manjaro data accessible in one place and divided by sections so it makes it easier to digest: New Manjaro search engine is available | Blog
You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.11.so.
Print a list of of packages that have files in /usr/lib/python3.11/ :
pacman -Qoq /usr/lib/python3.11/
Rebuild them all at once:*
pamac build $(pacman -Qoq /usr/lib/python3.11)
* Note that if any fail to build, you’ll have to rebuild what’s remaining one or a few at a time.
Use rebuild-detector to see if anything else needs to be rebuilt:
checkrebuild
Info about AUR packages
AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements topics are off-topic and will be flagged, moved or removed without warning.
For help with AUR packages, please create a new topic in AUR and a helpful volunteer may be able to assist you.
No plasma interface with kernel 6.9 + Nvidia gpu + Wayland
If you encouter a black screen with no inteface after login in, it’s probably a problem with simpledrm loading.
To solve it add nvidia_drm.fbdev=1 to /etc/default/grub
in the line begining with GRUB_CMDLINE_LINUX=" .
Verify that you also have nvidia_drm.modeset=1 in the same line.
Then exec sudo update-grub
Also, verify that you have nvidia_drm in /etc/mkinitcpio.conf in the MODULES= or HOOKS= line.
Exemple :
The default KDE Plasma session has been changed to X11
As of Plasma 6, KDE decided to make Wayland the default. However, since issues were discovered, we have reverted the default to X11. Users are free to choose whichever works best for them.
can you check status for build nvidia lib32 modules ?
sudo pacman -Syyu
[sudo]
:: Synchronisation des bases de données de paquets…
core 140,4 KiB 1003 KiB/s 00:00 [----------------------] 100%
extra 8,4 MiB 27,9 MiB/s 00:00 [----------------------] 100%
multilib 145,5 KiB 1119 KiB/s 00:00 [----------------------] 100%
:: Début de la mise à jour complète du système…
résolution des dépendances…
avertissement : impossible de résoudre « nvidia-utils=555.58 », une dépendance de « lib32-nvidia-utils »
:: Le paquet suivant ne peut être mis à jour à cause de dépendances insolubles :
lib32-nvidia-utils
:: Voulez-vous ignorer le paquet ci-dessus pour cette mise à jour ? [o/N]
erreur : la préparation de la transaction a échoué (la satisfaction des dépendances a échoué)
:: impossible de satisfaire la dépendance « nvidia-utils=555.58 » requise par lib32-nvidia-utils
waiting when it all will be ok (no update to do for the moment )
Why not just wait until the announcement that it’s there?
Or if you’re really, really, really that angsty, why not just give it a go and deal with thee consequences? Remember, always, before any upgrade: BACKUPS!
Because the fact that it might run better on YOUR installations is no guarantee - otherwise there’d be just one test laptop and it’d go straight to Stable
We won’t update to 6.1 Plasma any time soon. There are serious bugs which prevents that. You can find the Plasma 6 upstream release schedule and see when bug fixes are expected. Switch to unstable to help testing. Testing branch is a preparation branch for the Stable branch. So we will see when Plasma 6.1 is enough stable from our end to land here.
In addition to a considerable amount of bugs in 6.1, with NVIDIA 555.58 I have also had black screen problems when logging in and out in both Wayland and X11.
Lutris was not behaving normal right now, so I checked the command line output. It seems it has to be recompiled with the pushed python updates.
The log:
2024-07-01 19:09:32,621: The Battle.net source is unavailable because Google protobuf could not be loaded: Descriptors cannot be created directly.
If this call came from a _pb2.py file, your generated code is out of date and must be regenerated with protoc >= 3.19.0.
If you cannot immediately regenerate your protos, some other possible workarounds are:
1. Downgrade the protobuf package to 3.20.x or lower.
2. Set PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python (but this will use pure-Python parsing and will be much slower).
EDIT:
Another issue I face and cannot fully resolve is regarding gamscope-plus (and also gamescope (while using lutris). The error:
gamescope: children shut down!
(EE) failed to read Wayland events: Broken pipe
X connection to :2 broken (explicit kill or server shutdown).
X connection to :2 broken (explicit kill or server shutdown).
X connection to :2 broken (explicit kill or server shutdown).
X connection to :2 broken (explicit kill or server shutdown).
Initial process has exited (return code: 0)
(I am on gnome wayland with an AMD graphics card). I tried to downgrade to the previous gamescope version with manjaro-downgrade to resolve the issue, but this warning kept me from doing it to be honest.
Warning: Cannot resolve "libdisplay-info.so=1-64" (a dependency of "gamescope-plus")
Maybe this information helps
(I am on Gnome Wayland)
Hi. The update went almost OK. The only issue is missing krdp package that is listed as dependency of plasma-meta package:
:: Starting full system upgrade...
resolving dependencies...
warning: cannot resolve "krdp", a dependency of "plasma-meta"
:: The following package cannot be upgraded due to unresolvable dependencies:
plasma-meta