Here’s what I would try:
set pamac to ignore the problem package and restart the updates:
sudo pamac update --ignore package-name
It should then update the remaining packages.
After completion, try updating the ignored package separately.
Fixed with libxnvctrl 470xx-470.182.03-3.
1 Like
That’s a royal PITA, there appear to be hundreds to ignore…
When rebooting the computer, instead of ending up in grub/manjaro, I ended up in refind. However, no options were offered there (white background with the refind logo, no operating elements)
I had to reboot again into UEFI to change the boot order back. After that grub/manjaro started again.
Background: I once tried to install refind, but was unsuccessful at the time. The refind.efi -corpse- is still in the EFI partition and seems to got bumped to 1. place in boot-order.
After this update I got error encoding video with hevc_nvenc codec on Nvidia GTX1080Ti card (Pascal architecture). The error was: “hevc_nvenc @ 0x55629e85a9c0] B frames as references are not supported”. Workaround for me is to encode with ffmpeg parameter “-b_ref_mode 0” (b_ref_mode=0 for kdenlive). Befor the update there was no errors. Any suggestions about the issue?
1 Like
I got used to call WIN + pamac + Enter to get into the software center. This no longer works after the update, as pamac-manager seems to be removed from the listed programs.
Workaround: call pamac-manager directly from the terminal.
Almost everything went smoothly, but somehow the inferiors panel height reset to 50 and got tiny icons in some title-bars alike the system updater.
1 Like
I had the disc encryption issue described here [Unstable Update] 2023-02-17 - Plasma 5.27 LTS, GNOME, Python - #50 by Skunkie and the solution worked for me.
The same with 1660S.
Xorg, gnome.
Well, that was totally unrewarding.
I started applying the updates one by one because there were so many unresolved deps.
Now I can’t launch pamac or firefox, or the app launcher.
Guess it’s time for a fresh install. 
1 Like
After the restart I felt like my eyes want to bleed the moment I moved my mouse, quickly realised I’m stuck in 144hz mode.
I’ve installed nvidia-settings, I’ve tried setting the resolution to 1920x1080 manually, and trying to set the refresh rate manually, but I see no 280hz option (or 240).
I didn’t have to configure it previously, it just automatically detected the 280hz settings. I have tried turning the OC on and off on my monitor and changing profiles etc.
The monitor is an Asus 259QM.
I’ve tried the 6.1 kernel which I was using previously and the 6.2
Please help, this actually hurts my head, it’s like every change is burning and movement is burning my eyes. (I had headaches constantly from fairly light computer use before this monitor, but this feels even worse than I remember). Yes I’ve checked and strobing/pwm is not on, that’s not what’s causing the pain, plus I’d have a migrane in the time it took me to type this if it was on.
Update: tried a long shot of starting up Overwatch 2 and seeing if it somehow tricked everything into 280hz. It didn’t. I’m going to take a break now, starting to feel a headache coming on already, using NON-FREE nvidia drivers.
99% of world’s population does not even have 144hz and you get migraines unless you have 280hz? jeez.
Anyhow, what DE are you using? Try setting the refresh rate from the system settings, not nvidia control panel.
Solved it for me too
Quick question concerning ZFS compatibility and linux 6.2.8.
Apparently backported bug fixes to linux 6.2.8 introduced incompatibility with zfs 2.1.9 as detailed in:
It appears a patch was generated correcting the issue
This has been applied to linux modules extra as of approximately 8 hours ago on gitlab
zfs 2.1.9-10
Checking the package versions for linux6.2-zfs from extra lists 2.1.9-9 as the latestversion on all manjaro variants, stable, testing and unstable
https://packages.manjaro.org/?query=zfs
Is there any reason the latest extra module zfs version is not included in any manjaro variant?
Given that I’m depending on zfs and am currently using linux6.2, should I avoid this particular stable update as I’m not interested in reverting to linux6.1?
Or should I manually determine the means to checkout, build and apply the 2.1.9-10 zfs module myself?
Can’t change it from KDE config either.
I don’t get migraines from 144hz, just headaches, but they used to take 4-5hours to come on. I’ve been on 240+ for many years now and 144 is feeling instantly much worse than I recall, like everything is high speed-stop motion. It’s more a tingling in my head I’m noticing which is a sign I’ll get a headache soon. It’s only any form of strobe backlight / pwm under 1khz gives me migranes in 1-15mins, was just mentioning I don’t have that on because some people suggest checking that’s off. For some reason I was fine on 75hz CRT back in the day, and had to stick with CRT all through the 60hz LCD panel era because they gave me headaches in 1-2 hours.
Right now it’s sort of OK if nothing is moving on the screen, but the moment I move windows/mouse my head starts to feel weird.
I’m going to look up xrandr commands again now and hopefully fix this.
Now it has. 
zfs-dkms 2.1.9-2 and linux62-zfs 2.1.9-11 will be coming along shortly.
Because it was failing to build previously.
1 Like
Thanks for the quick response, cheers!
Tried:
cvt 1920 1080 280 ✔
# 1920x1080 279.75 Hz (CVT) hsync: 358.36 kHz; pclk: 969.00 MHz
Modeline "1920x1080_280.00" 969.00 1920 2104 2312 2704 1080 1083 1088 1281 -hsync +vsync
~ sudo xrandr --newmode "1920x1080_280.00" 969.00 1920 2104 2312 2704 1080 1083 1088 1281 -hsync +vsync
[sudo] password:
~ sudo xrandr --addmode DP-0 "1920x1080_280.00" ✔
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 18 (RRAddOutputMode)
Serial number of failed request: 45
Current serial number in output stream: 46
No clue what to do, need to take a break again, will try again in an hour or so.
Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text
I ran into error messages after the update from Pamac.
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
Error while configuring manjaro-keyring
A restart is required for the changes to take effect.
Looking into /var/log/pacman.logs, the relevant parts shows the following:
2023-03-31T08:04:39-0400] [ALPM] transaction started
[2023-03-31T08:04:39-0400] [ALPM] upgraded archlinux-keyring (20230130-1 -> 20230320-1)
[2023-03-31T08:04:39-0400] [ALPM-SCRIPTLET] ==> Appending keys from archlinux.gpg...
[2023-03-31T08:04:43-0400] [ALPM-SCRIPTLET] ==> Updating trust database...
[2023-03-31T08:04:43-0400] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2023-07-07
[2023-03-31T08:04:43-0400] [ALPM-SCRIPTLET] ==> Updating trust database...
[2023-03-31T08:04:43-0400] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2023-07-07
[2023-03-31T08:04:43-0400] [ALPM] upgraded manjaro-keyring (20221028-4 -> 20230318-1)
[2023-03-31T08:04:43-0400] [ALPM-SCRIPTLET] ==> Appending keys from manjaro.gpg...
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: error reading key: No public key
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] ==> Locally signing trusted keys in keyring...
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] -> Locally signed 2 keys.
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] ==> Importing owner trust values...
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] ==> Disabling revoked keys in keyring...
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] -> Disabled 8 keys.
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] ==> Updating trust database...
[2023-03-31T08:04:44-0400] [ALPM-SCRIPTLET] gpg: next trustdb check due at 2023-07-07
[2023-03-31T08:04:44-0400] [ALPM] transaction completed
I’m running a relatively fresh install of Manjaro XFCE (stable branch) from earlier in March. All updates installed as they came in, and no AUR enabled. Running kernel 6.2.8-1.
I made a post about it in the Manjaro support forum before I found this page.
So far everything seems to run normally. I’ve opted not to try any fixes until I see if these error messages come up again.
I did though get caught by the “nvidia-settings” change of it not being installed by default in the updates. Installing it manually through Pamac caused no errors. Though this seems like poor planning in development. I do agree with Philm’s post in the link for that. This problem will confuse much newer users. It even took me a little to figure out since I’m new to the Manjaro distribution.