Opened 14 years ago
Last modified 10 years ago
#1677 reopened defect
Speaker device not updated on external state changes
| Reported by: | sascha_silbe | Owned by: | sascha_silbe |
|---|---|---|---|
| Priority: | Low | Milestone: | Unspecified |
| Component: | Sugar | Version: | Git as of bugdate |
| Severity: | Unspecified | Keywords: | |
| Cc: | quozl | Distribution/OS: | Unspecified |
| Bug Status: | New |
Description
If the mixer state is set externally, e.g. via olpc-kbdshim, the Speaker device in the frame isn't updated.
I don't know the ALSA API at all, but given that alsamixer responds immediately to external changes I guess there's a way to get notified.
Change History (8)
comment:1 Changed 14 years ago by sascha_silbe
- Owner changed from tomeu to sascha_silbe
- Priority changed from Unspecified by Maintainer to Normal
- Status changed from new to accepted
comment:2 Changed 11 years ago by quozl
comment:3 Changed 10 years ago by quozl
- Cc quozl added
comment:4 Changed 10 years ago by dnarvaez
- Resolution set to wontfix
- Status changed from accepted to closed
I think this is not important enough to be tracked. Feel free to send patches of course.
comment:5 Changed 10 years ago by quozl
- Resolution wontfix deleted
- Status changed from closed to reopened
I think this is important enough to be tracked. This is an interoperability problem between Sugar and other system components on Linux, not just on OLPC builds. The point of interface is the ALSA mixer API. Sugar is not using the API in the manner that all other programs do.
The user impact is significant; Sugar does not show valid data in the frame. This degrades trust in the frame as a UI element.
comment:6 Changed 10 years ago by dnarvaez
- Bug Status changed from New to Unconfirmed
comment:7 Changed 10 years ago by dnarvaez
- Bug Status changed from Unconfirmed to New
comment:8 Changed 10 years ago by dnarvaez
- Priority changed from Normal to Low
http://dev.laptop.org/ticket/9913 has some ideas on how to be notified of changes.