Bug 195114

Summary: When playing sets volume level to max, then to specified level
Product: [Applications] juk Reporter: Jordan Manolov <water.archon>
Component: generalAssignee: Scott Wheeler <wheeler>
Status: REPORTED ---    
Severity: normal CC: kde, mpyne
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Jordan Manolov 2009-06-03 17:39:14 UTC 
Version:           3.2.2 (using 4.2.2 (KDE 4.2.2), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.26-2-686

The case is rather simple: given several songs to play one after another, when juk hasn't been active for some time. first track starts with the highest volume level, after which the application sets that level to the specified via the widget on the toolbar. This happens also when random play is enables, every second or third begins with high volume level, after a second sets it to desired.

How to reproduce: load several (at least 6) songs, do not play for an hour. Set the volume level via alsamixer to highest, the application output volume level no more than 30-50%. Enable random play and listen. 

Expected behavior: play each song from the beginning to the end with specified volume level.
Comment 1 Andrew Crouthamel 2018-11-02 23:02:42 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-16 05:38:01 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?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Michael 2022-04-05 03:36:51 UTC 
This bug from 2009 seems to be manifesting now as this bug, where the volume is set to -2million% ... https://bugs.kde.org/show_bug.cgi?id=452191