Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=1874082 Information from BlockerBugs App: <img alt="1874082" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/1874082" />
Commented but haven't voted yet: sumantrom
The votes have been last counted at 2020-10-19 15:44 UTC and the last processed comment was #comment-696874
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review
I'm not sure how I feel about this. It's not relevant to lives, so it could be fixed in an update. But should we ship without it working? I feel like sleep is unsupported enough that we can say "meh".
FinalFE +1 in any case because if a fix lands in the next few days, we might as well get it in. I'll continue to decide how I feel about it being a blocker or hope it gets fixed before I have to commit one way or another.
I thought only hibernation was considered unsupported. Suspend to RAM seems quite essential for any laptop user (it's true that those have at least an always available touchpad). It's also officially supported by GNOME, there's a button for it in the user menu. I think the argument was "we can't block on a broken suspend for particular PC models, because we simply don't have enough manpower to fix it all". But I don't think we consider suspend unsupported in general.
I'd very appreciate if more people could test this and post their results to Bugzilla, thanks. Perhaps this only affects some mice.
On the fence about this one till we have more data. Will send out an email.
D'oh, I conflated sleep and hibernation. But I'm still unsure how to feel about this one.
I do not have any wireless mice, so I cannot test for myself, but I consider this a serious problem. I agree that restarting bluetooth anytime the computer goes asleep is tedious. I believe that the system could restart it automatically when waking up.
FinalBlocker +1
I tried to use two different logitech wireless mouse that I had, I didnt face any challenge. Logitech M185 Logitech M221
Let's keep the technical discussion in Bugzilla, please :-) (None of those mice seem to support Bluetooth, according to the web specs, they use a proprietary USB dongle connection).
From the feedback on my email this seems like it's not a systemic issue, i.e. it's not affecting all bluetooth mice / controllers. Given that I think I'm:
FInalBlocker -1 FinalFE +1
I don't think we can really plausibly block a release on "some bluetooth mouse/controller combinations don't reconnect after sleep", it just doesn't seem bad enough.
FinalBlocker -1 FinalFE +1
FinalBlocker -1
For the reasons Adam said.
AGREED AcceptedFinalFE
The following votes have been closed:
@lruzicka , @kparal - where are you guys on blocker status now given the feedback we've got?
Based on the feedback on the test@ list, this seems to affect only some bluetooth devices and only on some bluetooth controllers. Also, I think bluetooth mice are relatively uncommon: mice using the logitech protocol seem more frequent, so this doesn't shouldn't affect too many people. And while this creates an inconvenience, fix through an update is fine.
It's inconvenient, but only affects selected hardware.
OK, vote seems clear enough now.
AGREED RejectedFinalBlocker
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F33 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.