triage October 2023

triage@lists.fedoraproject.org

26 discussions

Official Launch of the Fedora BugZappers Triage Team
by Jack Aboutboul 21 Sep '26

21 Sep '26

Want to help out with the Fedora Project, but can't code a lick? Well fear not my dear friends. There are many ways you can help the cause and today I am pleased to announce a brand new way you can help contribute. Join the Fedora BugZappers! Who are the BugZappers? The BugZappers, (http://www.fedoraproject.org/wiki/BugZappers) are the official triage team of the Fedora Project. The main goal of the team is to triage, or do a first pass, of bugs in Bugzilla and ensure that a number of parameters are satisfactorily met. Basically what that means is that the BugZappers will go through bugs as they come in and try and make sure the bugs are valid (i.e. not a duplicate), sane and contain enough information to be escalated to developers. If you have ever reported a bug and wondered why it took so long to get fixed, well then BugZappers is the right project to join. Tell Me More! The BugZappers aim to be the primary line of defense for Fedora Quality Assurance (QA). The BugZappers will begin running Bug Day events, every alternating week, usually on Wednesdays. Bug Day events are when the team gets together to concentrate our focus on certain subsections of the project which need work. Triage should continue on though, and remember kids, "Every day should be a Bug Day!" So, if you are tired of hearing complaints about things not working, pieces being broken or just plain want to help Fedora be the best dang Fedora it can be, then join the BugZappers team and help the developers make the most of their coding time. It's fun, it's easy, you don't need much experience to start and we are willing to show you the path of the righteous, should you choose to accept this mission. What's in it for me? Glad you asked. First of all there is candy. OK, so there is no candy, but there is free stuff. The team is working on some giveaways and run contests during Bug Day events. You also get to work on triaging things that annoy you first, so your problems get fixed sooner; kernel problems anyone? Also, a wise man once said, much fame and fortune come to he who close many bugs. OK, it really wasn't a wise man buy you get the point. How Do I Join? Step 1: Sign up for the mailing list at: http://www.redhat.com/mailman/listinfo/fedora-triage-list Step 2: Join us on IRC We live in #fedora-bugs on Freenode Step 3: Read/Modify/Enhance the wiki Our wiki is located at http://www.fedoraproject.org/wiki/BugZappers . Additionally, we have more information available on the wiki at: http://www.fedoraproject.org/wiki/BugsReports and http://www.fedoraproject.org/wiki/Bugs . More content will be added as we get the project off the ground and moving. Also, be sure to look for our announcement of the first Bug Day event coming soon to an Inbox near you! Thanks, Jack

2 1

[Bug 229469] NFS fcntl locks being released locally but not on server
by Red Hat Bugzilla 11 Sep '26

11 Sep '26

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=229469 csb sysadmin <admin(a)structbio.vanderbilt.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |admin(a)structbio.vanderbilt. | |edu --- Comment #28 from csb sysadmin <admin(a)structbio.vanderbilt.edu> 2008-11-17 17:45:46 EDT --- I don't know if what we experienced has anything to do with thie problem, but we had a RHEL5 system running 2.6.18-92.1.1 and after a 138 day uptime, the NFS server stopped being able to complete fcntl64(..., F_GETLK, .. calls or fcntl64(255, F_GETFL) calls in strace. For users whose home directories were on this server, these users could not start firefox, thunderbird, openoffice, many KDE apps, etc and I couldn't run this test script no matter which of the 35+ other RHEL4 and RHEL5 NFS clients I tried : #!/bin/sh ( flock -x 200 uname -a >> allHosts.txt ) 200>> lockFile It would just hang. Eventually we had to reboot the NFS server, re-starting NFS didn't help, and I don't think there is anyway to re-start [lockd] since it's a kernel level process. -- 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 4

needinfo canceled: [Bug 597511] [abrt] crash in gnome-panel-2.30.0-1.fc13: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla 01 Sep '26

01 Sep '26

Product: Fedora Version: 13 Component: gnome-panel Truls Gulbrandsen <trulsg(a)broadpark.no> has canceled Bug Zapper <triage(a)lists.fedoraproject.org>'s request for needinfo: Bug 597511: [abrt] crash in gnome-panel-2.30.0-1.fc13: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV) https://bugzilla.redhat.com/show_bug.cgi?id=597511 ------- Additional Comments from Truls Gulbrandsen <trulsg(a)broadpark.no> My system is now upgraded to Fedora 15 and the bug is no longer relevant to me.

4 3

fedora_prioritized_bug requested: [Bug 2119987] Review Request: python-icapclient3 - Python3 module for creating ICAP clients
by bugzilla＠redhat.com 31 Aug '26

31 Aug '26

Product: Fedora Version: rawhide Component: Package Review Frank Crawford <frank(a)crawford.emu.id.au> has asked for fedora_prioritized_bug: Bug 2119987: Review Request: python-icapclient3 - Python3 module for creating ICAP clients https://bugzilla.redhat.com/show_bug.cgi?id=2119987

4 3

needinfo canceled: [Bug 613361] [abrt] crash in gnome-applets-1:2.30.0-1.fc13: bonobo_closure_invoke_va_list: Process /usr/libexec/multiload-applet-2 was killed by signal 11 (SIGSEGV)
by Red Hat Bugzilla 18 Aug '26

18 Aug '26

Product: Fedora Version: 13 Component: gnome-applets Bug Zapper <triage(a)lists.fedoraproject.org> has canceled Bug Zapper <triage(a)lists.fedoraproject.org>'s request for needinfo: Bug 613361: [abrt] crash in gnome-applets-1:2.30.0-1.fc13: bonobo_closure_invoke_va_list: Process /usr/libexec/multiload-applet-2 was killed by signal 11 (SIGSEGV) https://bugzilla.redhat.com/show_bug.cgi?id=613361

3 2

[Bug 204606] /etc/rpm/macros should be owned by rpm
by Red Hat Bugzilla 18 Aug '26

18 Aug '26

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=204606 Panu Matilainen <pmatilai(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |WONTFIX --- Comment #20 from Panu Matilainen <pmatilai(a)redhat.com> 2008-09-16 05:36:34 EDT --- I don't see much point in owning files that doesn't normally exist. Otherwise we'd have to own many many other files too... WONTFIX as anaconda no longer creates the file. -- 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.

4 3

[Bug 197455] dmesg says CPU has Pentium F0 0F bug..../proc/cpuinfo says it hasnt
by Red Hat Bugzilla 14 May '26

14 May '26

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=197455 --- Comment #20 from Ralf Corsepius <rc040203(a)freenet.de> 2008-09-13 00:24:33 EDT --- Yeah, after all the years, this bug finally seems to be fixed: # uname -a Linux manus 2.6.26.3-29.fc9.i586 #1 SMP Wed Sep 3 03:05:01 EDT 2008 i586 i586 i386 GNU/Linux # dmesg | grep -i'f0 0f' Intel Pentium with F0 0F bug - workaround enabled. # cat /proc/cpuinfo | grep -i 'f00f' f00f_bug : yes -- 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.

6 6

needinfo canceled: [Bug 569641] Sound Juicer could not find any CD-ROM drives to read
by Red Hat Bugzilla 14 May '26

14 May '26

Product: Fedora Version: 12 Component: sound-juicer Jaroslav Franek <jarin.franek(a)post.cz> has canceled Bug Zapper <fedora-triage-list(a)redhat.com>'s request for needinfo: Bug 569641: Sound Juicer could not find any CD-ROM drives to read https://bugzilla.redhat.com/show_bug.cgi?id=569641 ------- Additional Comments from Jaroslav Franek <jarin.franek(a)post.cz> Retested with Fedora 14. Similar issue. The error text now reads: "Sound Juicer could not read the track listing on this CD. Reason: Cannot access CD: The specified location is not mounted" Probably not mounted, but at the same time Dolphin shows correctly the contents of the CD, including correct track info. And the CD plays in VLC media player. KDE does not offer any mount option for the audio CD to me. But anyway, I have turned to other, working, SW for audio ripping, so I do not need this to be fixed.

5 5

[Bug 253630] Clash of short-cut in search dialog
by Red Hat Bugzilla 26 Mar '26

26 Mar '26

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.

23 31

[Bug 304611] resolv.conf hardwired in /sbin/ dhclient-script and network-functions
by bugzilla＠redhat.com 20 Mar '26

20 Mar '26

https://bugzilla.redhat.com/show_bug.cgi?id=304611 --- Comment #20 from Fedora End Of Life <jkurik(a)fedoraproject.org> --- This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora 'version' of '24'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

triage October 2023