We hope with all these changes Manjaro to be more efficient for you all.

If you are curious about the latest state of development for the upcoming Manjaro-Illyria 18.0 release, you now have the opportunity to download a beta-build of Manjaro-Xfce 18.0 including the latest xfce-gtk3 packages aswell as our most recent styling efforts:

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Testing Updates Announcements RSS feed

Issues with folder view widget in KDE v5.13

KDE introduced a new setting for icon sizes. Now you’re able to define also the size for your panel. If you have a high-DPI display, you may want to increase the value. This will fix the display issue with given widget.

Pulseaudio changes

With this update we have a /etc/pulse/default.pa.pacnew. It may be necessary to merge (some lines related to “GSettings” in /etc/pulse/default.pa ) if ‘default.pa’ has been customised.

thunar-archive-plugin has added native support for the Engrampa archive manager. engrampa-thunar-plugin is no longer needed. Remove engrampa-thunar-plugin to continue with the update.

Items from previous update sets

Kernel 4.9 issues

Seems on rare conditions you may face a faulty boot with linux49. It results in messages similar like this: <module> likely not compiled with -mcmodel=kernel. Also you will land in the emergency console.

We recommend to install at least another kernel as backup. You may follow this post to recover. v4.9.107-2 is known to be working.

I see a lot of pacnew files

Well, there is no manual intervention needed for pacnew files coming from filesystem package. The best thing you can do is, do nothing.

Never, ever, ever, ever, ever merge the pacnew file for /etc/{passwd,shadow,gshadow,group}, unless you want to make the new comments match aesthetically with your in-use user accounts database. The only practical difference that merging can ever cause is to accidentally delete users or mangle the whole file’s syntax and render your computer maybe unbootable.

Changes made to Glibc

The new version of glibc removes support for NIS and NIS+. The default /etc/nsswitch.conf file provided by filesystem package already reflects this change. Please make sure to merge pacnew file if it exists prior to upgrade.

NIS functionality can still be enabled by installing libnss_nis package. There is no replacement for NIS+ in the official repositories.

Changes made to PAM

pam 1.3.0-2 no longer ships pam_unix2 module and pam_unix_*.so compatibility symlinks. Before upgrading, review PAM configuration files in the /etc/pam.d directory and replace removed modules with pam_unix.so. Users of pam_unix2 should also reset their passwords after such change. Defaults provided by pambase package do not need any modifications.

Check grep -rn 'pam_unix[2_]' /etc/pam.d, if no output, you need to do nothing.

Samba units renamed

Note: In samba 4.8.0-1, the units were renamed from smbd.service and nmbd.service to smb.service and nmb.service.

To provide basic file sharing through SMB start/enable smb.service and/or nmb.service services. See the smbd(8) and nmbd(8) man pages for details, as the nmb.service service may not always be required.

Directory permissions differ

Currently there seems to be an issue when using group = sambashare with Samba 4.8.1-1, which is used by default in thesmb.conf provided by Manjaro. Changing it to group = +sambashare or force group = +sambashare resolves this. However, we might fill out a bug report, to see why that is currently needed.

Commenting/removing group = sambashare is also a viable solution.

Long delay for starting Desktop Environment

There’s a bug which is exhausting the entropy pool. This is refilled over time through e.g. disk activity and mouse movement. You can increase the fill rate with a software solution:

since that update, almost every time I reboot, there is a message box telling me that maybe my internet is not present once KDE has started. The network connection is up at the time the message appears (Wired connection directly connected to my router)
Edit: Internet is also present at the router, last reconnect was a scheduled 24 hour reconnect 9 hours ago.

Yesterday, I reported that I successfully installed to a VM; today I successfully installed on real HW. Everything went well, though when I originally installed maybe two years ago, I suffered with the Open Source Video Drivers for a week or so; today, I felt I needed to install proprietary drivers within the first hour.

EDIT - works like a charm. i set it to lz4 in ~/.config/manjaro-tools/manjaro-tools.conf.

My iso-profiles were also slightly out of date so I commented out pcmciautils and zd1211-firmware from /usr/share/manjaro-tools/iso-profiles/shared/Packages-Root to get round the package not found errors, they are now AUR only packages.

I can’t see anything that could be related to an input thing. But I can just recreate it. If I go back to the last update it works, if I do the update its broken. I’ll play around a bit with that later. Hopefully I can find a reason.

philm updated Packages-root accordingly on manjaro’s gitlab last week. It no longer contains references to those problematic packages. He must have encountered the same issues compiling Manjoro 18 xfce Beta 3 and removed them.

the actual package is manjaro-iso-profiles-base. I have modified those symlinked files which I know is probably not best practice but it’s easier for me to work that way.

to clarify, they are in the manjaro-iso-profiles-base package, manjaro-iso-profiles-community and manjaro-iso-profiles-official both require that base package to be installed. I’m well aware of what i have to use for now. I currently have no interest in the community ISO profiles as I use KDE and XFCE only.

it is also possible to dump and save the text from that gitlab Packages-Root into the /usr/share/…/Packages-Root file and use it. It won’t cause any breakage.

the fact of the matter is all files from the gitlab build transaction I referenced will eventually end up in the manjaro-iso-profiles-base package when it is updated, the code is not written twice by @oberon or @philm , they have better things to do with their time

I can deal with it, you can either delete them or hash them out but whether everyone will know to do this I don’t know but it does stop manjaro tools working if not done. I guess it depends if its days, weeks or months till the new iso profiles are posted, not sure what should be done if it is going to be a long time?