I always update Manjaro with pacman so maybe pamac did something wrong on your side. I think most people on Testing branch also use pacman to update so it may be possible that pamac overwrote your config file, not sure if it is technically possible but seems plausible.
Need all the ones with same issue to maybe confirm that they also used Pamac and not pacman (sorry too lazy to read all messages, if you remember or can find the others you’re talking about, reply by calling their @name so they receive a notification).
1 Like
Note that for the update in question I had used pamac (not pacman).
Tagging, as suggested by @omano: @waranty92 @RayonRa @nicolas33 @stdout @94afd24efe1948f87e7d
You’re best bet would be to try and see if you can find a flatpak or appimage (snap won’t work because of the forced update mechanism in snap) of the version you need (that way it will contain all the required libraries it requires). Running on a rolling release version of linux is not conducive to keep old outdated software working.
VMWare guest still have issue with the graphical corruption. Waiting for mesa fix
1 Like
I always use pacman for big update.
i3, Thinkpad T470s, 5.9 kernel
Only hitch I had is with audio control: the volume icon and volume keys no longer control the system volume. Dunst notifications appear as they should when I try to change the volume, but the volume itself does not change.
I can control volume from within the AlsaMixer, as expected.
That was it, much appreciated
1 Like
Everything seems to be fine on KDE after upgrade.
Only thing scaring me is the mkinitcpio.conf pacnew 
Are the modules keyboard and resume safe to remove ?
I have this :
52c52
< HOOKS="base udev autodetect modconf block keyboard keymap resume filesystems"
---
> HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)
62a63
On a lesser extent I’m also wondering if /etc/default/grub could be merged :
diff /etc/default/grub /etc/default/grub.pacnew
3,5c3,5
< GRUB_TIMEOUT_STYLE=menu
< GRUB_DISTRIBUTOR='Manjaro'
< GRUB_CMDLINE_LINUX_DEFAULT="quiet resume=UUID=9b5e4530-6b1c-46c6-a66c-984c6986ebe0"
---
> GRUB_TIMEOUT_STYLE=hidden
> GRUB_DISTRIBUTOR="Manjaro"
> GRUB_CMDLINE_LINUX_DEFAULT="quiet udev.log_priority=3"
32,33c32,33
< # Uncomment if you want GRUB to pass to the Linux kernel the old parameter
< # format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
---
> # Uncomment if you want GRUB to pass to the Linux kernel the old parameter
> # format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
39c39
< # Uncomment and set to the desired menu colors. Used by normal and wallpaper
---
> # Uncomment and set to the desired menu colors. Used by normal and wallpaper
46c46
< GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"
---
> #GRUB_THEME="/path/to/gfxtheme"
If I want the manjaro grub menu to appear on each boot I have to keep GRUB_TIMEOUT_STYLE=menu right ?
Concerning the GRUB_CMDLINE_LINUX_DEFAULT lin, I don’t know what to do…
1 Like
main change is “xxx” becoming (xxx), how you setup the modules depends on your system. I couldn’t have a clear answer so I’ll do the same, RTFM lol
You can start from here [Stable Update] 2020-11-04 - Kernels, Nvidia 455.38, LibreOffice, Plasma5, Frameworks, Apps, Gnome 3.38, Deepin and read previous related messages, direct replies, or the replies made without replying directly which you will need to scroll down to find.
In the end I just changed the characters and left my modules as is.
//edit: and for your GRUB you can keep it as you have it currently, then changes are only comments, the new Manjaro grub theme, and quotes, or not, around parameters. You don’t want to replace your GRUB_CMDLINE_LINUX_DEFAULT line, it contains the needed info to resume from sleep, you could add the missing parameter though if you want.
//edit: everytime there is a pacnew doesn’t mean it is REQUIRED to overwrite your file. Here the changes are marginal and would not break anything if not applied. pacnew file just mean there was changes in the default config file, and it is up to you to think if and what you will modify, or not.
2 Likes
The safest bet is to just modify your current configuration changing the “” to (). That will keep your system running the way it was before. The .pacnew is a BASE configuration making the new change for arrays from “” to ().
(edit: just the arrays get changed from “” to (), so HOOKS, MODULES, BINARIES, FILES, and COMPRESSION_OPTIONS, the single strings like COMPRESSION remains a “”, )
As for the grub changes I personally just left my original in place because that is how I wanted my grub to be, from what I could tell most of the grub changes had to do with adding periods to the end of several commented out lines.
1 Like
Thanks for the tip!!! It looks amazing now.
I almost exclusively use pacman from a TTY to perform updates. So bang goes that theory.
OK so not a Pamac issue. But people have no trace of the pacnew file in pacman logs. Really weird.
I wonder I failed at updating /etc/mkinitcpio.conf during my previous upgrade. Anyway, adding lvm2 did the trick. Thank you much!
Same happened for me, actually during installation of web-installer-url-handler (1.0.2-1) running Linux 5.8.18-1-MANJARO #1 SMP PREEMPT Sun Nov 1 14:10:04 UTC 2020 x86_64 GNU/Linux, i3wm.
Edit: See also in forum thread [Testing Update] 2020-11-17 - KDE Frameworks 5.76, Deepin, Firefox 83.0, AMDVLK 2020.Q4.4.
1 Like
I’m running Linux 5.9.8-2-MANJARO with KDE and I lost the power management control over the brightness of my laptop screen.
CPU: Intel i5-8300H (8) @ 4.000GHz
GPU: NVIDIA GeForce GTX 1050 Mobile
VideoDriver: video-hybrid-intel-nvidia-455-xx-prime
Edit: Everything works 10/10 with 5.8.18-1-MANJARO.
Looks like a problem with the 5.9 kernel,the fix is here
1 Like
Still having issue with mesa in VMWare guest.
Issue is still opened on mesa’s side.
I found dirty temporary workaround until Manjaro ships mesa-20.3
Replace mesa with AUR’s mesa-llvm-rc 20.3.0_rc2-1. Using yay -S mesa-llvm-rc (this will delete: mesa and libva-mesa-driver )
When mesa 20.3 arrive replace it back.
I see… Any possibility of it being packaged? I don’t really wanna downgrade my kernel for this.