Bug 456887
| Summary: | Mixer plugin does not correctly remember alternative device setting | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Ekstrand <michael> |
| Component: | xfce4-mixer | Assignee: | Kevin Fenzi <kevin> |
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 9 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-10-10 18:10:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Michael Ekstrand
2008-07-28 13:36:37 UTC
Is there any errors or other output of interest in ~/.xsession-errors? When you set the device, does the ~/.config/xfce4/mcs_settings/sound.xml file update correctly? Does that file change on login? ~/.xsession-errors does not contain anything that seems pertinent. ~/.config/xfce4/mcs_settings/sound.xml indicates that it is supposed to use the selected alternate device. After a fresh login, sound.xml indicates device #0 (HDA Intel), but the applet is connected to the PulseAudio device. I have also now confirmed that it is fully connected to and manipulating the PulseAudio volume, not merely displaying it once while being actually backed by the correct device. This appears to be upstream bug 3283: http://bugzilla.xfce.org/show_bug.cgi?id=3283 Would you like to add yourself up there and provide more info? Or would you like me to do so? I would suggest we close this bug and let upstream work on it, but if you prefer we can leave it open as a reminder to pull in any fix they have. Thoughts? I've added a link back to this bug report in the Xfce report. As far as closing it or not -- I don't really have an opinion. Whatever you think would best enable the Fedora XFCE maintainers to deal with the situation. Well, I have added myself to the upstream bug, so I will know if anything happens there. I'm inclined to close this UPSTREAM. Feel free to re-open or file a new bug if you disagree. ;) Thanks for the report! |