After the update everything seems fine, except for a small annoying bug in Wine. Some of the system tray icons for Windows programs appear black.
Maybe it’s a cache problem.
I finally fixed the Wine systray icon errors by updating Wine to version 9.16.
please link to new topic. I have the same issue.
Edit: Replied in Unable to boot past Mobo/Manjaro Loading screen after 09/02 update - #36 by luzpaz
I gave up and reinstalled the operating system and it worked again. But if someone wants to continue from where I left off on this thread here’s the link…
This update went smoothly and I’m back in my KDE Plasma desktop session, but I did get a new P3 in the journal…
journalctl -b 0 -p 3 listed a new entry related to sd-pam “Failed to release session”, so I reran journalctl -b 0 --since '2024-09-02 22:16' to get a little more context:
Sep 02 22:16:08 AMD-Ryzen9-7940HS (sd-pam)[975]: pam_unix(systemd-user:session): session closed for user sddm
Sep 02 22:16:08 AMD-Ryzen9-7940HS (sd-pam)[975]: pam_systemd(systemd-user:session): Failed to release session: Caller does not belong to any known session.
Sep 02 22:16:08 AMD-Ryzen9-7940HS (sd-pam)[975]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[sddm] ruser=[<unknown>] rhost=[<unknown>]
System appears to be up and running fine despite this new journal entry.
sudo hddtemp /dev/sd{a..h}
The SATA temperature acquisition problem that was pointed out a month ago has been resolved with the update applied today.
Thank you to the manjaro team.
Now I can finally remove kernel 6.9.
Cinnamon edition.
3 posts were split to a new topic: Pipewire-pulse and pulseaudio are in conflict
NodeJS v22.7.0 is the official version for this “stable” update, but it is known to cause data corruption. I have already experienced this myself.
With this update on KDE with an nvidia GPU, I’m experiencing an issue where UI elements freeze. For instance, I can type my password at login, but the input won’t show any changes until I submit it; I can click items in the taskbar but the don’t show hovers until the click; kitty doesn’t show any changes until I unfocus and refocus the window. Really weird… Everything works fine when running on my Intel igpu, but it’s a bit stuttery since the triple buffering improvements are only available in Plasma 6.1.
Pipewire volume remains low and won’t go back up.
This has been happening since mid- or late July.
The sound volume remains very low.
I can point this out because the volume setting on the HDMI output monitor remains the same.
This does not happen with any Linux distribution other than manjaro. I’m multi-booting so I can compare. I mainly use manjaro and Cinnamon.
I was hoping it would be fixed eventually, but since no one has pointed it out for over a month, I decided to let you know just in case.
If it’s just a problem with my HW, there’s nothing I can do about it.
It’s not a fatal problem, but it’s been bothering me for a while.
inxi -Farz
System:
Kernel: 6.10.6-10-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-6.10-x86_64
root=UUID=b946ad7d-99d9-4b18-b26a-bc2f6a095f42 rw rootflags=subvol=@
zswap.enabled=0 amd_pstate=active sysrq_always_enabled=1
Desktop: Cinnamon v: 6.2.9 tk: GTK v: 3.24.43 wm: Muffin v: 6.2.0
with: plank tools: avail: cinnamon-screensaver vt: 7 dm: LightDM v: 1.32.0
Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX X570-F GAMING v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 5013 date: 03/18/2024
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K270
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3+ gen: 3
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 2 microcode: 0xA20120E
Topology: cpus: 1x dies: 1 clusters: 1 cores: 12 threads: 24 tpc: 2
smt: enabled cache: L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB
desc: 12x512 KiB L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 550 min/max: 550/4951 scaling: driver: amd-pstate-epp
governor: powersave cores: 1: 550 2: 550 3: 550 4: 550 5: 550 6: 550 7: 550
8: 550 9: 550 10: 550 11: 550 12: 550 13: 550 14: 550 15: 550 16: 550
17: 550 18: 550 19: 550 20: 550 21: 550 22: 550 23: 550 24: 550
bogomips: 177359
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow mitigation: Safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
470/480/570/570X/580/580X/590] vendor: Micro-Star MSI driver: amdgpu
v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20
pcie: gen: 3 speed: 8 GT/s lanes: 8 link-max: lanes: 16 ports:
active: DP-1 empty: DP-2, DP-3, DVI-D-1, HDMI-A-1 bus-ID: 0c:00.0
chip-ID: 1002:67df class-ID: 0300 temp: 43.0 C
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2 driver: X:
loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48")
s-diag: 1165mm (45.88")
Monitor-1: DP-1 mapped: DisplayPort-0 model: Philips PHL BDM4350
serial: <filter> built: 2017 res: 3840x2160 hz: 60 dpi: 102 gamma: 1.2
size: 953x543mm (37.52x21.38") diag: 1097mm (43.2") ratio: 16:9 modes:
max: 3840x2160 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.6-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 570 Series (radeonsi
polaris10 LLVM 18.1.8 DRM 3.57 6.10.6-10-MANJARO) device-ID: 1002:67df
memory: 7.81 GiB unified: no
API: Vulkan v: 1.3.279 layers: 1 device: 0 type: discrete-gpu name: AMD
Radeon RX 570 Series (RADV POLARIS10) driver: mesa radv v: 24.1.6-arch1.1
device-ID: 1002:67df surfaces: xcb,xlib
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere HDMI Audio [Radeon RX
470/480 / 570/580/590] vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8 link-max: lanes: 16
bus-ID: 0c:00.1 chip-ID: 1002:aaf0 class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 0e:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.10.6-10-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: PipeWire v: 1.2.3 status: active with: 1: pipewire-pulse
status: active 2: pipewire-media-session status: active 3: pipewire-alsa
type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli
Network:
Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 06:00.0
chip-ID: 8086:2725 class-ID: 0280
IF: wlp6s0 state: up mac: <filter>
IF-ID-1: wgpia0 state: unknown speed: N/A duplex: N/A mac: N/A
Info: services: NetworkManager, smbd, sshd, systemd-timesyncd,
wpa_supplicant
Bluetooth:
Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-6:3 chip-ID: 8087:0032
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Hi, I’m also using Cinnamon and have the same sound chip as you (Starship/Matisse HD Audio) but have no problem with it.
Comparing the results of inxi -Farz on my PC, I noticed that you have sndiod as server-1 and PipeWire as server-2, whereas I only have PipeWire as server-1.
So, unless you are using some MIDI instruments and really need the sniod server, you could perhaps remove the sndio package and see if it helps…
More info on sndio, just in case: sndio(7) — Arch manual pages
This often happens when the master vcolume is reduced. You can increase this with alsamixer. If alsamixer volumes are at 100% for all sound cards and the issue persists, some users had issues with sound depending on the kernel so test with an LTS kernel.
Smart status seems to be still good and healthy. No warnings and several tools like nvme-cli, smartctl and KDE-Partitionmanagers Smart-Status say it is “good”.
thanks.
I decided to try reverting to the settings from a year ago (startup program), and if that doesn’t work, I’ll try deleting it (sndio).
thanks.
The alsamixer setting was 100%.
When pipewire was unstable I used to run a startup program. I tried that and the problem went away. I took a break for a while.
About 2 years ago, around the time I removed Pulaseaudio and switched to Pipewire, I was having repeated issues with the sound disappearing, so I used this to work around the problem.
bash -c 'PIPEWIRE_RESET ; easyeffects'
PIPEWIRE_RESET
rm -v $HOME/.local/state/pipewire/media-session.d/* ; systemctl --user restart pipewire.service ; systemctl --user restart pipewire-pulse.service
plasma6 wayland on lenovo thinkpad P1 Gen 4i
problems after resume from suspend, LDEs of FnLock, Microphone are off
led of Power button blinking, backlight keyboard not working
have to reboot for correct working
notice only few days ago
This update broke hibernation for me (kernel 6.6, NVIDIA graphics using Nouveau). Black screen when resuming, kernel seems to panic (not even SysRq helps).
However, the proposed fix
[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"
did not seem to have any noticeable effect.
Upgrading to kernel 6.10 restored hibernation, at least for now (fingers crossed!).
Although it still behaves weirdly: when entering hibernation, screen turns black, HDDs spin down, then screen reappears, HDDs spin up again, then machine turns off. Same weirdness on resume from hibernation.
I really hate it when essential functionality breaks 
Do you have sufficient swap space configured? For hibernation, the default required is at least equal to the amount of system RAM.
This has been the case on my systems for a long time (at least with Plasma6; maybe also with 5.xx). I don’t recall if the mechanical HDD span up again as I didn’t notice it do a second spin-up; I have an SSD now so can’t tell.
Nothing to worry about, as far as I can tell.
This is not unique to Manjaro or Plasma. Same happens on different hardware using Mint (21.3) with Xfce.
Plenty of SWAP in all cases.
It’s not the same with resume, however. Just get the regular bootup sequence and a “normal” resume. I have removed “quiet” and “splash”.
seems my problem is related to kernel 6.10.6-10
kernel 6.6.47-1 don’t give that problem
Maybe this will be fixed with linux611? … I’d stick with LTS if they work for you though.
There are other threads regarding KB backlight (etc.) LEDs misbehaving after resume. I should re-check those and may link to your post if they haven’t already tried the other kernels. 
I don’t recall this happening on Plasma 5 at all - but for me that was on Gentoo/OpenRC, which was an entirely different setup, although it was the exact same machine.
Well, spinning HDDs up and down in short intervals is certainly not a good thing, not to mention completely unnecessary. On my machine, there are 6 HDDs (RAID) doing that spinning dance each time hibernation is used, which usually occurs once a day.
Just checked this again and out of 5 test runs, the unnecessary spin down + spin up occurred on 3 resumes while the other 2 didn’t do anything out of the ordinary (like it should be). But all 5 resumes succeeded. Even weirder.