I’m not sure what information will be helpful, but when I unplug my headset my volume becomes stuck at that level. I can’t raise or lower volume for the speaker or microphone afterward. Also, plugging the set back in doesn’t give me access to volume control - it remains stuck. This is true whether using the volume buttons, the slider from the top bar widget, or opening the settings and trying the sliders there.
Currently, my only solution is a full reboot. If there’s no good solution, is it possible just to reset whatever is getting locked up with sound control?
Alternative would be to check with an Live iso if you have same problems with an older kernel. If not you could downgrade the kernel.
In the next fiew days will be released F34 with improvements on sound management. Probably would be a good idea to check this live iso too.
There is a command where you can run to check what happens when you connect disconnect an USB device, to see what happens. Unfortunatly i don’t remember it. I saw it in a other topic while someone debugged an USB device problem.
Thanks for the advice. It looks like I’m up-to-date with my firmware. I should have mentioned, this is through my headphone jack, not USB. Is there still a way to debug?
Edit: nevermind. I rushed to judgment. It is locked again.
Hey, thanks for your input! I had two Fedora 33 and one Fedora 32 option in the boot menu. I chose the second Fedora 33 and so far it seems to be working. I’ve unplugged and replugged a few times and can’t get it to lock the volume.
Is this a bug to report to a different linux admin team? Thanks again!
This is something I have started to notice myself on later updates to F33 and now seeing in F34. It seems kind of curt, but opening a bug at this point is probably the best route and being patient as I feel this release is going to have a lot of bugs to work out initially.
Having two fedora 33 and one fedora 32 options in the boot menu and selecting the second does not tell us anything. I have 5 different kernel versions available for boot from the menu, so if I told you I booted from the 3rd choice how can you infer which kernel I actually used…
Each entry should identify the kernel related and this may be kernel or sound driver related so the needed info would include versions of all related software. Gnome, kernel, pulse, jack, alsa, sound app being used, etc. would all be helpful, and should be provided if you submit a bug report.
If the bug references similar problems with the same hardware/software then adding additional information is the correct approach. The developers need that info.