I also got this error…
error: tensorflow-opt-cuda: signature from "Sven-Hendrik Haase <sh@lutzhaase.com>" is invalid
:: File /var/cache/pacman/pkg/tensorflow-opt-cuda-2.15.0-4-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] ^C
Interrupt signal received
Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text
Are the shutdown problems with the LTS kernels >515 also on suspend/hibernate/resume actions?
postgresql seems to have been updated - the database needs upgrading…
I just deleted mine and recreated it.
I’m testing 6.7.0rc4-6 now and everything seems to work fine, wifi can be switched on-off over and over without freezes. 
Looks like the “Wifi causing hangup” problem is more generic than specific to a particular chipset:
But it looks like the problem is currently mitigated in 6.7 branch … more tests needed.
Kernel 6.1.66-1 is also affected. Any tree that back-ported 7e7efdda6adb wifi: cfg80211: fix CQM for non-range use that does not contain 076fc8775daf wifi: cfg80211: remove wdev mutex (which does not apply cleanly to 6.6.y or 6.6.1) will be affected. Upstream solution so far: [PATCH] wifi: nl80211: fix deadlock in nl80211_set_cqm_rssi (6.6.x) — Linux Stable Kernel Updates
If anyone other than me is using rtl-sdr dongles (quite possibly not, as they’re fairly niche), the latest update introduces a change which seems to cause problems in some circumstances. There’s a new group “rtlsdr” and it seems this causes problems unless a user accessing the dongles has been added to that group.
I need to do a little more testing to confirm adding the user to rtlsdr is the final fix (I have to wait until some radio timeshifting jobs release my dongles). I’ll come back with my answer in a few hours.
[Edit]: this does seem to solve the problem.
Not so. Dolphin, Gwenview, Kate etc are still at 23.08.3.
Upstream released new kernels as we speak with the offending patch reverted. I simply triggered those: [Regression] 6.1.66, 6.6.5 - wifi: cfg80211: fix CQM for non-range use
After the update my DE used a completely different icon set. Turns out the ePapirus icon theme got split into its own package and since the files for it disappeared my DE used a fallback theme.
To fix it, you can either select the papirus icon theme, which you should still have installed and is very similar, or you can install the epapirus-icon-theme package to get the exact icons previously in use back.
And what DE 
? is with the failing the ePapirus icons?
I’d assume something similar happens regardless of the specific DE as it’s about the icon theme you have selected. But to answer your question: Cinnamon.
Same problem here using Kernel: 6.1.66-1-MANJARO. No problem if I boot using Kernel: 5.10.203-1-MANJARO.
inxi -F
System:
Host: macmini51 Kernel: 5.10.203-1-MANJARO arch: x86_64 bits: 64
Desktop: Xfce v: 4.18.1 Distro: Manjaro Linux
Machine:
Type: Laptop System: Apple product: Macmini5,1 v: 1.0
serial: <superuser required>
Mobo: Apple model: Mac-8ED6AF5B48C039E1 v: Macmini5,1
serial: <superuser required> UEFI: Apple v: 135.0.0.0.0 date: 06/13/2019
CPU:
Info: dual core model: Intel Core i5-2415M bits: 64 type: MT MCP cache:
L2: 512 KiB
Speed (MHz): avg: 2124 min/max: 800/2900 cores: 1: 1840 2: 1916 3: 2183
4: 2559
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
driver: i915 v: kernel
Display: x11 server: X.Org v: 21.1.9 driver: X: loaded: modesetting
dri: crocus gpu: i915 resolution: 1360x768~60Hz
API: OpenGL Message: Unable to show GL data. glxinfo is missing.
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
driver: snd_hda_intel
API: ALSA v: k5.10.203-1-MANJARO status: kernel-api
Server-1: PulseAudio v: 16.1 status: active
Network:
Device-1: Broadcom NetXtreme BCM57765 Gigabit Ethernet PCIe driver: tg3
IF: enp2s0f0 state: down mac: 3c:07:54:67:10:09
Device-2: Broadcom BCM4331 802.11a/b/g/n driver: wl
IF: wlp3s0 state: up mac: 7c:c3:a1:73:03:cd
Bluetooth:
Device-1: Apple Bluetooth Host Controller driver: btusb type: USB
Report: btmgmt ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: 7C:C3:A1:73:03:CE bt-v: 4.0
Drives:
Local Storage: total: 239.41 GiB used: 25.63 GiB (10.7%)
ID-1: /dev/sda vendor: Timetec model: SATA 256GB size: 238.47 GiB
ID-2: /dev/sdb model: General USB Flash Disk size: 961 MiB type: USB
Partition:
ID-1: / size: 78.57 GiB used: 25.59 GiB (32.6%) fs: ext4 dev: /dev/sda4
ID-2: /boot/efi size: 196.9 MiB used: 23.3 MiB (11.9%) fs: vfat
dev: /dev/sda1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
System Temperatures: cpu: 51.0 C mobo: 50.0 C
Fan Speeds (rpm): N/A
Info:
Processes: 211 Uptime: 13m Memory: total: 8 GiB available: 7.68 GiB
used: 1.4 GiB (18.2%) Shell: Bash inxi: 3.3.31
Wifi problems will be addressed with 6.1.67 and 6.6.6 kernels. The discussion can be followed here: [Regression] 6.1.66, 6.6.5 - wifi: cfg80211: fix CQM for non-range use
You can add MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 14c3:0608 class-ID: 0280 to the busted wifi drivers…
6.1.65-2 and 6.5.4-3 ship with a potential fix: [PATCH] wifi: nl80211: fix deadlock in nl80211_set_cqm_rssi (6.6.x) Upstream however decided to revert the offending patch as stated already. Anyway, test and give feedback.
If the DE was Gnome, icon and other themes could no longer be compatible due to the recent update to Gnome 45, which requires new themes, addons, widgets, etc, to be 100% compatible going forward; no more gtk-3.0/gtk-4.0 themes.
In my case (chipset Mediatek MT7922) updating the kernel (mt7921e driver) to version 6.1.65-2 helped (which I can confirm after a quick test).
After a direct reboot I got the error
mt7921e: {address} driver itself failed
mt7921e: probe from {address} failed with error -5
but powering the laptop on and off fixed it.
Checking mine I have “read access only”:
sudo ls -SAhl /etc/sudoers.d/
total 4.0K
-r–r----- 1 root root 21 Jul 14 00:45 10-installer
No problems using sudo or switching to root
Sure, a different problem could result in the same symptoms. Don’t see how that’s relevant given that I’ve already debugged it and provided the solution.