Closed Bug 790106 Opened 12 years ago Closed 9 years ago

Desktop B2G/FF crash due to misrouted UPower messages from WebBluetooth

Categories

(Core :: DOM: Device Interfaces, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID
blocking-basecamp -

People

(Reporter: qdot, Assigned: qdot)

References

Details

(Keywords: crash, Whiteboard: [b2g-crash], [b2g-desktop-builds])

Attachments

(1 file)

UPower uses dbus on desktop, but other comm services on the phone. Using bluetooth on the desktop will crash in debug after a while due to a failed main thread assert in upower handling. This is due to the fact that we pass on messages that aren't handled by bluetooth, and they're handled in the dbus signal catching thread, not the main thread.
This probably doesn't need to block basecamp since we aren't actively using Desktop B2G for much?
(In reply to Kyle Machulis [:kmachulis] [:qdot] from comment #1)
> This probably doesn't need to block basecamp since we aren't actively using
> Desktop B2G for much?

Dunno, I think we expect developers to use it (*I* certainly do :) ).
blocking-basecamp: --- → ?
While this seems very annoying, we can't block on desktop-only issues.
blocking-basecamp: ? → -
Blocks: webbluetooth
No longer blocks: b2g-bluetooth
Summary: [b2g-bluetooth] Desktop B2G crash due to misrouted UPower messages → Desktop B2G/FF crash due to misrouted UPower messages from WebBluetooth
Keywords: crash
Whiteboard: [b2g-crash], [b2g-desktop-builds]
This is now a problem again now that we're trying to run bluetooth tests on b2g desktop. bent has been running into it for a couple of days.
I can't say for sure whether or not it would be approved, but an uplift could be considered for a patch here.
I think once we get C++ tests in (which bent at least has started), we'll have better grounds for uplift.
Fun fact and reason we haven't seen it in a while: This only happens on laptops running linux (either for real or in a VM). Desktops don't do battery queries. :)
This is a quick fix. Not really something I expect to land as it means either bluetooth or battery works, but not both.
Bluetooth hasn't worked on desktop in years. RIP.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: