triage January 2022

triage@lists.fedoraproject.org

3 participants
18 discussions

needinfo canceled: [Bug 619461] [abrt] crash in qbittorrent-1:2.2.8-2.fc12: message: Process /usr/bin/qbittorrent was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla 06 May '25

06 May '25

Product: Fedora Version: 12 Component: qbittorrent Karel Klíč <kklic(a)redhat.com> has canceled Bug Zapper <fedora-triage-list(a)redhat.com>'s request for needinfo: Bug 619461: [abrt] crash in qbittorrent-1:2.2.8-2.fc12: message: Process /usr/bin/qbittorrent was killed by signal 11 (SIGSEGV) https://bugzilla.redhat.com/show_bug.cgi?id=619461

2 1

needinfo canceled: [Bug 633653] [abrt] lekhonee-gnome-0.9-1.fc12: wordpress_get_categories: Process /usr/bin/lekhonee-gnome was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla 06 May '25

06 May '25

Product: Fedora Version: 12 Component: lekhonee-gnome Karel Klíč <kklic(a)redhat.com> has canceled Bug Zapper <fedora-triage-list(a)redhat.com>'s request for needinfo: Bug 633653: [abrt] lekhonee-gnome-0.9-1.fc12: wordpress_get_categories: Process /usr/bin/lekhonee-gnome was killed by signal 11 (SIGSEGV) https://bugzilla.redhat.com/show_bug.cgi?id=633653

2 1

[Bug 253630] Clash of short-cut in search dialog
by Red Hat Bugzilla 02 May '25

02 May '25

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=253630 lexual <lex.lists(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|lex.lists(a)gmail.com | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

5 5

[Fedocal] Reminder meeting : Prioritized bugs and issues
by bcotton＠redhat.com 28 Feb '25

28 Feb '25

Dear all, You are kindly invited to the meeting: Prioritized bugs and issues on 2021-06-02 from 11:00:00 to 12:00:00 America/Indiana/Indianapolis At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Evaluation meeting More information available at: https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_a… Source: https://apps.fedoraproject.org/calendar/meeting/9964/

3 2

fedora_prioritized_bug granted: [Bug 1953675] Akonadi does not start due to DB failure
by bugzilla＠redhat.com 21 Jan '25

21 Jan '25

Product: Fedora Version: 34 Component: kf5-akonadi-server Ben Cotton <bcotton(a)redhat.com> has granted Ben Cotton <bcotton(a)redhat.com>'s request for fedora_prioritized_bug: Bug 1953675: Akonadi does not start due to DB failure https://bugzilla.redhat.com/show_bug.cgi?id=1953675 --- Comment #7 from Ben Cotton <bcotton(a)redhat.com> --- This was accepted as a Prioritized Bug in today's meeting.

2 1

fedora_prioritized_bug requested: [Bug 1964879] Boot fails, or slow and partly broken, with dracut 054+ and bluetooth keyboard (possibly other scenarios also)
by bugzilla＠redhat.com 21 Jan '25

21 Jan '25

Product: Fedora Version: 34 Component: dracut Adam Williamson <awilliam(a)redhat.com> has asked for fedora_prioritized_bug: Bug 1964879: Boot fails, or slow and partly broken, with dracut 054+ and bluetooth keyboard (possibly other scenarios also) https://bugzilla.redhat.com/show_bug.cgi?id=1964879 --- Comment #32 from Adam Williamson <awilliam(a)redhat.com> --- Flagging for CommonBugs and nominating as a prioritized bug. This seems like a pretty bad problem.

2 1

fedora_prioritized_bug requested: [Bug 1812596] repoquery suddenly missing results in --whatrequires on Fedora 32+ (seem to be related to virtual provides)
by bugzilla＠redhat.com 21 Jan '25

21 Jan '25

Product: Fedora Version: 32 Component: dnf Miro Hrončok <mhroncok(a)redhat.com> has asked for fedora_prioritized_bug: Bug 1812596: repoquery suddenly missing results in --whatrequires on Fedora 32+ (seem to be related to virtual provides) https://bugzilla.redhat.com/show_bug.cgi?id=1812596 --- Comment #5 from Miro Hrončok <mhroncok(a)redhat.com> --- Proposing this as a prioritized bug.

4 5

Picking a new time for the Prioritized Bugs meeting
by Ben Cotton 03 Feb '22

03 Feb '22

I have a personal conflict with the current meeting time for the Prioritized Bugs meeting, so I'm looking to reschedule. If you'd like to attend semi-regularly, please feel free to add your availability: https://whenisgood.net/c8iqggm/ I make no promises about when the meeting will be scheduled, but if there are times that are obviously favoriable, then I'll use that. If you're not sure what meeting I'm talking about, the Prioritized Bugs process is documented at: https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

2 2

[Fedocal] Reminder meeting : Prioritized bugs and issues
by bcotton＠redhat.com 25 Jan '22

25 Jan '22

Dear all, You are kindly invited to the meeting: Prioritized bugs and issues on 2022-01-26 from 11:00:00 to 12:00:00 America/Indiana/Indianapolis At fedora-meeting-1(a)irc.libera.chat The meeting will be about: Evaluation meeting More information available at: https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ Source: https://calendar.fedoraproject.org//meeting/10144/

2 1

fedora_prioritized_bug requested: [Bug 1967821] "fedpkg lint" dies with rpmlint-2.0.0: rpmlint: error: unrecognized arguments: -f
by bugzilla＠redhat.com 25 Jan '22

25 Jan '22

Product: Fedora Version: 35 Component: rpkg Gerald Cox <gbcox(a)bzb.us> has asked for fedora_prioritized_bug: Bug 1967821: "fedpkg lint" dies with rpmlint-2.0.0: rpmlint: error: unrecognized arguments: -f https://bugzilla.redhat.com/show_bug.cgi?id=1967821 --- Comment #13 from Gerald Cox <gbcox(a)bzb.us> --- Resetting prioritized flag. This needs to be reconsidered. I'm not aware of any work around other than not using the fedpkg lint command and issuing all the commands manually. If a fix is available it shouldn't take a month to get it pushed to testing and then to stable. This situation has been going on since June, 2021 and it breaks the package maintenance workflow. In the meantime, people get the error message and then just skip the lint check.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

triage January 2022