Product: Fedora
Version: rawhide
Component: distribution
Ben Cotton <bcotton(a)redhat.com> has denied Adam Williamson
<awilliam(a)redhat.com>'s request for fedora_prioritized_bug:
Bug 1907030: "dnf update" runs out of memory on swapless machines with 1G or
less of RAM
https://bugzilla.redhat.com/show_bug.cgi?id=1907030
--- Comment #30 from Ben Cotton <bcotton(a)redhat.com> ---
In today's Prioritized Bugs meeting, we agreed to reject this as a Prioritized
Bug as it requires large-scope changes to the distribution. mattdm will
coordinate or delegate an effort to develop an F38 Change proposal to address
the issues:
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-08-24/fedora_priori…
d_bugs_and_issues.2022-08-24-14.00.log.html#l-93
Product: Fedora
Version: 36
Component: grub2
Ben Cotton <bcotton(a)redhat.com> has canceled Kamil Páral <kparal(a)redhat.com>'s
request for fedora_prioritized_bug:
Bug 2115202: update 2.06-45 breaks windows boot manager
https://bugzilla.redhat.com/show_bug.cgi?id=2115202
--- Comment #40 from Ben Cotton <bcotton(a)redhat.com> ---
Removing the Prioritized Bugs flag as this is an accepted F37 Final blocker:
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-08-24/fedora_priori…
d_bugs_and_issues.2022-08-24-14.00.log.html#l-32
Product: Fedora
Version: rawhide
Component: dnf
Adam Williamson <awilliam(a)redhat.com> has asked for fedora_prioritized_bug:
Bug 1907030: "dnf update" runs out of memory on swapless 0.5 GiB RAM machine
https://bugzilla.redhat.com/show_bug.cgi?id=1907030
--- Comment #22 from Adam Williamson <awilliam(a)redhat.com> ---
On further consideration, as people are hitting this on F36, it seems odd to me
to suggest blocking F37 on it. It's not an F37 bug, and blocking the F37
release on it wouldn't really help anyone, because if we don't ship F37 the
only alternative we're offering is "use F36 instead", and the bug affects F36.
So, I'm gonna nominate this as a prioritized bug instead, and suggest at the
next blocker review that we drop it as a proposed blocker. It certainly seems
like potentially a major problem that we can't do dnf operations with 1G or
less of RAM, but it doesn't feel like the release blocker process is the way to
handle it.
Product: Fedora
Version: 36
Component: kernel
Kamil Páral <kparal(a)redhat.com> has asked for fedora_prioritized_bug:
Bug 2100761: Bluetooth mouse doesn't reconnect after suspend/resume with kernel
5.18.5. With 5.17.14 it works fine.
https://bugzilla.redhat.com/show_bug.cgi?id=2100761
--- Comment #30 from Kamil Páral <kparal(a)redhat.com> ---
I tested with kernel-5.19.0-300.fc37.x86_64 and I don't see any improvement. My
bluetooth mouse still doesn't reconnect after resume, unless I open
gnome-control-center->Bluetooth. Which means the blocker proposal is relevant.
Also proposing as a prioritized bug, this is a highly important issue and sadly
receives no attention from the kernel team.
Product: Fedora
Version: 36
Component: grub2
Kamil Páral <kparal(a)redhat.com> has asked for fedora_prioritized_bug:
Bug 2115202: update 2.06-45 breaks windows boot manager
https://bugzilla.redhat.com/show_bug.cgi?id=2115202
--- Comment #23 from Kamil Páral <kparal(a)redhat.com> ---
Proposing as a Prioritized bug and a CommonBug.
Product: Fedora
Version: 36
Component: kde-partitionmanager
Ben Cotton <bcotton(a)redhat.com> has denied bdp <inbox2(a)mymetronet.net>'s
request for fedora_prioritized_bug:
Bug 2090536: [abrt] kde-partitionmanager: std::__atomic_base<int>::load():
partitionmanager killed by SIGSEGV
https://bugzilla.redhat.com/show_bug.cgi?id=2090536
--- Comment #14 from Ben Cotton <bcotton(a)redhat.com> ---
Rejecting as a Prioritized Bug while the bug is marked as private.