Bug 340484 - Testing audio capture device gets stuck if settings are closed without stopping it
Summary: Testing audio capture device gets stuck if settings are closed without stoppi...
Status: RESOLVED WORKSFORME
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: settings (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: 4.8
Assignee: Harald Sitter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-30 00:14 UTC by anonymouse2048
Modified: 2023-02-11 03:52 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description anonymouse2048 2014-10-30 00:14:32 UTC
If I start testing a capture device (causing playthrough) then close the settings panel without clicking the Test button again to stop it, it gets stuck permanently on.

Reproducible: Didn't try

Steps to Reproduce:
1. Open "Audio and Video settings" control module
2. Select any subcategory of "Audio recording"
3. Select a capture device
4. Click test
5. Close control module
6. Make some noises into the microphone

Actual Results:  
The sounds are fed through to the output device.

Expected Results:  
The sounds should stop being played through after the control module is closed.

I would try to reproduce the error, but I haven't been able to deactivate the playthrough yet. It persists across login sessions and reboots.
Comment 1 Andrew Crouthamel 2018-11-12 02:43:59 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-21 04:43:44 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-12 01:57:59 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-27 05:08:23 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-02-11 03:52:50 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!