Bug 360000 - KMail grabs default PCM device on notification
Summary: KMail grabs default PCM device on notification
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: misc (show other bugs)
Version: 5.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-02 15:14 UTC by Patrick Auernig
Modified: 2022-11-18 05:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Auernig 2016-03-02 15:14:53 UTC
The soundcard of my PC stopped working after a while, so I started monitoring the usage of PCM devices in my system.

What I found is that KMail grabs the default PCM device of the system when a notification dialog pops up (in my case it was the sieve script upload confirmation dialog).

If the device is already in use (by pulseaudio), audio keeps working as it should.

It seems that some notifications bypass pulseaudio and use ALSA directly, but do not release the device afterwards.

Closing the application releases the device again, but its really annoying.

Reproducible: Always

Steps to Reproduce:
1. Open the sieve script editor
2. Klick OK to close the editor
3. Default PCM device gets used by KMail

Actual Results:  
No audio over default soundcard

Expected Results:  
Sound keeps working

Arch Linux package version: 15.12.2-1
Kernel: 4.4.1-2-ARCH x86_64

output of fuser -av
                     USER        PID ACCESS COMMAND
/dev/snd/pcmC0D0p:   valeth    F...m kmail
Comment 1 Justin Zobel 2022-10-19 22:10:44 UTC
Thank you for reporting this bug 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 "CONFIRMED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-03 05:07:31 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 3 Bug Janitor Service 2022-11-18 05:17:47 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!