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
Io games have become quite famous because of their fun and captivating gameplay. It might show up as exciting conflicts or challenging tactical circumstances.
Io games are online multiplayer browser games that don't require any downloads or installations. Those with reliable internet connections can access these games right away. Since IO games usually have simple controls and gameplay, they're a great way to unwind.
Click https://io-games.onl/ to enjoy hot io games!
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.
https://bugzilla.redhat.com/show_bug.cgi?id=250843
Jordan <spiffyclean62(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |spiffyclean62(a)gmail.com
--- Comment #10 from Jordan <spiffyclean62(a)gmail.com> ---
It sounds like you've delved deep into the technicalities, specially with the
issues associated with filesystem consistency and metadata validation.
Your approach with the use of xfs_freeze/thaw around grub sell off to clear up
the striking difficulty is interesting, even though you rightly point out its
obstacles, specifically while /boot is part of the foundation filesystem.
Regarding the validation technique in grub-set up, if it aims to make sure
record integrity and area accuracy, perhaps exploring alternatives like FIBMAP
calls may be useful, as you cautioned. These calls might provide a extra
reliable manner to confirm file places with out the want for freezing or
unmounting the filesystem.
I also faced the bug on my site but its solve now :
https://spiffyclean.com.au/commercial-cleaning-company-melbourne/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=250843
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=244697
Fedora Admin user for bugzilla script actions <fedora-admin-xmlrpc(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|kernel-maint(a)redhat.com |jforbes(a)redhat.com
--- Comment #43 from Fedora Admin user for bugzilla script actions <fedora-admin-xmlrpc(a)fedoraproject.org> ---
This package has changed maintainer in Fedora. Reassigning to the new
maintainer of this component.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=244697
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
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.
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