You may want to read the 2022-06-12 troubleshoot note in the second post @Fabian
It’s BACK ! A few updates ago (June) my wine game stop working. Half way through the intro, it got stuck on a black screen. That was not a wine problem as I downgrade it. This new update has finally fix it. Both my Nvidia (GT750TI) and AMD (RX570) based computer had the problem at the same time. It is not a “driver” issue apparently nor wine, so I don’t know but that’s good again. Tx
I’m not sure it’s related to the update, but I didn’t edited nor changed anything else.
Upon reboot the system, LightDM didn’t start with message « Failed to start Light Display Manager».
I solved with this solution.
1 Like
Temporary workaround for now is to use the flatpak version of steam:
sudo pacman -S flatpak --needed --noconfirm
sudo flatpak install com.valvesoftware.Steam -y
You can use flatseal (another flatpak app) to grant it access to your existing game library so you don’t have to re-download your games (add the game library install path under “Other files” under “Filesystem”).
sudo flatpak install com.github.tchx84.Flatseal -y
FYI to @philm and advanced users: patched glibc and lib32-glibc are available here. They remove the commit that broke EAC.
After applying the update & rebooting I get a white screen saying "“uh oh, something went wrong, the system cant recover” 
I do have a timeshift, but not sure how to revert if I cant boot. I do have a USB somewhere…
OK, managed to fix it 
booted to tty & ran full update again. it was already downloaded, but a bunch of things had been skipped. after a reboot back to normal.
2 Likes
Ah, nice. 
Suspend is broken on my laptop again. This is like the third time an update did this (while staying on the LTS kernel 5.15.x series).
Something’s going on with upstream kernel development. I’ve experience three or four issues while on 5.15.x that break suspends and/or reboots.
What makes me resistant to troubleshoot this (again) is that the previous times all my troubleshooting efforts were in vain, since it was a matter of waiting for the regression to be fixed by the upstream kernel developers.
2 Likes
i have the weird scratching sound again. i had the same problem with the RC of kernel 5.19, so i went back to 5.17
it appears sometimes when i start a video/music/etc after i do not play any sounds for a while. i cannot even mute it. i scratches for a few sec and then its gone as long as sounds playing
i have an RX580 and i use HDMI for soundoutput
with kernel 5.19.0-2 the leds showing microphone and audio disabled not working
5.18 and 5.15 they hare fine for it
Since last Stable im still experience Firefox Coredumb errors.
1 Like
Yes, kernel 5.19 has the same problem as 5.18 with scratching sound sound on AMD Ellesmere HDMI Audio Radeon RX 590. Noise starting sound on AMD Ellesmere HDMI Audio Radeon RX 590.
Fortunately, kernel 5.15 does not have that problem.
1 Like
Can this glibc issue be added to the list of known issues in the Known issues and solutions? I am also affected by this issue and can’t play some games. I always look at this list of known issues for serious issues before updating.
@thingsiplay having EAC broken by a core package update is not critical for us as a distro. However, for those who are affected I’ve added the flatpak workaround and mentioned the patched glibc packages we don’t recommend to install officially.
having issue with wifi usb adapter TP-LINK TL-WN821N after this kernel update. In fact all my network devices disappeared after update and running inxi -N returns “No PCI device data found.” message.
edit
was able to get it working by installing rtl8192eu-git drivers package. Previously it was working on rtl8192eu package itself but its not a case anymore.
My update has no problem, but I suddenly got two orphaned packages:
intel-oneapi-mkl
onednn
Not sure what to do with them. I assigned them as explicit but don’t know where did they come from.
This update broke gcc/g++:
-- The CXX compiler identification is GNU 12.1.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - failed
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ - broken
CMake Error at /usr/share/cmake/Modules/CMakeTestCXXCompiler.cmake:62 (message):
The C++ compiler
"/usr/bin/c++"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: /home/ave/Documents/oss/wors_tracer/build/CMakeFiles/CMakeTmp
Run Build Command(s):/usr/bin/ninja cmTC_6166d && [1/2] Building CXX object CMakeFiles/cmTC_6166d.dir/testCXXCompiler.cxx.o
[2/2] Linking CXX executable cmTC_6166d
FAILED: cmTC_6166d
: && /usr/bin/c++ CMakeFiles/cmTC_6166d.dir/testCXXCompiler.cxx.o -o cmTC_6166d && :
/usr/bin/ld: /usr/lib/libm.so.6: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /usr/lib/libm.so.6 when searching for /usr/lib/libm.so.6
/usr/bin/ld: cannot find /usr/lib/libm.so.6
/usr/bin/ld: /usr/lib/libm.so.6: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /usr/lib/libm.so.6 when searching for /usr/lib/libm.so.6
/usr/bin/ld: /usr/lib/libmvec.so.1: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /usr/lib/libmvec.so.1 when searching for /usr/lib/libmvec.so.1
/usr/bin/ld: cannot find /usr/lib/libmvec.so.1
/usr/bin/ld: /usr/lib/libmvec.so.1: unknown type [0x13] section `.relr.dyn'
/usr/bin/ld: skipping incompatible /usr/lib/libmvec.so.1 when searching for /usr/lib/libmvec.so.1
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
Or is the issue deeper than I can see?
❯ pacman -F /usr/lib/libm.so.6
usr/lib/libm.so.6 is owned by core/glibc 2.35-6
❯ pacman -Qi glibc
Name : glibc
Version : 2.36-1
So why is libm owned by an old glibc? Wasn’t it supposed to be upgraded?..
Anyways, downgrading gcc, gcc-libs, glibc and lib32-glibc, clang, llvm, llvm-libs helped. Please fix.
saddly that is right. tried 5.18 and it has the same sound problem.
i guess i go back to 5.15 and hope it does not have to much impact on gaming with proton
It’s not. -F is using own database, and you need to update it with -Fy. To query actual packages on your system you need to use -Q, in your case -Qo.
EDIT: Also you can edit the same post like I just did, and not post 10x one after another.
I always update with $ sudo pacman -Syuw . This only downloads and checks all packages without installing them, which I then later do from the tty.
Two packages, python-pivy and freecad, were marked as ‘marginal trust’ or corrupted, and thus asked to be removed, which I did. Re-downloading those two packages had the same result.
I tried to ‘fix’ the key problem by the old method of downloading archlinux-keyring and manjaro-keyring, and then $ sudo pacman-key --init , --populate, --refresh-keys but the latter step produced very many errors and possibly further corrupted my key database.
I then turned to the Manjaro wiki and also found the old method there but it is now scratched out. Luckily there is now a new method which worked to get my key database re-established.
The two problem packages were downloaded and checked without problems and I could proceed to tty $ sudo pacman -Su for a successful update.
1 Like