David W. Hodgins wrote:
> On Sat, 18 Jun 2022 02:12:48 -0400, Andrew <Doug@hyperspace.vogon.gov>
> wrote:
>> No events, none at all.  All I saw was
>>
>> monitor will print the received events for:
>> UDEV - the event which udev sends out after rule processing
>> KERNEL - the kernel uevent
>>
>> ^C
>>
>> My guess is that Pulseaudio is misbehaving, but it could just as easily
>> be the victim here.
>> Three messages I saw in the log after the upgrade were:
>>
>> dbus-daemon[839]: [system] Failed to activate service 'org.bluez': timed
>> out (service_start_timeout=25000ms)
>>
>> kded5[9493]: kf.bluezqt: PendingCall Error: "Failed to activate service
>> 'org.bluez': timed out (service_start_timeout=25000ms)"
>>
>> pulseaudio[10257]: GetManagedObjects() failed:
>> org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
>> causes include: the remote application did not send a reply, the message
>> bus security policy blocked the reply, the reply timeout expired, or the
>> network connection was broken.
>>
>> I saw nothing of the kind in a log from before the upgrade.
>
> If it's a hard wired speaker, not a bluetooth connection, then bluez has
> nothing to do with the speaker.
>
> If you're not using bluetooth for any audio output, see
> https://forum.manjaro.org/t/journalctl-pulseaudio-error-after-latest-update/38771/5
>
> to stop it from looking for bluetooth headphones or earplugs.
>
> I doubt that will change anything with the wired speakers, but it might
> if it's
> the delay caused by searching for non-existent bluetooth speakers that's
> causing
> the problem.
>
> Regards, Dave Hodgins

It was a setting in KDE and I don't know if the solution makes any sense
outside the OpenSUSE environment.

System Settings -> Hardware -> Audio -> Profile was set to "Analog
Stereo Duplex", changing it to "Analog Stereo Output" fixed the problem.

It had worked with "Analog Stereo Duplex" under the previous level.