Comparing other distros kernels to Fedora.
by Rodd Clarkson
I've been having troubles getting 2.6.34.x kernels on f13 and 2.6.35.x
kernels on f14 to resume from suspend.
https://bugzilla.redhat.com/show_bug.cgi?id=628897
To try and resolve this I've been trying out other recent distros to see if
they have similar kernels and whether I have the same problem resuming.
Recent ubuntu is still only using 2.6.32 but openSUSE 11.3 has a 2.6.34
kernel and I can suspend and resume from it using the live CD. How can I
compare this kernel to ones in f13/f14 to see why it works in one and not in
the other?
Rodd
13 years, 6 months
[Fedora QA] #87: Expand desktop release criteria and validation
by fedora-badges
#87: Expand desktop release criteria and validation
---------------------------+------------------------------------------------
Reporter: jlaska | Owner: adamwill
Type: enhancement | Status: new
Priority: major | Milestone: Fedora 14
Component: Wiki | Version:
Keywords: retrospective |
---------------------------+------------------------------------------------
= problem =
[http://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test Desktop
test results] were often not available for non-GNOME desktops. This
leaves a large exposure come release day (for Alpha, Beta or Final).
= analysis =
The desktop release criteria are specific to GNOME. As a result, there is
no incentive to finding bugs in XFCE, LXDE or KDE.
= enhancement recommendation =
This might be too much for once ticket. Feel free to split this out into
more if needed.
Recommend looking for opportunities to improve communication between teams
and increasing non-GNOME desktop testing leading up to milestones.
* The goal is to extend the desktop validation testing introduced in
Fedora 13 to cover the main non-default desktops: KDE, Xfce and LXDE.
* Update appropriate desktop validation content as needed (see
[http://fedoraproject.org/wiki/QA:Desktop_validation_testing desktop
validation testing])
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/87>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 6 months
[Fedora QA] #94: Add several release criteria based on feedback from desktop SIGs
by fedora-badges
#94: Add several release criteria based on feedback from desktop SIGs
-----------------------------------------+----------------------------------
Reporter: adamwill | Owner: adamwill
Type: defect | Status: new
Priority: major | Milestone: Fedora 14
Component: Proventester Mentor Request | Version:
Keywords: |
-----------------------------------------+----------------------------------
Discussing the expansion of desktop validation testing to other major
desktops - https://fedorahosted.org/fedora-qa/ticket/87 - has resulted in
several proposed additional release criteria:
* Saving passwords in the desktop default keyring (if the desktop
implements one), and retrieving passwords from the keyring, must work
* The desktop default update manager must not periodically check for
updates when the system is booted live, but must periodically check for
updates when running on an installed system
* The desktop's offered mechanisms for shutting down, logging out and
rebooting must work
We should consider adding these to the release criteria, and select
appropriate levels for each.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/94>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 6 months
[Fedora QA] #105: F14 Graphics Test Week
by fedora-badges
#105: F14 Graphics Test Week
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: defect | Status: new
Priority: major | Milestone: Fedora 14
Component: Test Day | Version:
Keywords: |
----------------------+-----------------------------------------------------
We should have a Graphics Test Week for F14, as usual. I will organize it.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/105>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 6 months
[Fedora QA] #104: F14 systemd Test Day
by fedora-badges
#104: F14 systemd Test Day
----------------------+-----------------------------------------------------
Reporter: adamwill | Owner: adamwill
Type: defect | Status: new
Priority: major | Milestone: Fedora 14
Component: Test Day | Version:
Keywords: |
----------------------+-----------------------------------------------------
Lennart is enthusiastic about having a Test Day for systemd for F14. I
will organize one.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/104>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
13 years, 6 months
F14 Branched -- hard freezes
by Martin Sourada
Hi all,
I've been encountering a strange issue I have no idea how to handle --
my laptop hard freezes about an half an hour after boot, irrespective of
what am I doing (first I was doing something in midori, second I was
listening to some song in rhythmbox, third I wasn't even present).
Screen freezes, one cannot ping the machine, sound, if any is playing at
the time of freeze, plays an infinite loop.
Strange thing is, when I was home it didn't froze for 3 straight days.
It does not freeze on F12 either. The only difference is that at the
place where it freezes I also have external USB HDD, USB keyboard and
USB wireless mouse connected and use wired connection instead of
wireless.
Anyone one having similar issues? Any idea how to debug this? How to
produce some usable info in order to fill a bug?
Thanks,
Martin
13 years, 6 months
Review request: Nice-to-have bug process documentation proposal
by Adam Williamson
Hi, everyone. So we partly used the proposed new nice-to-have bug
tracking system during the F14 Beta process, and it seemed to go well.
In a quick burst of airport productivity, I've quickly written up a
bunch of proposed new wiki pages and modifications to existing ones to
document the nice-to-have process (and, incidentally, extend
documentation of the blocker process, since we don't seem to have much
of it beyond the blocker meeting SOP right now). All the pages can be
found here:
https://fedoraproject.org/wiki/Category:NTH_adjustment_drafts
it should be pretty obvious which are new and which are modifications of
existing pages. I hope this is mostly straightforward and
non-controversial.
A quick five-minute summary is that we will now have (in fact, we
already do) trackers for nice-to-have bugs for Alpha, Beta and Final
releases as well as trackers for blocker bugs. Bugs on these NTH lists
will be given priority after blocker bugs for QA, devel and releng work
for releases. Fixes for these bugs - and *only* these bugs, if a fix is
to be taken through a freeze, there must be a matching accepted NTH bug
- will be taken through release freezes. Proposing, reviewing and
monitoring NTH bugs will work exactly as it does for blocker bugs, and
mostly happen in the blocker meetings, but of course after consideration
of the blocker lists.
In practice this is a formalization of existing procedure - until F14
Beta, QA and releng did much the same process but entirely informally,
we just kept lists of bugs we'd take fixes for either in our heads or in
the RC creation trac tickets. This process is meant to be more robust,
documented and discoverable.
Some releng SOP pages may require minor updates, I figured I'd leave
that to releng. The process for creating blocker trackers should also be
updated to cover creating NTH trackers (I couldn't find that; poelcat,
where is it?)
Comments, questions, suggestions welcome!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
13 years, 6 months
