"Basic graphics mode" feature and criterion discussion
by Adam Williamson
Hi folks!
So at last week's Fedora 30 Beta Go/No-Go meeting, it was decided that
the Basic release criterion:
"Boot menu contents
The boot menu for all supported installer and live images should
include an entry which causes both installation and the installed
system to use a generic, highly compatible video driver (such as
'vesa'). This mechanism should work correctly, launching the installer
or desktop and attempting to use the generic driver."
should no longer apply to Beta - i.e. that it should no longer be a
Basic or Beta criterion.
The justification for this is, I hope I am correctly representing all
views here (please say so if not), that this mechanism is both less
necessary (due to a general reduction in the amount of 'weird' graphics
hardware out there, and general improvement in the reliability and
coverage of the major drivers for the major graphics hardware
manufacturers) and inherently less likely to work (due to the general
trend of work on kernel modesetting and Wayland) than it used to be.
For context, it is worth noting that the *feature* predates the
introduction of both kernel modesetting *and* Wayland to Fedora. What
the feature initially did was tell anaconda to write an X config file
specifying the 'vesa' driver (instead of working out the correct
'native' driver for the adapter and writing a config file specifying
that). After KMS was introduced in Fedora 10, the mechanism was tweaked
to also pass the 'nomodeset' kernel parameter to disable KMS. Around
2012 (https://bugzilla.redhat.com/show_bug.cgi?id=858270) we noticed
that the X config file mechanism was a bit superfluous as 'nomodeset'
alone could basically be relied on to force some sort of 'fallback
mechanism', and so the feature was simplified to *only* specify the
'nomodeset' kernel parameter (this is all it does now).
The *criterion* dates to 2010, in the Fedora 15 release cycle: it
appears in the Fedora 15 Alpha criteria but not the Fedora 14 Alpha
criteria. It was added on 2010-08-16:
https://fedoraproject.org/w/index.php?title=Fedora_15_Alpha_Release_Crite...
The group at the meeting did not, however, make any further decisions,
so this leaves us with some open questions:
0) Do we generally agree with the decision made at the meeting? If
anyone (especially a subject matter expert) strongly believes the
decision was wrong and this should still be a Basic/Beta requirement,
please say so.
1) Should the criterion be modified somehow, but some requirement in
relation to some kind of fallback graphical mode be kept at Basic or
Beta?
2) Should the criterion be moved to Final, unchanged or changed
somehow?
3) Should the requirement just basically be dropped entirely as no
longer useful?
4) (This one mainly for ajax and airlied) to what extent does the
concept of a 'fallback option' for our supported desktop environments
and graphical servers still actually make sense? Could a different
implementation of the same basic idea be envisaged, and would it be
useful? If so, should we do that, and what would be the consequences
for the criteria?
I realize this is quite a big and fuzzy topic, but I'm hoping the
responses to this mail will clarify our path :) So if you have any kind
of useful information or strong opinions on the general area here,
please do contribute them, and hopefully a clearer way forward will
emerge.
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
5 years, 1 month
Re: F30 KDE Spin no Login GUI after update
by Adam Williamson
On Fri, 2019-03-22 at 16:07 +0000, Rodger Etz wrote:
> Hi,
>
> Sounds like what I see using the F29 KDE spin upgraded to F30 on bare metal x86_64.
>
> It seems SDDM is not launching properly via systemd anymore.
>
> When you switch to another TTY, login and execute
>
> systemctl stop sddm && sddm
>
> it starts properly.
>
> Did a quick strace and saw that something is trying to access some file without success when launching via systemd.
>
> Sorry, didn't have time to dive into it and file an issue yet.
It's likely to be the same thing affecting Rawhide:
https://bugzilla.redhat.com/show_bug.cgi?id=1686675
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
5 years, 1 month
Re: [Test-Announce] Fedora 30 Candidate Beta-1.4 Available Now!
by Adam Williamson
On Thu, 2019-03-21 at 01:36 +0000, rawhide(a)fedoraproject.org wrote:
> According to the schedule [1], Fedora 30 Candidate Beta-1.4 is now
> available for testing. Please help us complete all the validation
> testing! For more information on release validation testing, see:
> https://fedoraproject.org/wiki/QA:Release_validation_test_plan
>
> Test coverage information for the current release can be seen at:
> https://www.happyassassin.net/testcase_stats/30
>
> You can see all results, find testing instructions and image download
> locations, and enter results on the Summary page:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Summary
>
> The individual test result pages are:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Installation
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Base
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Server
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Cloud
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Desktop
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Security_Lab
>
> All Beta priority test cases for each of these test pages [2] must
> pass in order to meet the Beta Release Criteria [3].
>
> Help is available on #fedora-qa on irc.freenode.net [4], or on the
> test list [5].
Hey folks!
So, unfortunately we had some trouble getting a candidate build done,
but now we have one. The go/no-go meeting is on Thursday at 17:00 UTC -
that's in about 11 hours. Obviously time is tight to do the testing,
but if folks could help test as much stuff as possible, that'd be
great.
We do have one outstanding blocker bug, but there's a chance it'll get
downgraded at the meeting, so it'd be great if we could complete the
testing for all Beta tests on this compose. If there isn't enough time,
though, no-one will blame us :)
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
5 years, 1 month
Missing icons - purpose or a bug?
by Lukas Ruzicka
Hello,
I was doing a test to start every single application in KDE menus. I
realized that some applications are gone from the menu, however they were
present some time ago. I was using KDE Live CD, compose 20190301.
1. In All Applications -> Administration, there was "Users" to
administer users. Now, the icon has disappeared and is not elsewhere. The
only way I could start users now is through the Search bar or System
settings.
2. Similarly, in All Applicatons -> Settings, there was Network
Configuration. It has disappered from the main menu.
My question is, is this a purpose? Or is it a bug?
Thanks.
--
Lukáš Růžička
FEDORA QE, RHCE
Red Hat
<https://www.redhat.com>
Purkyňova 115
612 45 Brno - Královo Pole
lruzicka(a)redhat.com
TRIED AND PERSONALLY TESTED, ERGO TRUSTED. <https://redhat.com/trusted>
5 years, 1 month
notifications
by Neal Becker
Up until now, notifications showed up in the notification area near the
panel. After last update (I think) notifications are showing up as annoying
yellow rectangles which mostly appear on the right top of the screen. These
boxes clutter up the screen and have to be clicked to remove.
Anyone know why the behavior suddenly changed and how to restore the
original?
Thanks,
Neal
5 years, 1 month
SDDM Themes not working
by Gerald B. Cox
I find that I now cannot select themes - and I'm getting either a solid
white or blue background when SDDM starts.
When I tried to test, this is what I received:
sddm-greeter --theme /usr/share/sddm/themes/01-fedora-breeze
[11:43:09.032] (II) GREETER: High-DPI autoscaling not Enabled
[11:43:09.108] (EE) GREETER: Socket error: "QLocalSocket::connectToServer:
Invalid name"
[11:43:09.109] (EE) GREETER: Cannot connect to the daemon - is it running?
[11:43:09.317] (II) GREETER: Loading
file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml...
[11:43:09.317] (WW) GREETER:
file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml: No such file or
directory
[11:43:09.317] (WW) GREETER:
file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml: No such file or
directory
[11:43:09.317] (WW) GREETER: Fallback to embedded theme
Wanted to see if there was a quick fix or if this is known before I create
a bug report.
I didn't see anything on bugzilla, but might have missed it.
Thanks!
5 years, 1 month
