spheenik Posted March 31, 2019 Report Share Posted March 31, 2019 Hi, since version 6 (I guess), enpass plays a little sound when logging in. My audio server is Pulse Audio, and playing the sound creates an entry in "pavucontrol" (Playback), which is always "QtPulseAudio:XXXX: QtPulseSample-XXXX-YYYYYYYYY" where XXXX is the PID of the enpass process, and YYYYYYYYYY some random number. Problem is, after the sound has played, these stay there, and pile up after logging in several times. I suspect the application does not close the stream properly when it is finished, that's why it stays there. I'd appreciate if this could be fixed, and the entry removed after playing. Thank you! 1 Link to comment Share on other sites More sharing options...
hackedhead Posted April 3, 2019 Report Share Posted April 3, 2019 I'm also experiencing this. It appears that disabling "Play an unlock sound" in the "Customize" control panel does effectively prevent this from occurring, but it of course means that no sound is played. I'm going to suffer the mild annoyance of not having an unlock sound to solve the major annoyance of having approximately a dozen orphaned sound sources in `pavucontrol` because their presence makes it really annoying to manage the sound controls I actually need for other apps. Link to comment Share on other sites More sharing options...
gdiffey@gmail.com Posted November 27, 2020 Report Share Posted November 27, 2020 I don't think you're even aware of this but on longlived instances I end up closing enpass and relaunching it after a few days because these little snick sounds end up making it so I can't manage sound properly.. i think you're using this api? https://doc.qt.io/qt-5/qsound.html I think you need to destroy the qsound object after querying 'isfinished' or change to using qsoundeffect Link to comment Share on other sites More sharing options...
Garima Singh Posted November 30, 2020 Report Share Posted November 30, 2020 Hey @gdiffey@gmail.com Welcome to the forum! We really appreciate you your exploring the app and sharing this. The same has been noted and shared with the team members. Thanks! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now