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, 7 months
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
2 years, 3 months
Fedora Workstation WG minutes, 2021-05-25
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2021-05-25)
==============================================
Meeting started by cmurf at 19:41:24 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-05-26/workstation...
.
Meeting summary
---------------
* Rollcall (cmurf, 19:41:35)
* present: Allan, Michael, Neal, Matthias, Kalev, Jens (secr.),
Chris, Langdon, Tomas, Owen (cmurf, 19:41:37)
* regrets: (cmurf, 19:41:39)
* present guests: Luna(bittin), Knurpht, feborges, James Cassell
(cmurf, 19:41:41)
* Approval of May 11 minutes (cmurf, 19:41:43)
* LINK:
https://meetbot.fedoraproject.org/teams/workstation/workstation.2021-05-1...
(cmurf, 19:41:45)
* AGREED: approved, no objections (cmurf, 19:41:49)
* Announcements, follow-ups, status reports (cmurf, 19:41:51)
* Add selected Flathub apps to the third-party repos (cmurf, 19:42:07)
* LINK: https://pagure.io/fedora-workstation/issue/108 (cmurf,
19:42:09)
* Broadcom wireless (cmurf, 19:42:19)
* LINK: https://pagure.io/fedora-workstation/issue/116 (cmurf,
19:42:21)
* Release art for GNOME Software (cmurf, 19:42:25)
* LINK: https://pagure.io/fedora-workstation/issue/230 (cmurf,
19:42:27)
* Open Floor (cmurf, 19:42:31)
Meeting ended at 19:42:40 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* cmurf (34)
* zodbot (7)
* Neal (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years
