Bug 523560
| Summary: | bluez not really compatible with session switching | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Corch <ghbmail> |
| Component: | bluez | Assignee: | Bastien Nocera <bnocera> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 11 | CC: | bnocera, dwmw2, lkundrak, lpoetter, marcel, plautrba, wtogami |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-06-28 14:40:25 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
Corch
2009-09-16 00:15:47 UTC
Your PulseAudio is running as the GDM user, which is why it's causing problems. Do "killall pulseaudio", and run pulseaudio within the session, and it should be working. *** This bug has been marked as a duplicate of bug 513579 *** The big problem is that there is not really a scheme how ownership of a bluez service can be safely handed over from one session to the next. For alsa device nodes we can simply set ACLs and use inotify so that we know when the old owner released the device and be sure he cannot access the device anymore. The D-Bus services bluez offers don't really have anything comparable. bluetoothd can receive messages from the current console user. You can use ConsoleKit to see whether you're allowed to contact bluetoothd. It's the exact same bug as the one I marked it as a dupe of. (In reply to comment #3) > bluetoothd can receive messages from the current console user. You can use > ConsoleKit to see whether you're allowed to contact bluetoothd. This is racy because we would get the ckit msgs asynchronously, so that we might send a msg to bluez and only then get the ck session switch msg, even if the session switch happened before we sent the bluez msg. That way you'd still lose a msgs and get log out output warning about that. More importantly however this is not sufficient. bluez must actively reset connections that were created by a session A when we switch to a session B. Without this the connection would still be configured for use with session A and be blocked for session B. We need to have some logic in BlueZ that follows polkit authorizations or so and shuts downs access to devices accordingly and also informs the user about this, when it does this. > It's the exact > same bug as the one I marked it as a dupe of. No, that bug was a series of different things. This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |