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: News â Manjaro
Nvidia drivers got downgraded to 550.100, therefore update with sudo pacman -Syuu. If you want to stay on the 555 driver series you may either switch to unstable or install nvidia-dkms via: sudo pacman -U https://mirror.easyname.at/manjaro/pool/overlay/nvidia-dkms-555.58.02-1-x86_64.pkg.tar.zst. More info about Nvidia drivers here:
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.
Linux 6.9 is EOL and will - at some point - be removed from the repo.
Suggestion is to install latest LTS to be sure
sudo mhwd-kernel -i linux66
2024-07-14
Nvidia driver downgrade
Nvidia drivers got downgraded to 550.100, therefore update with sudo pacman -Syuu. If you want to stay on the 555 driver series you may either switch to unstable or install nvidia-dkms via: sudo pacman -U https://mirror.easyname.at/manjaro/pool/overlay/nvidia-dkms-555.58.02-1-x86_64.pkg.tar.zst. More info about Nvidia drivers here:
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.
Using Freon on Manjaro-Gnome, the update today is hiding all SATA-drives (but not the NVMe).
One reason may be, kernel-module drivetemp is not loaded ( sudo modprobe drivetemp does it).
But loading module drivetemp is not enough, because ALL the SATA-drives are called now âtemp1â -
instead of for example " SAMSUNG HDâŠ".
Kernel 6.1.103-1 and 6.10.3-1
EDIT:
Kernel 6.1.100-1 is o.K.
Everything works as it shouldâŠ
Anyone who has protontricks and/or protonup-qt will have to manually allow replacing conflicting packages when using pacman to update:
looking for conflicting packages...
:: python-vdf-solstice-3.5-1 and python-vdf-3.4-4 are in conflict. Remove python-vdf? [y/N] y
:: python-steam-solstice-1.6.0-1 and python-steam-1.4.4-4 are in conflict. Remove python-steam? [y/N] y
After the update, I couldnât use mpv anymore so I rebooted my machine and now I can only log into emergency mode with 6.4 kernel, I also have 6.6 and 6.9 but both lead to a black screen.
I have the failed to mount /boot/efi error and a bunch of other ones in journalctl :
EXT4-fs error (device sda2): ext4_validate_block_bitmap:421: comm ext4lazyinit: bg 82: badblock bitmap checksum also appears with other bg values
pipewire-pulse really shouldnât provide pulseaudio, as itâs not 100% compatible. For example, pacmd is missing and the CLI protocol that pacmd depends on isnât implemented, either.
Packages that explicitly require pulseaudio and are incompatible with pipewire-pulse should continue to declare depends=(pulseaudio).
Packages that work with either pulseaudio or pipewire-pulse should declare pulse-native-provider.
Anybody else having difficulty connecting through Wifi since latest testing update ?
All was well before, now I can not connect anymoreâŠ
/08/2024 22:11 NetworkManager <info> [1722888686.4484] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.48.6-1/libnm-device-plugin-wifi.so)
5/08/2024 22:11 NetworkManager <info> [1722888692.4227] device (wlp3s0): Activation: (wifi) access point 'Airport3' has security, but secrets are required.
5/08/2024 22:11 NetworkManager <info> [1722888692.4237] device (wlp3s0): Activation: (wifi) connection 'Airport3' has security, and secrets exist. No new secrets needed.
5/08/2024 22:11 NetworkManager <warn> [1722888718.1655] device (wlp3s0): Activation: (wifi) association took too long
5/08/2024 22:11 NetworkManager <warn> [1722888718.1657] device (wlp3s0): Activation: (wifi) asking for new secrets
5/08/2024 22:11 NetworkManager <info> [1722888718.1667] device (wlp3s0): Activation: (wifi) connection 'Airport3' has security, and secrets exist. No new secrets needed.
5/08/2024 22:12 NetworkManager <warn> [1722888743.1653] device (wlp3s0): Activation: (wifi) association took too long
5/08/2024 22:12 NetworkManager <warn> [1722888743.1671] device (wlp3s0): Activation: (wifi) asking for new secrets
5/08/2024 22:12 NetworkManager <info> [1722888743.1698] device (wlp3s0): Activation: (wifi) connection 'Airport3' has security, and secrets exist. No new secrets needed.
5/08/2024 22:12 NetworkManager <warn> [1722888768.1647] device (wlp3s0): Activation: (wifi) association took too long
After entering credentials again through KDE settings, still can not connect:
5/08/2024 22:19 wpa_supplicant wlp3s0: Trying to associate with SSID 'Airport3'
5/08/2024 22:19 NetworkManager <info> [1722889145.9850] device (wlp3s0): supplicant interface state: scanning -> associating
5/08/2024 22:19 NetworkManager <info> [1722889145.9851] device (p2p-dev-wlp3s0): supplicant management interface state: scanning -> associating
5/08/2024 22:19 NetworkManager <warn> [1722889146.1653] device (wlp3s0): Activation: (wifi) association took too long
5/08/2024 22:19 NetworkManager <info> [1722889146.1653] device (wlp3s0): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed')
5/08/2024 22:19 NetworkManager <info> [1722889146.1662] manager: NetworkManager state is now DISCONNECTED
5/08/2024 22:19 NetworkManager <warn> [1722889146.1667] device (wlp3s0): Activation: failed for connection 'Airport3'
5/08/2024 22:19 NetworkManager <info> [1722889146.1672] device (wlp3s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
5/08/2024 22:19 wpa_supplicant nl80211: send_event_marker failed: Source based routing not supported
5/08/2024 22:19 wpa_supplicant wlp3s0: CTRL-EVENT-DISCONNECTED bssid=e0:b9:e5:d8:4c:83 reason=3 locally_generated=1
5/08/2024 22:19 NetworkManager <info> [1722889146.6866] device (wlp3s0): set-hw-addr: set MAC address to 9A:AC:91:9E:53:FB (scanning)
5/08/2024 22:19 wpa_supplicant wlp3s0: CTRL-EVENT-DSCP-POLICY clear_all
5/08/2024 22:19 NetworkManager <info> [1722889146.6892] device (wlp3s0): supplicant interface state: associating -> disconnected
5/08/2024 22:19 NetworkManager <info> [1722889146.6893] device (p2p-dev-wlp3s0): supplicant management interface state: associating -> disconnected
5/08/2024 22:19 wpa_supplicant wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
5/08/2024 22:19 wpa_supplicant wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
5/08/2024 22:19 wpa_supplicant wlp3s0: Reject scan trigger since one is already pending
5/08/2024 22:19 wpa_supplicant wlp3s0: Reject scan trigger since one is already pending
Restored latest timeshift backup now, all is OK againâŠ
Which update could be responsible for this ?
System info can be given if askedâŠ
Thanks for any hints
You will need to rebuild any AUR Python packages that install files to site-packages or link to 
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.
2024-08-04
