NVIDIA Question
by David St.Clair
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
1 year, 10 months
Mouse goes crazy
by Jonathan Villa
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.
???
1 year, 10 months
[Fedora QA] #483: New Live USB Creator Test Day
by fedora-badges
#483: New Live USB Creator Test Day
----------------------+------------------------
Reporter: adamwill | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 24
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
A major F24 feature is a
[https://fedoraproject.org/wiki/Changes/LUCasPrimaryDownloadable rewrite
of liveusb-creator] which may become the primary download for Workstation
(so instead of an ISO file, you'd get the liveusb-creator app from the
Workstation download page). However, we really haven't done much testing
of it yet and don't know if it's working properly, running on all the
platforms it needs to run on, and has all the features it ought to have.
This would be a great topic for a Test Day. We should co-ordinate with the
developers, Jiri Eischmann and Martin Briza, on this - they're both pretty
familiar with QA so they should be open to working with us. I'll mail them
and ask them to sign up to this ticket.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/483>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
7 years, 2 months
[Fedora QA] #472: create testcase for resizing in custom partitioning
by fedora-badges
#472: create testcase for resizing in custom partitioning
------------------------+------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 22
Component: Test cases | Version:
Keywords: | Blocked By:
Blocking: |
------------------------+------------------------
After discovering https://bugzilla.redhat.com/show_bug.cgi?id=1221247 it
seems reasonable we should test this more properly in the future.
Currently we seem to have no test case about resizing partitions in manual
part dialog. We probably should, and test it against at least a standard
partition and a logical volume. Optionally, we can split standard
partitions into ext4 and ntfs, to cover similar use cases as in our
QA:Testcase_partitioning_guided_shrink .
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/472>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
7 years, 3 months
[Fedora QA] #482: Fedora 24 Qt-Gtk Integration Test Day
by fedora-badges
#482: Fedora 24 Qt-Gtk Integration Test Day
----------------------+------------------------
Reporter: jgrulich | Owner:
Type: task | Status: new
Priority: major | Milestone: Fedora 24
Component: Test Day | Version:
Keywords: | Blocked By:
Blocking: |
----------------------+------------------------
We would like to organize a test day to test Qt integration in GNOME
desktop.
What to test (packages):
'''adwaita-qt''' - a Qt theme to make Qt applications to fit into GNOME
desktop
'''qgnomeplatform''' - a Qt platform theme aimed to accommodate as much of
GNOME settings as possible
Who will take care of the test day:
Jan Grulich (jgrulich)
Martin Bříze (mbriza)
When we would like to have the test day:
We don't care about the date, we both can be available probably any day.
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/482>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
7 years, 3 months
[Fedora QA] #480: Fedora 24 Translation (L10n) Test Day
by fedora-badges
#480: Fedora 24 Translation (L10n) Test Day
--------------------------------------+------------------------
Reporter: anipeter | Owner: tflink
Type: task | Status: new
Priority: major | Milestone: Fedora 23
Component: Blocker bug tracker page | Version:
Keywords: l10n, fltg | Blocked By:
Blocking: |
--------------------------------------+------------------------
Fedora 24 Alpha release is on 22nd March (Tuesday) and Software
Translation Deadline is on 5th April (Tuesday) [1].
As per mail discussion [2], the date for F24 L10n Test day is finalized as
29th March (Tuesday)
FLTG team will be working towards coordinating and arranging the test day
including creating new test cases, reviewing old test cases, listing
existing bugs, provide required assistance to get the image for testing,
help testers on test day etc. The list of items to do will be listed soon.
Thanks Ani Peter (apeter)
FLTG
[1] - https://fedoraproject.org/wiki/Releases/24/Schedule[[BR]]
[2] - bit.ly/1TdUirs
--
Ticket URL: <https://fedorahosted.org/fedora-qa/ticket/480>
Fedora QA <http://fedorahosted.org/fedora-qa>
Fedora Quality Assurance
7 years, 3 months
F24 anaconda update karma request
by Adam Williamson
Hey folks! So we have a new anaconda which could do with karma:
https://bodhi.fedoraproject.org/updates/anaconda-24.13.2-1.fc24
current stable anaconda is entirely broken, so it would be good to get
this pushed out. If you've managed to get pungi4 and/or livemedia-
creator to spit out images locally, more power to you (I'm damned if I
can) and you can test that way. Otherwise you have the option of using
a current live image and updating anaconda packages in the live
environment before running the installer, or you can use this updates
image:
https://www.happyassassin.net/updates/24test.img
with a current F24 nightly - that should be more or less equivalent to
the package build, at least good enough to provide karma for the
update.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 8 months
Lenovo T500, kernels, and NetworkManager
by Russel Winder
My Lenovo T500 will not boot 4.6 though it will 4.5 ones. I have posted
a bug report. https://bugzilla.redhat.com/show_bug.cgi?id=1320922
However it seems that since the last update of the iwl* files, or maybe
the NetworkManager files, kernel 4.5 will not start the WiFi. From what
I can see the fact that NetworkManager is still a running service means
that the wired Ethernet port cannot be started.
Is there something wrong with my set up that stops NetworkManager using
wired Ethernet?
I found that stopping the NetworkManager service allows me to use ifup
to get the wired Ethernet working, but this is initd type stuff rather
than systemd type stuff and so feels ugly, or is it the right thing?
What is officially the best way of getting wired Ethernet to be part of
the set up?
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel(a)winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
7 years, 8 months
Fedora 24: i686 images no longer 'release blocking'
by Adam Williamson
Hi, folks! As discussed at last week's meeting, it seemed a good idea
to flag this up on the list for anyone who missed it.
From Fedora 24 onwards, FESCo has decided that i686 (32-bit x86) images
are no longer 'release blocking', by policy:
https://fedorahosted.org/fesco/ticket/1469
I have tweaked the release criteria 'preamble' text slightly to mention
this explicitly, and also to link to the canonical list of release-
blocking images that the program manager is maintaining now (the F24
list is
https://fedoraproject.org/wiki/Fedora_Program_Management/ReleaseBlocking/... ).
I noted that the question of whether we 'support' / block on 32-bit
*upgrades* is not yet resolved, so I've filed a FESCo ticket for that:
https://fedorahosted.org/fesco/ticket/1539
What this means to us is pretty simple: we no longer have to worry
about getting all the validation tests done for 32-bit images. Woot! We
still *can* test them, if we want, but we don't have to. They're just
like the LXDE live, or any other non-blocking image.
An outstanding question is what we do with the validation matrices.
Cloud was easy enough - I just marked all rows in the i386 table as
'Optional'. Base, Server and Desktop don't really split out x86_64 and
i386/i686 (sidebar: the best thing about ditching i386/i686/x86_32 is
we no longer have to be terminally confused about what it's freaking
*called*...), so they're OK too. However, Installation is a bit of a
problem:
https://fedoraproject.org/wiki/Template:Installation_test_matrix
quite a lot of the tables have 'i386' and 'x86_64' as environments.
Especially with the Milestone column, listing i386 alongside x86_64 is
a bit misleading if i386 is no longer blocking. I can see a few
options:
1) just ditch the i386 columns entirely; openQA can continue testing
it, and people can test manually if they want, but we don't bother
tracking the results in the validation pages
2) stick an admon template at the top of the page saying 'the i386
tests aren't blocking', with links out to the criteria and/or the FESCo
ticket
3) Duplicate each table which distinguishes between 'i386' and
'x86_64', so we have one table with just an 'i386' column and all tests
marked Optional, and another table with the other columns and the
appropriate milestone
I can see arguments for any of those approaches. #1 is nice and simple
and reduces the scariness of the page, but I guess means we don't get a
quick overview of i386 status and probably means fewer people bothering
to do i386 tests. I don't know how much we care about that.
#2 is also simple and keeps the tests around, but people are probably
going to miss the admon note and will therefore be confused about
whether we're "missing" a lot of required results, if i386 isn't done.
#3 is probably the most 'theoretically correct', but would probably be
something of a giant PITA to read. I suppose we could have the i386
tables collapsed by default. That might work. Now I think about it,
though, I think having rows that are identical except for their
environments might confuse python-wikitcms, I'd have to look into it.
If you're thinking "4) change the Milestone column", I'd rather not,
because those values are somewhat significant to Wikitcms. Other ideas
welcome!
If anyone can think of any other system/process which might need
adjusting for this change, too, please do let us know! Or just go fix
it. ;)
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
7 years, 8 months
