Hello community, here we have another set of package updates.
Current promotions
We currently have a flash sale with our partner MINISFORUM on the UM790Pro featuring the Manjaro Linux GamingEdition. Use the device either as a MiniPC or Gaming Console! Use our link to get yours. Note: US Market only!
Find out all about our current Gaming Laptop the Hero with Manjaro pre-installed from Spain!
Protect your personal data, keep yourself safe with Surfshark VPN: 85% OFF + 2 mo. FREE
Recent News
Manjaro Team member @romangg has a new library project with a guest post on Phoronix.
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
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.
issues with auto-mount of ntfs filesystem using Kernel 6.8
The kernel changed default ntfs driver from FUSE one to ntfs3.
These two are not fully compatible, mainly as far as mount options go. If you have custom mount options in the fstab (or any other application, such as VeraCrypt) they need to be changed.
Symptoms:
Mount fails with: Device or resource busy
DMesg reports: Can't open blockdev
Solution:
Migrate your mount options. For me the changes were:
pacman-contrib is now split out from pacman. If you have anything installed that depends on pacman-contrib, update with:
sudo pacman -Syu pacman-contrib
2024-01-11
Making dbus-broker our default D-Bus daemon
2024-01-09 - Jan Alexander Steffens
We are making dbus-broker our default implementation of D-Bus, for improved performance, reliability and integration with systemd.
For the foreseeable future we will still support the use of dbus-daemon, the previous implementation. Pacman will ask you whether to install dbus-broker-units or dbus-daemon-units. We recommend picking the default.
For a more detailed rationale, please see our RFC 25.
Unfortunately this update seems to have broken KDE6 HDR mode. HDR is enabled but the colors look very washed out. I connected the same monitor to another computer before and after the update and it went from vibrant HDR to muted washed out picture with the update. I’m connected over Display Port, kernel 6.8. It happens both on a 7840u APU and 6900xt. I’ve disabled HDR for now. Other than that everything seems great!
And once again copy, as I still am unable to edit the wiki post:
For anyone experiencing issues with auto-mount of ntfs filesystem using Kernel 6.8:
The kernel changed default ntfs driver from FUSE one to ntfs3.
These two are not fully compatible, mainly as far as mount options go. If you have custom mount options in the fstab (or any other application, such as VeraCrypt) they need to be changed.
Symptoms:
Mount fails with: Device or resource busy
DMesg reports: Can't open blockdev
Solution:
Migrate your mount options. For me the changes were:
allow_other → umask=000
default_permissions → [drop]
user_id=1000 → uid=1000
group_id=1000 → gid=1000
[ nikgnomic: comment added to Known issues & Solutions 2024-03-16 ]
The way official gnome-shell-extension-custom-accent-colors gets patched for Manjaros maia is not working 100% successfully. The border of the input fields in the application overview and in the dialog coming up asking for credentials don’t get styled with maia color.
Also when using the dash to panel extension, the application overview button gets shrinked. If I switch to another color everything works flawlessly.
I looked into the stylesheets. From version 9 to version 10 the parents stylesheets changed a lot. The patched in maia stylesheet still looks like version 9, which probably explains the issue.
If anyone who mount NTFS partitions (including Windows) suffers from permission issues even after modifying ntfs to ntfs3 in /etc/fstab.
I already have fast boot disabled in Windows10, so what I did is simply booting into Windows then open all my partitions and shutting down, then boot into Manjaro, and all permissions seem to be fixed.
And for exFAT USBs/drives issues, it’s solved by installing exfatprogs which removes the non-working exfat-utils.
Since this update to Gnome 46 I’ve been struggling to switch off bluetooth through the panel. The button doesn’t grey out as expected. I have to execute to sudo systemctl stop bluetooth to turn off bluetooth, at which point the button does grey out. A bit annoying!
Yeh I did contemplate doing that but then I realise there are times where I do need to use bluetooth. I seem to enjoy switching off and turning on bluetooth manually through GNOME’s panel. The thing is the hanging on the UI side doesn’t always happen.
I’m on testing but haven’t synced with this update. I also experience this Bluetooth issue but haven’t spent any time investigating it. It seemed to happen when I started using kernel 6.8.0.
GNOME 46
Plasma 6.0.3
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-04-04
Windows Fast Startup should always be disabled when multibooting.