Wake up from suspend are very slow on 5.18.14
It recognizes no mouse / keyboard inputs.
Stuck at lockscreen
5.18.15 does not have a fix for that.
1 Like
Tested and confirmed. Updated my original post.
1 Like
@ufo_driver @Gquirt @gjoe @CarlLaFong It has landed. Got it on my machine and everything is back to normal. No need for the workaround.
3 Likes
Can I just say that I love how on top of things the Manjaro team is? Even when there’s a small issue I’ve never not seen it fixed within a day or two.
Buy some merch. They deserve the support and the advertising! (For the record, I have a Manjaro draft hoodie and I love it.)
10 Likes
A post was merged into an existing topic: VisualBoyAdvance-M no longer opening roms after last stable update
After the July 29 stable Update my Virtualbox crashed. NS_Error_Failure
Install latest Extension Pack.
ok this works.
thank you !
Same thing happened to me Virtualbox no longer works.
I’m not super concerned but Firefox segfaults on start
[Sat Jul 30 17:00:23 2022] firefox[2367]: segfault at d8 ip 00007fd504389814 sp 00007fffdfe33158 error 4 in libX11.so.6.4.0[7fd50437a000+8b000]
[Sat Jul 30 17:00:23 2022] Code: 84 00 00 00 00 00 f3 0f 1e fa 8b 47 1c c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 8b 47 74 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 87 d8 00 00 00 c3 0f 1f 40 00 f3 0f 1e fa 48 63 f6 48 c1 e6
Beyond that it works as usual
Ok, I am not exactly sure how, but after running the update yesterday after the software manager notified me of a number of updated packages, my system tried to come back up using the real time kernel, which basically caused all kinds of booting issues. I was using 5.15 LTS when performing the update, so is there any way to determine why my system was using the real time kernel after the update? This was on a machine installed at 21.3.5 and only a week or two old, so really had no history with any previous kernels.
I had to manually uninstall the kernel and manually install 5.18.14 afterwards. I also uninstalled virtualbox as the “watchdog: BUG soft lockup” error seemed to indicate issues with “vboxdrv(0E+”, but noticed when manually installing 5.18.14 that the software manager added virtuabox elements back again, although my software manager doesn’t show any at this point.
All in all a pretty confusing upgrade for a semi-knowledgeable user.
Because you manually installed it at some point. It could have been by accident.
So this particular install is my first Manjaro experience, having come from using Garuda for the last 6+ months. I installed a few weeks ago from the available .iso and updated when notified. I know 5.15 LTS was the version I was running yesterday, and I haven’t touched one button in that section of the system manager. If I did anything to cause this, I have no recollection of doing that.
Based on your idea, I wonder if I didn’t add the RT kernel as an option during the initial install, and didn’t realize the ramification of doing so. Is there an option during the live installer to choose the RT kernel?
I have a problem with dkms with v4l2loopback-dkms
( 9/19) Install DKMS modules
==> dkms install --no-depmod v4l2loopback/0.12.5 -k 5.15.55-1-rt48-MANJARO
Deprecated feature: REMAKE_INITRD
Error! Bad return status for module build on kernel: 5.15.55-1-rt48-MANJARO (x86_64)
Consult /var/lib/dkms/v4l2loopback/0.12.5/build/make.log for more information.
==> WARNING: `dkms install --no-depmod v4l2loopback/0.12.5 -k 5.15.55-1-rt48-MANJARO' exited 10
the make.log shows
DKMS make.log for v4l2loopback-0.12.5 for kernel 5.15.55-1-rt48-MANJARO (x86_64)
dom 31 jul 2022 00:31:17 -04
Building v4l2-loopback driver...
make -C /usr/lib/modules/5.15.55-1-rt48-MANJARO/build M=/var/lib/dkms/v4l2loopback/0.12.5/buil
d modules
make[1]: se entra en el directorio '/usr/lib/modules/5.15.55-1-rt48-MANJARO/build'
CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.o
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
make[2]: *** [scripts/Makefile.build:288: /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback
.o] Error 1
make[1]: *** [Makefile:1886: /var/lib/dkms/v4l2loopback/0.12.5/build] Error 2
make[1]: se sale del directorio '/usr/lib/modules/5.15.55-1-rt48-MANJARO/build'
make: *** [Makefile:43: v4l2loopback.ko] Error 2
Im using the exact same Laptop and also with KDE and no touchpad issue.
But im using 5.15 LTS Kernel… maybe try this out.
I’m using a laptop (Asus Tuf A17 2022 w/ nvidia dGPU), and the backlight of the display panel is always off after this update using kernel 5.15, the 5.10 is fine.
Have a similar issue on 5.15 LTS.
I can enter lockscreen password, but it just goes back to suspend after I hit enter. After which, the lockscreen is completely unresponsive (recognizes no keyboard / mouse inputs), and the only way I can get back in is with a reboot.
Used Timeshift to restore to before update and no longer have the issue.
Yup, did it that way too, updated after recovery w/ ignoring the kernel update:
but don’t prefer this way… because of security.
$ sudo pacman-mirrors -f && sudo pacman -Syyuu --ignore linux518