Groups | Search | Server Info | Login | Register
Groups > comp.os.linux.hardware > #3563
| From | Andrew <Doug@hyperspace.vogon.gov> |
|---|---|
| Newsgroups | comp.os.linux.hardware |
| Subject | Re: Audio weirdness |
| Date | 2022-06-19 19:37 +0200 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <t8nms9$1lrt$1@gioia.aioe.org> (permalink) |
| References | (2 earlier) <t8hjqc$t74$1@gioia.aioe.org> <t8hkuo$1bn2$1@gioia.aioe.org> <op.1nw661vga3w0dxdave@hodgins.homeip.net> <t8jqd0$2b5$1@gioia.aioe.org> <op.1nypdicxa3w0dxdave@hodgins.homeip.net> |
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 This is going to have to wait - I'm going to be away for a week or so, then I'll have time for another go at the problem. Thanks -- This mail has been tested by https://RKIvirus.com/ and has been found to contain Covid-19. Disinfect after reading.
Back to comp.os.linux.hardware | Previous | Next — Previous in thread | Next in thread | Find similar
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