Public bug reported:
Hello, I like to leave pavucontrol open all the time so I can have easy
access to the per-application volume slider. I need to turn up firefox
above 100% often, because some coworkers have quiet microphones in
Google Meet, and there's no way in Google Meet to change individual
volumes.
But pavucontrol causes high CPU use in both pavucontrol and pulseaudio,
both are listed around 10% processor use in top, and Xorg around 5%.
The funny thing is that pavucontrol was on a non-visible virtual desktop
(i3wm). It's a wild guess but it feels like it's constantly rendering
the interface with frequent calls to pulseaudio to learn the current
state -- even though it's not visible, hasn't been visible for a long
time, and won't be visible for a long time.
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pavucontrol 4.0-1build1
ProcVersionSignature: Ubuntu 5.4.0-204.224-generic 5.4.284
Uname: Linux 5.4.0-204-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jan 14 15:54:29 2025
SourcePackage: pavucontrol
UpgradeStatus: Upgraded to focal on 2020-01-24 (1816 days ago)
** Affects: pavucontrol (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to pavucontrol in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/2094822
Title:
high processor use even when idle
Status in pavucontrol package in Ubuntu:
New
Bug description:
Hello, I like to leave pavucontrol open all the time so I can have
easy access to the per-application volume slider. I need to turn up
firefox above 100% often, because some coworkers have quiet
microphones in Google Meet, and there's no way in Google Meet to
change individual volumes.
But pavucontrol causes high CPU use in both pavucontrol and
pulseaudio, both are listed around 10% processor use in top, and Xorg
around 5%.
The funny thing is that pavucontrol was on a non-visible virtual
desktop (i3wm). It's a wild guess but it feels like it's constantly
rendering the interface with frequent calls to pulseaudio to learn the
current state -- even though it's not visible, hasn't been visible for
a long time, and won't be visible for a long time.
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pavucontrol 4.0-1build1
ProcVersionSignature: Ubuntu 5.4.0-204.224-generic 5.4.284
Uname: Linux 5.4.0-204-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jan 14 15:54:29 2025
SourcePackage: pavucontrol
UpgradeStatus: Upgraded to focal on 2020-01-24 (1816 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/2094822/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntustudio-bugs
Post to : ubuntustudio-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntustudio-bugs
More help : https://help.launchpad.net/ListHelp
