Groups | Search | Server Info | Keyboard shortcuts | Login | Register

Groups > comp.os.linux.hardware > #3551

Re: Audio weirdness

Show all headers | View raw

David W. Hodgins wrote:
> On Fri, 17 Jun 2022 06:27:36 -0400, Andrew <Doug@hyperspace.vogon.gov> 
> wrote:
>> Well, not what I was expecting at all.
>> 1. "lsmod" after a boot showed various modules, including snd-hda-intel.
>> 2. "lsmod" while music was (not) being played showed additional modules.
>> 3. "lsmod" once the workaround (cable) had been applied and with music
>> playing, the modules loaded were identical to case 2.
>>
>> I have tried two different "content" sources - Firefox and Dragon
>> Player.  The behaviour is identical.
> 
> I'd try (as root) in a termainl, start "udevadm monitor", unplug/replug the
> speaker cable, ctrl+c to kill the udevadm monitor.
> 
> Then see if there are any udev rules being triggered by that. If there are
> you may be able to find a way to force them when you boot.
> 
> I suggest doing as little as possible while udevadm is running to keep the
> noise in it's output to a minimum. Just the unplug/replug. It produces 
> output
> for every mouse movement and keyboard press and release.
> 
> Regards, Dave Hodgins
> 
> 

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.

Back to comp.os.linux.hardware | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Audio weirdness Andrew <Doug@hyperspace.vogon.gov> - 2022-06-15 12:24 +0200
  Re: Audio weirdness "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-06-15 16:11 -0400
    Re: Audio weirdness Andrew <Doug@hyperspace.vogon.gov> - 2022-06-17 12:08 +0200
      Re: Audio weirdness Andrew <Doug@hyperspace.vogon.gov> - 2022-06-17 12:27 +0200
        Re: Audio weirdness "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-06-17 14:34 -0400
          Re: Audio weirdness Andrew <Doug@hyperspace.vogon.gov> - 2022-06-18 08:12 +0200
            Re: Audio weirdness "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2022-06-18 10:04 -0400
              Re: Audio weirdness Andrew <Doug@hyperspace.vogon.gov> - 2022-06-19 19:37 +0200
              Re: Audio weirdness Andrew <Doug@hyperspace.vogon.gov> - 2022-07-13 15:47 +0200
              Re: Audio weirdness - SOLVED Andrew <Doug@hyperspace.vogon.gov> - 2022-08-05 13:12 +0200

csiph-web