test October 2018

test@lists.fedoraproject.org

37 participants
208 discussions

NVIDIA Question
by David St.Clair 17 Jan '22

17 Jan '22

This may be a dumb question, but why can't Redhat distribute NVIDIA binary drivers? In NVIDIA's licence (http://www.nvidia.com/object/nv_swlicense.html) it says: "2.1.2 Linux Exception. Notwithstanding the foregoing terms of Section 2.1.1, SOFTWARE designed exclusively for use on the Linux operating system may be copied and redistributed, provided that the binary files thereof are not modified in any way (except for unzipping of compressed files)." So, what's keeping RedHat from putting the drivers in the distribution? If it's a GPL thing, would it be easy to just download it during installation or at least give the option to the user? Thanks, -- David St.Clair dstclair(a)cs.wcu.edu

10 20

Mouse goes crazy
by Jonathan Villa 17 Jan '22

17 Jan '22

Ok, I have had Yarrow working well for a while now, but yesterday I started experiencing some odd issues with my mouse. All of a sudden it stops working correctly. The only thing that seems to fix is to kill X and run mouse-test, then restart. Any ideas? Also, I have FC 1 running on a desktop which is hooked up to a KVM switch. Whenever I go to another PC, and return, the same thing happens, the mouse goes crazy. ???

8 7

Fedora Modular 27 compose report: 20171028.n.0 changes
by Fedora Branched Report 02 Nov '20

02 Nov '20

OLD: Fedora-Modular-27-20171028.n.0 NEW: Fedora-Modular-27-20171028.n.0 ===== SUMMARY ===== Added images: 0 Dropped images: 0 Added packages: 0 Dropped packages: 0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0.00 B Size of dropped packages: 0.00 B Size of upgraded packages: 0.00 B Size of downgraded packages: 0.00 B Size change of upgraded packages: 0.00 B Size change of downgraded packages: 0.00 B ===== ADDED IMAGES ===== ===== DROPPED IMAGES ===== ===== ADDED PACKAGES ===== ===== DROPPED PACKAGES ===== ===== UPGRADED PACKAGES ===== ===== DOWNGRADED PACKAGES =====

1 0

proposal: drop optical media from release criteria
by Matthew Miller 08 Jul '19

08 Jul '19

Justification: http://newsthump.com/2018/05/21/man-decides-to-keep-box-of-cables-hes-has-s… -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

19 85

Re: Criteria / validation proposal: drop Xen
by Adam Williamson 27 Apr '19

27 Apr '19

On Thu, 2017-07-06 at 15:13 -0400, Konrad Rzeszutek Wilk wrote: > On Thu, Jul 06, 2017 at 11:59:01AM -0700, Adam Williamson wrote: > > Hi, folks! A while ago, Xen virtualization functionality was added to > > the criteria and the validation test case set, on the understanding > > that Oracle would provide testing for it (and help fix bugs as they > > arose). > > > > For the last couple of releases we really have not had any such testing > > We had been doing the testing, it just that we (or rather me and > Dariof) seem to get a wind of this at the last minute. Not sure exactly > how to fix that thought. Well, I mean, every few *days* a compose gets nominated for validation testing, and a mail is sent to test-announce. Just check your test- announce archives for mails with "nominated for testing" in their subject lines, and you'll see dozens. Is this not sufficient notification? > > from Oracle. On that basis, I'm proposing we remove this Final > > criterion: > > s/Oracle/Xen Project/ I believe? Perhaps, it's just that it always seemed to be you doing the testing, so they got a bit conflated :) > > "The release must boot successfully as Xen DomU with releases providing > > a functional, supported Xen Dom0 and widely used cloud providers > > utilizing Xen." > > > > and change the 'milestone' for the test case - > > https://fedoraproject.org/wiki/QA:Testcase_Boot_Methods_Xen_Para_Virt - > > from Final to Optional. > > > > Thoughts? Comments? Thanks! > > I would prefer for it to remain as it is. This is only practical if it's going to be tested, and tested regularly - not *only* on the final release candidate, right before we sign off on the release. It needs to be tested regularly throughout the release cycle, on the composes that are "nominated for testing". Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

7 9

Blocking criteria proposal for F30+: Printing
by Stephen Gallagher 01 Apr '19

01 Apr '19

There was a bug[1] filed recently that indicated that printing was broken on certain printers. As a result of that discussion, it became apparent that there was no criteria for printing to work at all, which seems like an oversight. I discussed this briefly with Matthias Clasen this morning and he agreed that this should be treated as blocking for Workstation. I'd like to propose that we add the following criteria to Beta for Fedora 30+: * Printing must work on at least one printer available to Fedora QA. "Work" is defined as the output from the device matching a preview shown on the GNOME print preview display. (Note that differences in color reproduction are not considered "non-working".) and this to Final for Fedora 30+: * Printing must work on at least one printer using each of the following drivers: (I don't know which ones to specify here, but we ought to try to figure out a cross-section that covers a large swath of our expected user base). [1] https://bugzilla.redhat.com/show_bug.cgi?id=1628255

8 13

Proposal to modify release criteria for fwraid
by Stephen Gallagher 16 Nov '18

16 Nov '18

At yesterday's F29 Go/No-Go meeting, we discussed the blocker status of BZ #1628192 - Fedora 29 installation cannot see a firmware RAID device. While the blocker criteria clearly states that this should be a blocker for Beta, many of the people present at the meeting disagreed, for a variety of reasons. * Hardware supporting fwraid is considerably less pervasive than it was when the criterion was written * Testing this criterion can only be done with install media, which limits our testing pool to the very dedicated members of Fedora QA. Yes, anyone *can* download a nightly compose and try it, but in practice this tends to be limited to the core testers. The majority of testing that this feature will get will tend to happen as people try out the Beta release. To that end, I'd like to propose that we make the following change to the criteria going forward: "The blocking criterion for successful installation atop a firmware RAID array is moved to the GA release criteria."

5 7

Nvidia and Fedora current state
by Michael Schwendt 06 Nov '18

06 Nov '18

What's the current state of Fedora with regard to Nvidia graphics hardware? Should it just work? On a machine with GeForce GTX 1060, Fedora 28 suffers badly from freezes and slowdowns during boot, unbearable slow mouse movement on the GDM login screen, then more freezes before GNOME Shell appears but isn't really usable because everything is slow as a snail. Switching the login settings from Wayland to Xorg at least results in a usable GNOME Shell. Installing the Nvidia driver packages from rpmfusion hasn't made a difference. The current Fedora 29 Live Workstation image starts, but faces mysterious freezes before the desktop appears. Installation to harddisk has worked, but I've run into a series of unrelated issues, and the performance of GNOME Shell isn't pretty. It takes too long to start a terminal, or suddenly the shell freezes for 10-15 seconds and restarts.

6 15

Test Results:Fedora 29 RC 1.2 Desktop
by pmkellly＠frontier.com 03 Nov '18

03 Nov '18

In regard to the test results page and the specified order of testing: Following up on a comment I made on a message earlier today concerning if the updates-testing repo should be enabled for Anaconda installs and the impression I am under that we want to do testing on each drop according to this matrix before any updates are applied I edited the subject page to move the Updates Graphical test to be the last test in the Beta sequence. I searched for the source of the matrix, but could not find it. Then I considered that that each matrix may be made by editing the last one. That's why I edited this page at least to get the suggestion going. I would further suggest that we add a command line DNF test at the end of the final sequence, but I did not add such a test to the page. Awaiting your feedback. Have a Great Day! Pat (tablepc)

4 4

Fedora updates-20181031.0 compose check report
by Fedora compose checker 31 Oct '18

31 Oct '18

No missing expected images. Failed openQA tests: 2/2 (x86_64) New failures (same test did not fail in updates-20181030.0): ID: 303943 Test: x86_64 AtomicHost-dvd_ostree-iso install_default URL: https://openqa.fedoraproject.org/tests/303943 ID: 303944 Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/303944 -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test October 2018