Audio gets choppy after sleep/wakeup

Ask Fedora
,
1

I have this reoccurring issue with audio. Where it gets choppy on eg. Youtube, system sounds, Steam game audio after closing the lid on my laptop and waking the computer back up. Restarting the computer fixes the issue, but I’d like to have a solution without restarting.
Also when this issue occurs the clock jumps forward by 2h.

It’s worth mentioning I am a beginner at using the konsole and know very little about linux and Fedora.

Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.2.7-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 22 × Intel® Core™ Ultra 7 155H
Memory: 32 GiB of RAM (30.9 GiB usable)
Graphics Processor: Intel® Arc
Manufacturer: LENOVO
Product Name: 83E2
System Version: Yoga Pro 7 14IMH9

Hope you can help :slight_smile:

2

When the audio is broken try

systemctl --user restart pipewire

and if it dosent fix it try for

systemctl --user restart wireplumber

Also another reason that this might be happening is because of clock shift, the time on your system changes after sleep, if that is the case you can sync the clock to your network time via (this was the issue and the fix when it happened on my laptop)

sudo timedatectl set-ntp true
3

Thank you for your response @sketch-exe. I will try this the next time the issue occurs and report back if this solves it.

4

Because the clock jumps at the same moment the audio breaks, I’d check the clock first. Right after the next wake, run timedatectl in Konsole, compare the Local time, Universal time and RTC time lines, and check whether “RTC in local TZ” says yes or no. Then run journalctl -b -g "PM: suspend|Time has been changed" to see the times Fedora recorded going to sleep and waking up. If Windows is also installed on this laptop, set it to keep the hardware clock in UTC by adding a DWORD named RealTimeIsUniversal with value 1 under HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation.

Drafted with AI, reviewed by me.

5

Ok the issue is back. Windows is not installed on this laptop, but it was.
Results:

Gaute@fedora:~$ timedatectl
Local time: Sat 2026-09-26 12:08:38 CEST
Universal time: Sat 2026-09-26 10:08:38 UTC
RTC time: Sat 2026-09-26 10:09:39
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: no
NTP service: active
RTC in local TZ: yes

Warning: The system is configured to read the RTC time in the local time zone.
This mode cannot be fully supported. It will create various problems
with time zone changes and daylight saving time adjustments. The RTC
time is never updated, it relies on external facilities to maintain it.
If at all possible, use RTC in UTC by calling
‘timedatectl set-local-rtc 0’.

Gaute@fedora:~$ journalctl -b -g “PM: suspend|Time has been changed”
Sep 26 02:02:28 fedora kernel: PM: suspend entry (s2idle)
Sep 26 05:28:19 fedora kernel: PM: suspend devices took 0.287 seconds
Sep 26 05:28:20 fedora kernel: PM: suspend exit
Sep 26 07:47:25 fedora kernel: PM: suspend entry (s2idle)
Sep 26 09:47:26 fedora kernel: PM: suspend devices took 0.154 seconds
Sep 26 09:47:26 fedora kernel: PM: suspend exit
Sep 26 09:47:36 fedora kernel: PM: suspend entry (s2idle)
Sep 26 11:55:32 fedora kernel: PM: suspend devices took 0.106 seconds
Sep 26 11:55:32 fedora kernel: PM: suspend exit

6

The RTC is one minute ahead of UTC
Im pretty sure Fedora uses UTC for hardware RTC

sudo timedatectl set-local-rtc 0
7

It depends. Anaconda will set the system up to use local time RTC if it detects a Windows installation. (Though the detection isn’t always reliable, see this and following posts.)

8

Gaute@fedora:~$ sudo timedatectl set-local-rtc 0
[sudo] password for Gaute:
Gaute@fedora:~$ timedatectl
Local time: Sat 2026-09-26 12:22:16 CEST
Universal time: Sat 2026-09-26 10:22:16 UTC
RTC time: Sat 2026-09-26 10:22:18
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: no
NTP service: active
RTC in local TZ: no

“Local time: Sat 2026-09-26 12:22:16 CEST” <— This is just wrong local time is 10:25 rn

9

I think RTC configuration is correct now, but Local and Universal time got the difference of two hours i.e system clock is almost 2 hours ahead.
RTC shows difference of only seconds from UTC which is fine i guess.
Check why NTP isnt synchronizing

Can you try this? (from my initial response)

sudo timedatectl set-ntp true
10

Gaute@fedora:~$ sudo timedatectl set-ntp true
Gaute@fedora:~$ timedatectl
Local time: Sat 2026-09-26 12:38:55 CEST
Universal time: Sat 2026-09-26 10:38:55 UTC
RTC time: Sat 2026-09-26 10:40:27
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: no
NTP service: active
RTC in local TZ: no

11

I guess manually correcting it should be a way now.

sudo timedatectl set-time '2026-09-26 10:40:00'

or whatever time its in your timezone right now.

12

Gaute@fedora:~$ sudo timedatectl set-time ‘2026-09-26 10:45:00’
[sudo] password for Gaute:
Failed to set time: Automatic time synchronization is enabled

13

sudo timedatectl set-ntp false
sudo timedatectl set-time ‘2026-09-26 10:45:00’ [ with ur time ]
sudo timedatectl set-ntp true

14

Gaute@fedora:~$ sudo timedatectl set-time ‘2026-09-26 10:48:00’
Too many arguments.

I did the set-ntp false thing first

15

wait, my bad lol for some reason the qoute is a bit diffrent

sudo timedatectl set-ntp false
sudo timedatectl set-time '2026-09-26 10:45:00'
sudo timedatectl set-ntp true

try now

16

Gaute@fedora:~$ sudo timedatectl set-time ‘2026-09-26 10:52:00’
Gaute@fedora:~$ sudo timedatectl set-ntp true
Gaute@fedora:~$ timedatectl
Local time: Sat 2026-09-26 10:57:04 CEST
Universal time: Sat 2026-09-26 08:57:04 UTC
RTC time: Sat 2026-09-26 10:57:04
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

And the Audio works again! :raising_hands:

17

Congratulations.
Dont change the configuration and test it for a few more sleep wakeup cycle

18

Thank you for your help!

Let’s hope the issue doesn’t return when I close the lid again in the future

19

The 2-hour jump is most likely the “RTC in local TZ: yes” setting left over from when Windows was installed. Run sudo timedatectl set-local-rtc 0, and timedatectl should then show “RTC in local TZ: no”. Does the audio still get choppy after the next lid close?

Drafted with AI.

20

They already did this and showed the output in post 5.

Perhaps your AI agent isn’t taking replies into account?