So, I now tested GSYNC again myself, and I get either frequent black screen flickers or multiple second periods of black screen. I’ve only tested this with Death Stranding. Not playing a larger variety of games at this moment.
These issues are plaguing the Windows drivers too, it’s annoying as hell.
Qt6 apps (strawberry) crash with a core dump after the recent qt6 update (6.2.1-2). I had to rebuild qt6ct (qt6 settings) against qt6.2.1-2 to get Strawberry working again. I don’t use Strawberry much, so I am unsure if it also did not launch when qt6base updated to 6.2.1-1.
I can’t reproduce that.
@Yochanan Strange that on my Arch VM, I did not have this issue. The only difference there is that I do not have qt6ct installed in VM. Someone on the Endeavour forum had the same issue and also had qt6ct installed.
I have qt6ct installed as well. However, I’m not actively using it at the moment. I’m currently usiung qgnomeplatform-qt6 + adwaita-qt6.
I think there is a problem with the power management for NVIDIA card in optimus laptop with the package nvidia-utils,I opened an issue with more details
I am having this error when installing new kernel linux-515:
Error! Bad return status for module build on kernel: 5.15.0-1-MANJARO (x86_64)
Consult /var/lib/dkms/v4l2loopback/0.12.5/build/make.log for more information.
The information in /var/lib/dkms/v4l2loopback/0.12.5/build/make.log:
DKMS make.log for v4l2loopback-0.12.5 for kernel 5.15.0-1-MANJARO (x86_64)
Mon Nov 1 11:45:01 -03 2021
make: pwd: No such file or directory
Building v4l2-loopback driver...
make -C /usr/lib/modules/5.15.0-1-MANJARO/build M= modules
make: make: No such file or directory
make: *** [Makefile:43: v4l2loopback.ko] Error 127
Probably dkms related only. Have no that issue w/o dkms installed.
details
$ pamac update
Preparing...
Synchronizing package databases...
Refreshing core.db...
Refreshing extra.db...
Refreshing community.db...
Refreshing chaotic-aur.db...
Warning: linux515: downgrading from version 5.15.rc6.211018.g519d819-1 to version 5.15-1
Resolving dependencies...
Checking inter-conflicts...
To upgrade (5):
mpd 0.23.3-1 (0.23.2-1) extra 876.0 kB
openmpi 4.1.1-3 (4.1.1-2) extra 3.4 MB
python-gobject 3.42.0-1 (3.40.1-2) extra 257.6 kB
re2 1:20211101-1 (1:20210901-1) extra 178.3 kB
zenity 3.41.0-1 (3.32.0+55+gd7bedff-1) extra 3.1 MB
To downgrade (1):
linux515 5.15-1 (5.15.rc6.211018.g519d819-1) core 102.1 MB
Total download size: 110.0 MB
Total installed size: 5.4 MB
Apply transaction ? [y/N] y
Download of re2 (1:20211101-1) started
Download of mpd (0.23.3-1) started
Download of re2 (1:20211101-1) finished
Download of mpd (0.23.3-1) finished
Download of python-gobject (3.42.0-1) started
Download of linux515 (5.15-1) started
Download of python-gobject (3.42.0-1) finished
Download of zenity (3.41.0-1) started
Download of zenity (3.41.0-1) finished
Download of openmpi (4.1.1-3) started
Download of openmpi (4.1.1-3) finished
Download of linux515 (5.15-1) finished
Checking keyring... [6/6]
Checking integrity... [6/6]
Loading packages files... [6/6]
Checking file conflicts... [6/6]
Checking available disk space... [6/6]
Running pre-transaction hooks...
Save Linux kernel modules [1/1]
Downgrading linux515 (5.15.rc6.211018.g519d819-1 -> 5.15-1)... [1/6]
Upgrading mpd (0.23.2-1 -> 0.23.3-1)... [2/6]
Upgrading openmpi (4.1.1-2 -> 4.1.1-3)... [3/6]
Upgrading python-gobject (3.40.1-2 -> 3.42.0-1)... [4/6]
Upgrading re2 (1:20210901-1 -> 1:20211101-1)... [5/6]
Upgrading zenity (3.32.0+55+gd7bedff-1 -> 3.41.0-1)... [6/6]
Running post-transaction hooks...
Creating system user accounts... [1/10]
Reloading system manager configuration... [2/10]
Creating temporary files... [3/10]
Arming ConditionNeedsUpdate... [4/10]
Updating module dependencies... [5/10]
Updating linux initcpios... [6/10]
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful
Refreshing PackageKit... [7/10]
Updating Grub-Bootmenu [8/10]
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Info: Separate boot partition not detected
No snapshots found.
If you think an error has occurred , please file a bug report at " https://github.com/Antynea/grub-btrfs "
Unmount /tmp/grub-btrfs.EJdnOqGgRR .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
Updating icon theme caches... [9/10]
Restore Linux kernel modules [10/10]
==> Warning:
-> Kernel has been updated. Modules of the current kernel
-> have been backed up so you can continue to use your
-> computer. However, the new kernel will only work
-> at next boot.
A restart is required for the changes to take effect.
Transaction successfully finished.
$
$ pacman -Qi dkms | head -n4
error: package 'dkms' was not found
$ pacman -Si dkms | head -n4
Repository : extra
Name : dkms
Version : 2.8.6-2
Description : Dynamic Kernel Modules System
EDIT
Installation of raw dkms and reinstalling of 515 does not show the error also. The problem should be a bit deeper.
details
$ pamac install dkms
Preparing...
Choose optional dependencies for dkms:
1: linux-headers: build modules against the Arch kernel
2: linux-lts-headers: build modules against the LTS kernel
3: linux-zen-headers: build modules against the ZEN kernel
4: linux-hardened-headers: build modules against the HARDENED kernel
Enter a selection (default=none):
Synchronizing package databases...
Refreshing chaotic-aur.db...
Resolving dependencies...
Checking inter-conflicts...
To install (1):
dkms 2.8.6-2 extra 54.7 kB
Total download size: 54.7 kB
Total installed size: 177.9 kB
Apply transaction ? [y/N] y
Download of dkms (2.8.6-2) started
Download of dkms (2.8.6-2) finished
Checking keyring... [1/1]
Checking integrity... [1/1]
Loading packages files... [1/1]
Checking file conflicts... [1/1]
Checking available disk space... [1/1]
Installing dkms (2.8.6-2)... [1/1]
Running post-transaction hooks...
Arming ConditionNeedsUpdate... [1/2]
Refreshing PackageKit... [2/2]
Transaction successfully finished.
$
$ pamac reinstall linux515
Preparing...
Warning: linux515-5.15-1 is up to date -- reinstalling
Resolving dependencies...
Checking inter-conflicts...
To reinstall (1):
linux515 5.15-1 core
Apply transaction ? [y/N] y
Checking keyring... [1/1]
Checking integrity... [1/1]
Loading packages files... [1/1]
Checking file conflicts... [1/1]
Checking available disk space... [1/1]
Running pre-transaction hooks...
Remove upgraded DKMS modules [1/2]
Save Linux kernel modules [2/2]
Reinstalling linux515 (5.15-1)... [1/1]
Running post-transaction hooks...
Arming ConditionNeedsUpdate... [1/7]
Updating module dependencies... [2/7]
Install DKMS modules [3/7]
Updating linux initcpios... [4/7]
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: 5.15.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: 5.15.0-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: qat_4xxx
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.15-x86_64-fallback.img
==> Image generation successful
Refreshing PackageKit... [5/7]
Updating Grub-Bootmenu [6/7]
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Info: Separate boot partition not detected
No snapshots found.
If you think an error has occurred , please file a bug report at " https://github.com/Antynea/grub-btrfs "
Unmount /tmp/grub-btrfs.R1hAhvJCr5 .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
Restore Linux kernel modules [7/7]
==> Warning:
-> This computer hasn't been restarted for a while.
-> You are running an old kernel. In order to use a
-> new version of the kernel, please restart your
-> computer as soon as possible.
A restart is required for the changes to take effect.
Transaction successfully finished.
$
$ pamac search --installed header
xorgproto 2021.5-1 extra
combined X.Org X11 Protocol headers
wxgtk-common 3.0.5.1-2 extra
Common libraries and headers for wxgtk2 and wxgtk3
libcups 1:2.3.3op2-3 extra
The CUPS Printing System - client libraries and headers
acl 2.3.1-1 core
Access control list utilities, libraries and headers
linux-api-headers 5.12.3-1 core
Kernel headers sanitized for use in userspace
$
I removed.
I chose the easy way 
.
It was a dependency of simple-droid-cam (AUR) , which I don’t use anymore.
Anyway thanks!
When using Nvidia 495 and Plasma 5.23+, the plasma shell (kwin?) doesn’t graphically update unless I move my mouse around, anyone else? Can’t figure out if this is a bug I should report to KDE or not.
I don’t have that issue and I have 495 nvidia and 5.23.2,maybe you are in Wayland?
Yes, forgot to mention that, sorry. I’ve gotten too accustomed to Wayland as my daily driver it seems.
I’m mostly curious if it’s just on my machine or something everyone/others are experiencing 
I couldn’t get the same to happen in an Arch VM but obviously that’s a bit different when it comes to rendering graphics.
You seem to have KDE+Nvidia+Wayland so to me that’s the death combo. Your VM is totaly different setup. You can’t compare it.
Well we added now 470.82.00. Let’s see how it works.
5 Likes
3 posts were split to a new topic: Package information is present in db, but the package itself is absent on the servers
Are you reporting a bug or requesting a feature? Please open a new thread.
It’s just a question, since 495.44 drivers has a bug, that’s for Nvidia to fix. What I linked was just a workaround to stop the logs from filling up with dbus warnings. Not sure if it prevents dbus-daemon from bloating up. Mine got to over 500 MiB at its worst.
2 Likes
Hi, I noticed that there is a GPU hang regression on the Kernel 5.10.77
Arch Linux have already a patch for this:
1 Like