maybe you can downgrade both packages to v. 2.36-7 (not tested) e.g.
pacman -U https://archive.archlinux.org/packages/g/glibc/glibc-2.36-7-x86_64.pkg.tar.zst
pacman -U https://archive.archlinux.org/packages/l/lib32-glibc/lib32-glibc-2.36-7-x86_64.pkg.tar.zstI know, but I donât have the need to, since everythingâs fine with my things. I mentioned that as mine is at the version that gives you guys problems, but I donât have any problems.
there are definitely many problems with it, but not with all systems - I did another upgrade on a system where these problems do not occur - maybe manjaro firmware or kernel modules ⌠no idea
Perhaps a custom software package? You could compare you list with @OfficerActionâs to see if you want to.
yeah, it is strange 
the other system (intel i5) is identical to the (intel i7) except for the firmware the i5 upgrade worked without intervention ⌠both w/ an intel GPU
see:
Doesnât compute. Error.
Unknown.CPU.
OK, Iâll stop now.
haha sorry, i6 means i7-6700
AAAAH.
Well, it runs perfectly on my i7-8700 as well.
my question is, why same plasma version works w/ glibc 2.36-7 and not w/ glibc 2.37-2 on some systems?
Some software package, is what I think.
or some lib32 libraries havenât been adjusted (updated) yet⌠apart from the other system I use jack2 and also some lib32 packages (audio stuff) but that would be very unlikely unless a lib32 GPU library is affected
As previously stated:
Answering my own question about constantly re-enabling powersave power profile â this has now been fixes with either this update, or the one before (I managed to skip that one on my affected computer). Setting Performance, Balanced or Powersave now work as expected.
Strange that two computers with KDE gets updates, one is fine, the other has the canât launch and no icons problem.
Very minor regression that I noticed and Iâm not even sure what caused it (probably kernel 6.1, I jumped to it with this update): after the PC unlocks or wakes up from sleep, the num lock light on the keyboard stays off. But itâs still on, itâs just the light.
Iâm running an Nvidia GPU with the proprietary driver, connected via DisplayPort to a âGSync-compatibleâ monitor. My desktop is KDE Plasma, under Wayland.
After this update, my monitor was constantly dropping out to a black screen for a few seconds, in what seemed to be a soft reboot of some kind. When the picture reappeared, it would work for a couple of seconds before blacking out again. It stopped when I went into Plasma settings and changed the monitorâs refresh rate to its highest supported rate.
Possibly related is the fact that this update is when the âAdaptive sync: Never/Always/Automaticâ drop-down menu appeared for the first time on that same page of Plasma settings. It defaulted to âalways,â and changing it to other values does not prevent the constant blackouts when changing the refresh rate.
Not sure if this was said explicitly or not. I added PAMAC_CLI_AUTH=1 to /etc/environment, logged out and logged back in again and now running pamac upgrade in a cli allows authorization natively, no more intrusive pop-up from the GUI asking for a password.