F32, Automatic suspend isn't working.
by Chris Murphy
cross-posting test@ and desktop@
Fedora Workstation 32 (upgraded from f31)
Laptop on battery power set aside, 12 hours later it's dead instead of
sleeping. On F31 it reliably would sleep after 20 minutes.
Sleep still happens when pressing the power button and closing the
lid. It seems to be a GNOME automatic suspend timer problem.
Using dconf editor, I changed the
/org/gnome/settings-daemon/plugins/power/sleep-inactive-battery-timeout
Custom value 30 and the problem doesn't happen. Is there a way to
increase debug messages somehow to find out whether this timeout is
being reached? And what process or policy is causing it to be reset?
With the available information I can't figure out what's preventing
sleep.
--
Chris Murphy
1 year, 1 month
Release criteria proposal: networking requirements
by Adam Williamson
Hi folks!
So at this week's blocker review meeting, the fact that we don't have
explicit networking requirements in the release criteria really started
to bite us. In the past we have squeezed networking-related issues in
under other criteria, but for some issues that's really difficult,
notably VPN issues. So, we agreed we should draft some explicit
networking criteria.
This turns out to be a big area and quite hard to cover (who'd've
thought!), but here is at least a first draft for us to start from. My
proposal would be to add this to the Basic criteria. I have left out
some wikitext stuff from the proposal for clarity; I'd add it back in
on actually applying the proposed changes. It's just formatting stuff,
nothing that'd change the meaning. Anyone have thoughts, complaints,
alternative approaches, supplements? Thanks!
=== Network requirements ===
Each of these requirements apply to both installer and installed system
environments. For any given installer environment, the 'default network
configuration tools' are considered to be those the installer documents
as supported ways to configure networking (e.g. for anaconda-based
environments, configuration via kernel command line options, a
kickstart, or interactively in anaconda itself are included).
==== Basic networking ====
It must be possible to establish both IPv4 and IPv6 network connections
using DHCP and static addressing. The default network configuration
tools for the console and for release-blocking desktops must work well
enough to allow typical network connection configuration operations
without major workarounds. Standard network functions such as address
resolution and connections with common protocols such as ping, HTTP and
ssh must work as expected.
Footnote titled "Supported hardware": Supported network hardware is
hardware for which the Fedora kernel includes drivers and, where
necessary, for which a firmware package is available. If support for a
commonly-used piece or type of network hardware that would usually be
present is omitted, that may constitute a violation of this criterion,
after consideration of the [[Blocker_Bug_FAQ|hardware-dependent-
issues|normal factors for hardware-dependent issues]]. Similarly,
violations of this criteria that are hardware or configuration
dependent are, as usual, subject to consideration of those factors when
determining whether they are release-blocking
==== VPN connections ====
Using the default network configuration tools for the console and for
release-blocking desktops, it must be possible to establish a working
connection to common OpenVPN, openconnect-supported and vpnc-supported
VNC servers with typical configurations.
Footnote title "Supported servers and configurations": As there are
many different VPN server applications and configurations, blocker
reviewers must use their best judgment in determining whether
violations of this criterion are likely to be encountered commonly
enough to block a release, and if so, at which milestone. As a general
principle, the more people are likely to use affected servers and the
less complicated the configuration required to hit the bug, the more
likely it is to be a blocker.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
1 year, 9 months
[Fedora 34] Call for Test Days
by Sumantro Mukherjee
Hi Fedora users, developers and friends!
It's time to start thinking about Test Days for Fedora 34.
For anyone who isn't aware, a Test Day is an event usually focused
around IRC for interaction and a Wiki page for instructions and results,
with the aim being to get a bunch of interested users and developers
together to test a specific feature or area of the distribution. You can
run a Test Day on just about anything for which it would be useful to do
some fairly focused testing in 'real time' with a group of testers; it
doesn't have to be code, for instance, we often run Test Days for
l10n/i18n topics. For more information on Test Days, see
https://fedoraproject.org/wiki/QA/Test_Days .
Anyone who wants to can host their own Test Day, or you can request that
the QA group helps you out with organization or any combination of the
two. To propose a Test Day, just file a ticket in fedora-qa pagure - here's
an example https://pagure.io/fedora-qa/issue/624 . For
instructions on hosting a Test Day, see
https://fedoraproject.org/wiki/QA/SOP_Test_Day_management .
You can see the schedule at https://pagure.io/fedora-qa/issues?tags=test+days .
There are many slots open right now. Consider the development
schedule, though, in deciding when you want to run your Test Day - for
some topics you may want to avoid
the time before the Beta release or the time after the feature freeze
or the Final Freeze.
We normally aim to schedule Test Days on Thursdays; however, if you want
to run a series of related Test Days, it's often a good idea to do
something like Tuesday / Wednesday / Thursday of the same week (this is
how we usually run the X Test Week, for instance). If all the Thursday
slots fill up but more people want to run Test Days, we will open up
Tuesday slots as overflows. And finally, if you really want to run a
Test Day in a specific time frame due to the development schedule, but
the Thursday slot for that week is full, we can add a slot on another
day. We're flexible! Just put in your ticket the date or time frame you'd
like, and we'll figure it out from there.
If you don't want to run your own Test Day, but you are willing to
help with another, feel free to join one or more of already accepted
Test Days:
GNOME Test Day
i18n Test Day*
Kernel Test Week*
Upgrade Test Day*
IoT Test Week*
And don't be afraid, there are a lot of more slots available for your
own Test Day!
[*] These are the test days we run generally to make sure everything
is working fine, the dates get announced as we move into the release
cycle.
If you have any questions about the Test Day process, please don't
hesitate to contact me or any member of the Fedora QA team on test at
lists.fedoraproject.org or in #fedora-qa on IRC. Thanks!
Best Regards,
Sumantrom
Fedora QE
3 years, 1 month
Fedora Workstation WG minutes, 2020-10-27
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2020-10-27)
==============================================
Meeting started by cmurf at 17:35:23 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2020-10-28/workstation...
.
Meeting summary
---------------
* Rollcall (cmurf, 17:35:54)
* present: mclasen, aday, mcatanzaro, kalev, otaylor, tpopela, jens,
neal, langdon, cmurf (cmurf, 17:35:55)
* regrets wg members: (cmurf, 17:35:57)
* present guests: James (cmurf, 17:35:59)
* Approve 20 October minutes (cmurf, 17:36:01)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2020-10-21/workstation...
(cmurf, 17:36:03)
* Minutes are approved (cmurf, 17:36:05)
* Announcements (cmurf, 17:36:07)
* F33 release is 30 minutes away (cmurf, 17:36:09)
* aday wants to do F33 release retrospective discussion in future
(cmurf, 17:36:11)
* US election next week, do we hold meeting as usual? Yes, most of us
will be here. (cmurf, 17:36:13)
* Follow-ups and status reports (cmurf, 17:36:15)
* F34 planning (cmurf, 17:36:17)
* LINK: F34 milestone issues:
https://pagure.io/fedora-workstation/issues?status=Open&milestone=Fedora+34
(cmurf, 17:36:19)
* LINK: Issues with no milestone:
https://pagure.io/fedora-workstation/issues?status=Open&milestone=none&cl...
(cmurf, 17:36:21)
* WG examines the list of issues tagged for F34 (cmurf, 17:36:23)
* Neal discusses btrfs full-disk encryption, goal for F34 (cmurf,
17:36:25)
* Neal asks tpopela about progress on removing Chrome's dependency on
atd. atd is already removed from F34 (fedora-workstation#183)
(cmurf, 17:36:27)
* ACTION: tpopela to work with Chrome upstream to remove atd
dependency. (cmurf, 17:36:29)
* Neal wants to rename fedora-workstation-repos package to something
generic so it can be used in desktop spins. (cmurf, 17:36:31)
* Matthias asks about generic camera app, is it a wishlist or
something that actually exists? aday and Neal reply that it already
exists. (cmurf, 17:36:33)
* aday asks how to handle apps that currently depend on Cheese; this
is something we need to think about. (cmurf, 17:36:35)
* Langdon asks what's wrong with Cheese? aday wants photo booth to be
less kooky, fewer fun effects. (cmurf, 17:36:37)
* aday wants to make progress on fedora-workstation#105 (install
fedora-workstation-repositories by default) and
fedora-workstation#108 (filtered view of flathub) (cmurf, 17:36:39)
* topela asks about systemd-oomd, which will be included in systemd
247. Neal suggests that we stick with earlyoom for F34, unless
systemd developers request otherwise. (cmurf, 17:36:41)
* WG examines the list of issues not tagged for F34 (cmurf, 17:36:43)
* Neal provides status update on fedora-workstation#161 (btrfs disk
integration). Development work stalled (cmurf, 17:36:45)
* tpopela mentions H.264 support in Firefox (fedora-workstation#126).
mstransky has been working on this. Neal says Firefox 81 should use
OpenH264 directly instead of via ffmpeg, so this should be fixed.
Michael suggests we should test Firefox and confirm it actually
works before closing the issue. (cmurf, 17:36:47)
* Neal discusses automatically installing OpenH264
(fedora-workstation#84). This still needs more work (possibly in
gnome-initial-setup) (cmurf, 17:36:49)
* WG discusses btrfs documentation for how to rescue corrupted
filesystem (fedora-workstation#157). Neal says this is WIP. (cmurf,
17:36:51)
* Neal says btrfs upstream is also fixing btrfs dependency on system
page size. (cmurf, 17:36:53)
* ABRT: Michael says status is not good, and probably not likely to
improve. (cmurf, 17:36:55)
* Neal mentions debuginfod. Local retracing should no longer require
installing debug RPMs anymore. ABRT developers are planning to work
on this. (cmurf, 17:36:57)
* Michael proposes to move some btrfs issues to the btrfs tracker.
(cmurf, 17:36:59)
* ACTION: Michael to move the issues (cmurf, 17:37:01)
* aday asks about fedora-workstation#125 (guidelines for preinstalled
and nonremovable apps). (cmurf, 17:37:03)
* ACTION: aday to prepare guidelines. (cmurf, 17:37:05)
* Neal suggests we close fedora-workstation#124 (anaconda: no more
hub). Michael closes the issue. (cmurf, 17:37:07)
* Neal asks do we replace PulseAudio with pipewire in F34? Kalev says
that's a question for Wim. tpopela says Wim is planning on F35, not
F34. Neal says Fedora Jam will use it in F34 anyway. (cmurf,
17:37:09)
* ACTION: Neal to discuss with Wim. (cmurf, 17:37:11)
* James mentions gnome-software downloading entire F33 runtime when
installing dconf-editor is unexpected. (This is related to
fedora-workstation#187.) (cmurf, 17:37:13)
* Open Floor (cmurf, 17:37:15)
* WG discusses timezones and DST. Remember meeting time is pinned to
US Eastern time. (cmurf, 17:37:17)
Meeting ended at 17:37:30 UTC.
Action Items
------------
* tpopela to work with Chrome upstream to remove atd dependency.
* Michael to move the issues
* aday to prepare guidelines.
* Neal to discuss with Wim.
Action Items, by person
-----------------------
* aday
* aday to prepare guidelines.
* **UNASSIGNED**
* tpopela to work with Chrome upstream to remove atd dependency.
* Michael to move the issues
* Neal to discuss with Wim.
People Present (lines said)
---------------------------
* cmurf (47)
* zodbot (7)
* aday (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 1 month
What is amdvlk and why do I need it?
by Matthew Miller
Over the weekend, I played Baldur's Gate 3 Early Access via steam. Awesome.
The launcher doesn't work, which is a known problem, but running bg3.exe
does.
However, with stock Fedora Workstation 33, after the intro when the menu is
supposed to load, instead it's a quilt-like pattern of colored squares (and
the mouse cursor a big block of the same).
I built and installed amdvlk-vulkan-driver from
https://github.com/GPUOpen-Drivers/AMDVLK, though, and now it works
flawlessly. Can someone who knows about this explain to me what the
situation is? How does this external driver relate to what we have in
Fedora?
Graphics card is an AMD Radeon Vega 56, btw.
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
3 years, 1 month
Fedora Workstation WG minutes, 2020-10-20
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2020-10-20)
==============================================
Meeting started by cmurf at 15:18:57 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2020-10-21/workstation...
.
Meeting summary
---------------
* Rollcall (cmurf, 15:19:12)
* present: cmurf, aday, otayor, kalev, tpopela, mcatanzaro, neal,
jens, langdon (arrived 13 minutes in) (cmurf, 15:19:13)
* regrets wg members: mattias (cmurf, 15:19:15)
* present guests: feborges (cmurf, 15:19:17)
* Approve 13 Oct minutes (cmurf, 15:19:19)
* LINK:
https://meetbot.fedoraproject.org/teams/workstation/workstation.2020-10-1...
(cmurf, 15:19:21)
* AGREED: Approved - no objections (cmurf, 15:19:23)
* Announcements (cmurf, 15:19:25)
Meeting ended at 15:19:39 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* cmurf (14)
* zodbot (7)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 1 month
Re: [Test-Announce] Fedora 33 Candidate RC-1.2 Available Now!
by Adam Williamson
On Tue, 2020-10-20 at 01:21 +0000, rawhide(a)fedoraproject.org wrote:
> According to the schedule [1], Fedora 33 Candidate RC-1.2 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/33
>
> 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_33_RC_1.2_Summary
>
> The individual test result pages are:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.2_Installation
> https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.2_Base
> https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.2_Server
> https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.2_Cloud
> https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.2_Desktop
> https://fedoraproject.org/wiki/Test_Results:Fedora_33_RC_1.2_Security_Lab
>
> All RC priority test cases for each of these test pages [2] must
> pass in order to meet the RC Release Criteria [3].
>
> Help is available on #fedora-qa on irc.freenode.net [4], or on the
> test list [5].
>
> Current Blocker and Freeze Exception bugs:
> http://qa.fedoraproject.org/blockerbugs/current
>
> [1] http://fedorapeople.org/groups/schedule/f-33/f-33-quality-tasks.html
> [2] https://fedoraproject.org/wiki/QA:Release_validation_test_plan
> [3] https://fedoraproject.org/wiki/Fedora_33_RC_Release_Criteria
> [4] irc://irc.freenode.net/fedora-qa
> [5] https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/
Just to keep everyone in the loop here: this candidate has all known
blocker fixes, *except*
https://bugzilla.redhat.com/show_bug.cgi?id=1883609 . The planned fix
for that is a new shim build that is signed with a key that will not be
revoked, but we're still waiting on that to be built and signed.
We wanted to give FESCo the option at Thursday's go/no-go of deciding
not to block on the re-signed shim any more, so we did this compose.
The plan is to do full testing on it, and if that doesn't turn up any
other blockers, we'll decide whether to ship it on Thursday. So if
folks can please try to help get complete test results on this
candidate, that'd be great.
Thanks very much!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
3 years, 1 month
