grub.pacnew tries to override (disable) current Manjaro grub theme GRUB_THEME, and to modify GRUB_TIMEOUT and GRUB_CMDLINE_LINUX_DEFAULT.
What to do about this :
:: OpenVPN now uses a netlink interface for network configuration. The systemd
units start the process with a dedicated unprivileged user 'openvpn', with
extra capabilities(7). The configuration should no longer drop privileges,
so remove 'user' and 'group' directives.
Scripts that require elevated privileges may need a workaround.I remembered, there was something inside update:
:: OpenVPN now uses a netlink interface for network configuration. The systemd
units start the process with a dedicated unprivileged user ‘openvpn’, with
extra capabilities(7). The configuration should no longer drop privileges,
so remove ‘user’ and ‘group’ directives.
Scripts that require elevated privileges may need a workaround.
Very smooth, thank you!!
Now this is interesting, will a newer .pacnew file overwrite the old .pacnew and then your regular config gets overwritten or merged automatically?
Looking at my mkinitcpio.conf it was definitely merged since the hooks look to have changed and the syntax has changed only in places from " " to ( ) There was no problem this time but it could have easily been the case.
It’s fair to say linux users should know their machine and do this stuff, especially power users like arch users but I’ve never before been told this - really should be part of some Manjaro Crash Course. 
Pacman offers no such service to merge these files, is this planned for pamac? Does yay offer this?
On one hand this isn’t great for regular users coming from Windows that are frightened to mess with system files, on the other, consistent sane defaults should be okay.
Please split this topic if this is out of scope of an update thread. 
Edit: Found the comic where I first heard about the config files breaking, I really thought it was a joke. (Warning, naughty words, adult themes)
1 Like
Thanks, it’s working now.
It turns out SDDM’s auto login was the problem - not sure if it was all along or in addition to that regression (I should’ve checked earlier logs more carefully)
Sample log output
I noticed this in /var/log/Xorg.0.log:
[ 483.780] (EE) Failed to open authorization file "/var/run/sddm/{5cd37d36-6e3a-4fc5-b255-2faeb13837d9}": No such file or directory
And systemctl status sddm:
Nov 19 12:25:42 sddm-helper[1237]: pam_env(sddm-autologin:session): deprecated reading of user environment enabled
Nov 19 12:25:42 sddm-helper[1237]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_open_session
Nov 19 12:25:42 sddm-helper[1237]: Starting: "/usr/share/sddm/scripts/wayland-session /usr/bin/startplasma-x11"
Nov 19 12:25:42 sddm[731]: Session started
Nov 19 12:25:42 sddm-helper[1237]: [PAM] Closing session
Nov 19 12:25:42 sddm-helper[1237]: pam_unix(sddm-autologin:session): session closed for user luke
Nov 19 12:25:42 sddm-helper[1237]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_close_session
Nov 19 12:25:42 sddm-helper[1237]: pam_kwallet5(sddm-autologin:setcred): pam_kwallet5: pam_sm_setcred
Nov 19 12:25:42 sddm-helper[1237]: [PAM] Ended.
Nov 19 12:25:42 sddm[731]: Auth: sddm-helper exited with 1
I had some .pacsave and .pacnew files I missed from previous upgrades too, one was related to PAM, but ultimately it was disabling auto login (while sddm was downgraded) and clicking the “Sync” settings button that fixed it. Re-enabling autologin works too.
Really? Can you install digikam? Because I can’t on a fresh install. KDE-Git packages are all over the place
Supposing I have the same issue as Iah7, can I just wait a few days until sddm 0.19.0-2.2 is in stable, update and my black screen will be fixed?
Hi Anthony
sddm 0.19.0-2.2 is already in stable. I isntalled it already a few minutes ago.
check/install with sudo pacman -Syyu
no change despite this version for me…
Hi grau,
you are right, I already have it and my screen is still black, only tty working. Guess its something else then.
Having same issue, going back go kernels 5.7 and 5.4 will have you able to use manjaro while waiting for fixes.
warning: gnome-wallpapers: local (20201023-1) is newer than community (20201020-1)
What does it mean?
Thank you. I already suspected that it would be fish unable to execute /etc/profile.d/flatpak.sh but this file has not been changed by this upgrade (I compared it to the previous version). So while this is a plausible explanation, now I do not understand why it did work ever before 
.
In general, fish is not POSIX-compliant by design, so it is not a bug per se. Unfortunately one cannot use it as a login shell then (except with heavy customization). I was not aware of that.
As a solution I chose the route described here: ArchWiki: Setting fish as interactive shell only
1 Like
I’m not even going to use 5.9 because of a number of problems with Nouveau, I’m going to stay at 5.4. Legacy Nvidia drivers have serious problems with this kernel, in one of my tests I received a black screen. Possibly, the problems can be fixed before the release of 5.10, which will be LTS.
Error when trying to launch screensaver:
/usr/lib/xscreensaver/xmatrix: error while loading shared libraries: libgdk_pixbuf_xlib-2.0.so.0: cannot open shared object file: No such file or directory
Some other screensavers work, some don’t. Obviously not a serious issue as it’s only a screensaver, but still, it would be nice to have it working again.
Update went smooth with UI . Bluetooth problems through previous update are gone.
Good work @ manjaro
Ok, to “make a point”:
The misspelling is not the only thing which is wrong. Even in your example, you could see the addtional dash (-) for fasttrack et al is missing in the man.
The EXAMPLES section of the man (the most valued documentation IMHO, I hate enumerations of parameters given as “documentation” or “manual”). Do use too less dashes:
EXAMPLES section
EXAMPLES
Most optional arguments are self explaining others require explanation. The API functions is mainly designed to help packagers and iso-builders. However it can be of use for everyone because it takes the hazzle out of
editing your pacman-mirrors configuration.
Commands
• Which countries has mirrors?
pacman-mirrors –country-list
• Which countries in my custom mirror pool
*pacman-mirrors –country-config
• What branch am I on
pacman-mirrors –get-branch
Commands requiring sudo
• I want to permanently change branch to unstable, use mirrors from Germany and France, use only https and http protocol in that order
sudo pacman-mirrors –country Germany,France –api –set-branch unstable –procotol https http
• Create a mirrorlist with German mirrors
sudo pacman-mirrors –country Germany
• If you want more countries in your mirrorlist add them they will be written to your custom mirror pool
sudo pacman-mirrors –country Germany France Denmark
• Create a mirrorlist with 5 mirrors up-to-date on your branch
sudo pacman-mirrors –fastrack 5
• I want to choose my mirrors
sudo pacman-mirrors –interactive
• I have a custom mirror list and I want to create a new custom mirror list?
sudo pacman-mirrors –interactive –default
• I have a custom mirror list - can I reset it?
sudo pacman-mirrors –country all
Advanced use samples - BEWARE OF THE DRAGONS
(snipped away because not relevant here).
Whoes output would be more handy if it is get outputted when a incorrect parameter is given. Also I’m very sure the short help did not mention continent, but I can’t reproduce that anymore.
Report:
- encryption OK
- mkinitcpio.conf not overwritten, no pacnew because last time, doh
- openvpn works, sans pia, who need a kick in the nuts for bad ipv6 conf
Yet I am still annoyed.
- Thunderbird… No comment
- What the hell happened to custom kwin(?) keyboard shortcuts? I see nothing of the sort in kde settings any more. I need my custom commands back!
- Why the hell does the compositor keep crashing/disabling itself for weeks now?
So to sum up: death by 3 papercuts
1 Like