Bug 1472537

Summary:	pulseaudio and system can be easily overwhelmed with audible bell
Product:	[Fedora] Fedora	Reporter:	Doug Maxey <bz>
Component:	pulseaudio	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	26	CC:	lpoetter, rdieter, wtaymans
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-29 12:29:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Doug Maxey 2017-07-19 01:51:59 UTC

Description of problem:
After a fresh install of f26 on a desktop system, I find it too easy to end up needing to reboot to be able to type into any kind of editor or even the command line.

Version-Release number of selected component (if applicable):
pulseaudio-10.0-4.fc26.x86_64
gnome-software-3.24.3-1.fc26.x86_64
xorg-x11-server-Xorg-1.19.3-4.fc26.x86_64

How reproducible:
100%

Steps to Reproduce:
1. reboot and login as regular user.
2. start the 'less' command on a small file (empty ok)
3. attempt scroll down with the mouse, which triggers a sequence of bells.

Actual results:

Doing the above seems to precipitate a very glitchy keyboard input
when the sound stops working and all audio related icons disappear.

The system immediately becomes very sluggish and causes typing
(or pasting) to lose characters.

Expected results:

pa has this same overload issues on f25.  But in the older releases,
when it failed, the user could restart the daemon and reload modules
as necessary.

With the current scheme, unless the user is admin, nothing can be
done.  Even with sudo access, I have yet to determine how to recover
without a reboot.

Comment 1 Fedora End Of Life 2018-05-03 08:09:27 UTC

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 2 Fedora End Of Life 2018-05-29 12:29:08 UTC

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.