Right after the update im experiencing ~3 seconds game freezing, when i play a native Linux (non-steam) game ![]()
I had no issue before this update. I don’t have tested Proton games yet.
With this update I’ve run into the a recent issue that I encountered a few updates ago.
The problem running the the reset script (mentioned in the above thread) is not resolving the issue. ![]()
I’m planning to try once again after posting this.
I’ve followed your advice and installed manjaro-pipewire with
sudo pacman -Syu manjaro-pipewire
but I had to remove pulseaudio-bluetooth at first with
sudo pacman -Rdd pulseaudio-bluetooth
just like @Yochanan recommended in his post above.
inxi -Axx now reports:
Audio:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
bus-ID: 08:00.1 chip-ID: 1002:ab28
Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s
lanes: 16 bus-ID: 0a:00.4 chip-ID: 1022:1487
API: ALSA v: k6.6.83-1-MANJARO status: kernel-api with: aoss
type: oss-emulator
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
I’m wondering whether it would be appropriate to mention the sound problems with Pipewire/Pulseaudio in the ‘Known issues and solutions’ wiki post on top since there seem to be a lot of people affected by it based on the replies in this announcement.
I’ve noticed @philm mentioning it in the first post before. I was just talking about the second post (wiki post?) because that’s where I usually start looking if I would potentially run into any problems and for possible solutions.
This thread may be useful:
TLDR:
Update: I’ve resolved this using the previous solution mentioned in the thread
The only thing that it took 1 logout and 2 reboots to have an impact.
Seen and replied to that thread a few weeks ago. Shared the Arch forum post which was mentioned.
It had no fix for users using amd-pstate driver with amd-pstate=passive flag.
Only solution is to stick to 6.12.x for now.