Thanks!
It appears PulseAudio is repeatedly failing to start and timing out
because rtkit-daemon.service is failing to start. And rtkit-
daemon.service is failing to start for some reason related to "Bad
address" errors occurring on lots of mount operations.
As a workaround, you can tell
Sorry, wrong pastebin link.
Here's the correct one: https://pastebin.com/NL6UCN49
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1798712
Title:
[System76 Oryx Pro] No
Running pulseaudio with `-` outputs this:
https://pastebin.com/2fbrzwzb
Here's a small explanation of pauses:
[line 1] pulseaudio -
[some output]
[line 5] Failed to acquire high-priority scheduling: Input/output errorI:
[pulseaudio] core-util.c: Failed to acquire high-priority
After restarting my computer, and attempting to start pulseaudio, I
noticed that it takes exactly 10 minutes to start. Here's the updated
current boot log.
** Attachment added: "currentboot.log"
Thanks but that log is quite cluttered, covering the past 2 days.
Can you please at some point reboot the machine, wait until audio starts
working and then collect a fresh log? That way the log will be much
smaller and it will be easier to focus on the audio problem.
--
You received this bug
Hey Daniel, I attached the log that you requested. "it" did mean
pulseaudio, as your assumption guessed. As a heads up, I disabled
pulseaudio from automatically starting, so that I wouldn't be trying to
have multiple pulseaudio sessions open at once.
** Attachment added: "currentboot.log"
Unfortunately that did not update this bug as I hoped, but your link in
comment #1 will do.
Can you please elaborate on what "it" starting in comment #2 means? Are
you talking about it=pulseaudio? Can you please attach a system log from
after "it" has started?
journalctl -b > currentboot.log
7 matches
Mail list logo
