On my Thinkpad P14s AMD Gen 1 running Kernel 6.0.6-1 fprintd does not work anymore
Nov 07 12:20:35 machineid fprintd: identify has failed: 502
Nov 07 12:20:35 machineid fprintd: Device reported an error during identify for enroll: Unexpected result from device 502
Nov 07 12:20:53 machineid fprintd: Authorization denied to :1.131 to call method 'Claim' for device 'Synaptics Sensors':>
Nov 07 12:21:07 machineid fprintd: Authorization denied to :1.131 to call method 'Claim' for device 'Synaptics Sensors':>
Nov 07 12:21:16 machineid fprintd: Authorization denied to :1.131 to call method 'Claim' for device 'Synaptics Sensors':>
Clearing fingerprint memory from BIOS did also not resolve the issue.
Same with Kernel 6.1.0rc2-1.
Also, after sleep touchpad clicking and two finger scrolling/clicking does not work anymore.
Even resetting it with
sudo modprobe -r psmouse && sudo modprobe psmouse
does not work (anymore… it did on older 6 Kernel versions which broke the touchpad on wake as well… not sure what to do about this, so far only a reboot did helps).
Yes, but shouldn’t it? Virtualbox balked that the versions do not match, so there is a version requirement, but we don’t specify it.
Is it because we need to allow a version mismatch, as in: you can sometimes not update the host-modules before all guest machines have their guest-utils upgraded too? Otherwise I dont see why we allow the mismatch to happen.
That may be inherently unneeded as Manjaro does not support partial upgrade, in the sense it is expected that all packages are used at their latest version. The case here is that an EOL kernel was used, which should have been switched for another.
I get a “No Signal” error message with a graphic drawing tablet, “xp-pen 15.6 Pro”, as 2nd monitor since the update. Using KDE. On Manjaro Live USB and Ubuntu the drawing tablet works without an error.
After this update LibreOffice Calc often recovers an open document after screen lock with KDE.
So right after logging in after screen lock Libre Office opens a popup and offers the already open document for recovering.
Same behaviour when switching between different desktop sessions.
I’m still running the same “old” issue with VirtualBox and Intel 9th gen CPU: I have to have ibt=off in kernel parameters in order for VMs to start. I’m running 6.0.6-1 kernel and dkms-built vbox kernel modules.
This solution didn’t work for me, however, I found a solution that did work: After rolling back with Timeshift, I disabled my secondary monitor before applying the updates. After rebooting, I re-enabled the secondary monitor.
VirtualBox Guestadditions 7.0.2. causes crash on some Guest Systems.
Crashes Win10, win11 and Win Server 2016.
The new WDDM Driver causes this crash.
Workaround: Disable 3D Support before you install the Guest Additions on the Guest.
Build in VNC-Server Crashes the guest randomly.
RDP Connection directly to the guest does not work or ends up in a black Screen.
Blame this all on the new WDDM driver.
.Net aplications in the guest will only work over Network with the enp67s0 Driver.
All in all 7.0.2 appears to be 20% slower then 6.1.38
Well there are many Bugs still in 7.0.2 virtualbox. In the end it should not be in the stable branch.
Somebody can confirm this bugs?
Is there a workaround for VNC and RDP?
My workaround at the moment is using noMachine to connect to my VMs.