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
11 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
1 year, 7 months
services impact on startup times
by Chris Murphy
Hi,
These are based on Fedora-Workstation-Live-x86_64-33-20200828.n.0.iso
in a VM. The numbers are different on bare metal but correlate.
The only standout is rngd.service. That's a pretty big single hit,
percentage wise. And I don't know if we even need it anymore. Among
the rest, perhaps atd.service and crond.service could be disabled by
default on new installations, in favor of systemd timers.
Startup finished in 1.320s (kernel) + 1.344s (initrd) + 7.727s
(userspace) = 10.392s
disable atd.service
Startup finished in 1.308s (kernel) + 1.310s (initrd) + 7.557s
(userspace) = 10.176s
disable dbxtool.service
Startup finished in 1.302s (kernel) + 1.291s (initrd) + 7.527s
(userspace) = 10.120s
disable import-state.service
Startup finished in 1.308s (kernel) + 1.326s (initrd) + 7.410s
(userspace) = 10.044s
disable iscsi.service
Startup finished in 1.316s (kernel) + 1.303s (initrd) + 7.177s
(userspace) = 9.797s
disable libvirtd.service
Startup finished in 1.316s (kernel) + 1.266s (initrd) + 6.779s
(userspace) = 9.361s
disable lvm2-monitor.service
Startup finished in 1.315s (kernel) + 1.323s (initrd) + 6.750s
(userspace) = 9.389s
disable mdmonitor.service
Startup finished in 1.316s (kernel) + 1.350s (initrd) + 6.675s
(userspace) = 9.342s
disable ModemManager.service
Startup finished in 1.270s (kernel) + 1.305s (initrd) + 7.052s
(userspace) = 9.629s
disable nfs-convert.service
Startup finished in 1.312s (kernel) + 1.343s (initrd) + 6.958s
(userspace) = 9.614s
disable rngd.service
Startup finished in 1.308s (kernel) + 1.277s (initrd) + 5.247s
(userspace) = 7.833s
disable switcheroo-control.service
Startup finished in 1.308s (kernel) + 1.334s (initrd) + 5.223s
(userspace) = 7.867s
disable vboxservice.service
Startup finished in 1.301s (kernel) + 1.302s (initrd) + 5.176s
(userspace) = 7.780s
disable crond.service
Startup finished in 1.310s (kernel) + 1.278s (initrd) + 5.076s
(userspace) = 7.665s
preset-all
Startup finished in 1.316s (kernel) + 1.312s (initrd) + 7.869s
(userspace) = 10.498s ##stopwatch 11.35
disable atd.service crond.service iscsi.service rngd.service vboxservice.service
Startup finished in 1.305s (kernel) + 1.294s (initrd) + 5.505s
(userspace) = 8.105s ##stopwatch 8.89
All of these times are based on 'systemd-analyze'. The stopwatch
method is less precise but still demonstrates the difference is real.
It may not be a big enough deal to do anything about it this cycle,
but could be something to look at for the next. Maybe more
opportunities are available.
--
Chris Murphy
3 years
F33 and GNOME megaupdate planning
by Kalev Lember
Hi all,
Fedora 33 went into Beta freeze yesterday so we need to do a bit of
planning how we handle GNOME megaupdates during that time. This is how
my plan looks like:
GNOME 3.37.91 was released during this weekend. I was keeping an eye on
the modules and built everything as they were released upstream, so we
went into the Beta freeze fully up to date (with the exception of
gnome-terminal and vte291 which are still at 3.36.x versions and need
maintainer attention due to a large number of downstream patches).
The next GNOME release is .92 in two weeks. At that point, we are deep
into the Beta freeze in Fedora land and don't have much schedule room
left. I think it's best to not ask for a freeze break to land .92 at
that point.
After that comes the .0 release just one week after .92.
My plan is to collect all the GNOME updates that are released in that
time and put together a megaupdate in Bodhi for .92. If something urgent
comes up during that time (something that warrants a freeze break) then
this should go to Bodhi separately, so that we can pull those individual
fixes through the Beta freeze as needed. Anything else I think it's best
to wait for the .92 megaupdate.
The .92 megaupdate is likely never going to go stable (as we are going
to be in freeze at that point) and is likely just going to get replaced
by .0 megaupdate a week later.
We also have a f33-gnome side tag in koji now. If you are helping with
builds, please use the side tag for any builds that you want to be part
of the megaupdates.
(I've cross-posted this to both the desktop@ and devel@ mailing lists.)
--
Kalev
3 years, 1 month
Re: Proposal to Add: Log In/Out Blocker Criteria
by Kamil Paral
On Wed, Aug 12, 2020 at 4:25 PM Kamil Paral <kparal(a)redhat.com> wrote:
> I'd accept the criterion as proposed (because we need it now), and do the
> reorganization later (possibly when this cycle is over and we have more
> time to bikeshed about best criterion layout). I'm fine with either adding
> to the existing criterion (mine version) or creating a standalone criterion
> (Geoff's version), just note that the standalone version would still need
> to get tweaked (remove "multiple user accounts", etc).
>
In accordance with the discussion during the last QA meeting, I've put my
proposed changes live:
https://fedoraproject.org/w/index.php?title=Fedora_33_Beta_Release_Criter...
3 years, 1 month
Fedora Workstation WG minutes, 2020-08-25
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2020-08-25)
==============================================
Meeting started by cmurf at 04:36:56 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2020-08-26/workstation...
.
Meeting summary
---------------
* Rollcall (cmurf, 04:37:25)
* present wg members: cmurf, tpopela, aday, mclasen, kalev, neal,
mcatanzaro, langdon (cmurf, 04:37:27)
* regrets wg members: petersen (cmurf, 04:37:29)
* present guests: (cmurf, 04:37:31)
* Approval of 17 Aug minutes (cmurf, 04:37:33)
* LINK:
https://meetbot.fedoraproject.org/teams/workstation/workstation.2020-08-1...
(cmurf, 04:37:35)
* ACTION: Langdon to provide Chris with the amendment, then we'll
re-approve (cmurf, 04:37:45)
* Announcements (cmurf, 04:37:47)
* Today is beta freeze (cmurf, 04:37:49)
* Follow-ups & Status reports (cmurf, 04:37:51)
* Workstation F33 image is still a bit oversize (cmurf, 04:37:53)
* kalev has submitted a PR to make gnome-shell non-removable (cmurf,
04:37:55)
* GNOME upstream release happened on August 22 (beta 2?). Kalev is
turning the wheels to get the updates in. (cmurf, 04:37:57)
* Meta issue: pre-installed programs+apps for F33 (cmurf, 04:37:59)
* Make a small core of packages non-removable with DNF (cmurf,
04:38:03)
* LINK: https://pagure.io/fedora-workstation/issue/165 (cmurf,
04:38:05)
* Remove Photos and Rhythmbox from the default apps (cmurf, 04:38:07)
* LINK: https://pagure.io/fedora-workstation/issue/164 (cmurf,
04:38:09)
* AGREED: We'll wait to do anything with Photos - Allan to speak to
Debarshi about the change first (cmurf, 04:38:17)
* Remove Boxes from default install (cmurf, 04:38:19)
* LINK: https://pagure.io/fedora-workstation/issue/179 (cmurf,
04:38:21)
* AGREED: Deferred until F34 (cmurf, 04:38:47)
* ACTION: : Chris to talk to Daniel about networking problem on live
image. (cmurf, 04:38:55)
* ACTION: : Chris to talk to Mark Pearson about Lenovo's needs for
default apps. (cmurf, 04:38:57)
* Make a small core of packages non-removable with DNF (cmurf,
04:39:01)
* LINK: https://pagure.io/fedora-workstation/issue/165 (cmurf,
04:39:03)
* Making gnome-shell non-removable is in-progress (cmurf, 04:39:05)
* ACTION: Neal to talk to bootloader team to make grub nonremovable
(cmurf, 04:39:07)
* Open Floor (cmurf, 04:39:09)
Meeting ended at 04:39:25 UTC.
Action Items
------------
* Langdon to provide Chris with the amendment, then we'll re-approve
* : Chris to talk to Daniel about networking problem on live image.
* : Chris to talk to Mark Pearson about Lenovo's needs for default apps.
* Neal to talk to bootloader team to make grub nonremovable
Action Items, by person
-----------------------
* **UNASSIGNED**
* Langdon to provide Chris with the amendment, then we'll re-approve
* : Chris to talk to Daniel about networking problem on live image.
* : Chris to talk to Mark Pearson about Lenovo's needs for default
apps.
* Neal to talk to bootloader team to make grub nonremovable
People Present (lines said)
---------------------------
* cmurf (57)
* zodbot (7)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 1 month
