After every update just run: DIFFPROG=meld pacdiff
It will take you through every pacnew and you can view, skip, remove. Read man page. meld is a super nice gui diff tool. You can compare files side-by-side.
The pacnew files cannot be merged without being reviewed first. Some will get you in big trouble.
Thank you very much! My system is working now again too. I also didn’t have a /etc/mkinitcpio.conf.pacnew. I had a grub.cfg.pacnew but this didn’t contain any critical changes (mainly some new spaces).
My system is asking for the encryption password twice now. Do you have this behavior too?
I run a couple of laptops with Manjaro-Xfce on AMD hardware. Yesterday’s upgrade worked fine, but I was wondering as to why the upgrade pulled certain KDE components. I haven’t noticed that before, but then I don’t watch it all the time, hence I might missed it.
Fixed it. Had to install the last stable version from the Arch Linux Archive.
I think the problem in my case is the older vpn Server I try to connect to.
First uninstall openvpn via pacman. After this install it from the Archive in an older version:
:: 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.
:: 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.
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.
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.