Bug 1575301 - pulseaudio cpu usage
Summary: pulseaudio cpu usage
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pulseaudio
Version: 28
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-05 20:18 UTC by Sammy
Modified: 2019-05-28 23:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:02:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Sammy 2018-05-05 20:18:47 UTC
I just updated to Fedora 28 and noticed that pulseaudio is using constantly 4%+ cpu while no audio is in use.

I am using KDE plasma and this is Lenovo Thinkpad T450s.

One observation is that if I kill pulseaudio it is automatically restarted but it no longer has the cpu usage. It sounds like it is not completing something during the initial start.

Comment 1 Sammy 2018-05-10 21:59:50 UTC
This has been reported elsewhere:

https://bbs.archlinux.org/viewtopic.php?id=222857

Following that removing speech-dispatcher solves the problem.
But of course this is not the real solution.

Comment 2 Sammy 2018-05-10 22:47:17 UTC
Also, the problem is only happening on my laptop Lenovo T450s but not on any of my desktop machines.

Comment 3 Edouard Bourguignon 2018-10-27 09:02:34 UTC
I do

killall speech-dispatcher

And it seems fine after that.

I'm still having this issue on Fedora 29. Speech-dispatcher is running for no reasons, using cpu.

Comment 4 Ben Cotton 2019-05-02 20:34:04 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2019-05-28 23:02:16 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.