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
Fedora Workstation WG minutes, 2021-10-26
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2021-10-26)
==============================================
Meeting started by brainycmurf at 18:19:17 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-10-26/workstation...
.
Meeting summary
---------------
* Rollcall (brainycmurf, 18:19:29)
* present: Neal, Matthias, Allan, Chris, Michael, Kalev, Jens, Tomas,
Owen (brainycmurf, 18:19:29)
* regrets: (brainycmurf, 18:19:29)
* absent: Langdon (we should reach out to see if he's still planning
on coming back) (brainycmurf, 18:19:29)
* present guests: Zac (brainycmurf, 18:19:29)
* DST ends somewhere next week. Europeans will be later (or earlier)
next week (brainycmurf, 18:19:30)
* Approval of October 19 minutes (brainycmurf, 18:19:32)
* LINK:
https://meetbot.fedoraproject.org/teams/workstation/workstation.2021-10-1...
(brainycmurf, 18:19:34)
* Announcements, follow-ups, status reports (brainycmurf, 18:19:38)
* Allan will do a 30 minute F35 workstation status update at the F35
release party, November 12/13 (brainycmurf, 18:19:44)
* LINK:
https://hopin.com/events/fedora-linux-35-release-party/registration
(brainycmurf, 18:19:47)
* State of Fedora Workstation 35 under freeze (brainycmurf, 18:19:49)
* LINK:
https://qa.fedoraproject.org/blockerbugs/milestone/35/final/buglist
(brainycmurf, 18:19:51)
* LINK: https://bodhi.fedoraproject.org/updates/FEDORA-2021-81dea304dd
(brainycmurf, 18:20:13)
* Video review on GNOME UX for new users indicates UX issues
(brainycmurf, 18:20:20)
* LINK: https://pagure.io/fedora-workstation/issue/247 (brainycmurf,
18:20:22)
* Change gedit for gnome-text-editor in the default install
(brainycmurf, 18:20:33)
* LINK: https://pagure.io/fedora-workstation/issue/248 (brainycmurf,
18:20:35)
* Open Floor (brainycmurf, 18:20:43)
Meeting ended at 18:21:15 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* brainycmurf (43)
* zodbot (7)
* : (0)
* Neal (0)
Generated by `MeetBot`_ 0.3
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 11 months
super-high load on video calls
by Matthew Miller
This is on my X1 Carbon, F35 beta but it was also happening with F34.
Wayland. top -b from Firefox followed by Chrome. This is with only a few
tabs open and one Google Meet video call.
I think this is the same problem we were having with people's audio on Nest.
In Firefox in particular, when the load is that high, the audio totally
breaks up. Chrome also drives the CPU and load average up but audio stays
smooth.
In Firefox, I found the advice to change gfx.webrender.all to true, and I
thought at first that helped, but it clearly isn't.
----
top - 11:04:03 up 12 days, 19 min, 2 users, load average: 12.10, 6.24, 3.14
Tasks: 443 total, 4 running, 439 sleeping, 0 stopped, 0 zombie
%Cpu0 : 71.4/28.6 100[ ] %Cpu1 : 70.4/22.2 93[ ]
%Cpu2 : 66.7/23.3 90[ ] %Cpu3 : 70.4/22.2 93[ ]
%Cpu4 : 73.1/23.1 96[ ] %Cpu5 : 80.8/15.4 96[ ]
%Cpu6 : 71.4/28.6 100[ ] %Cpu7 : 82.8/13.8 97[ ]
GiB Mem : 15.4 total, 0.2 free, 9.0 used, 6.2 buff/cache
GiB Swap: 8.0 total, 4.5 free, 3.5 used. 2.9 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1092576 mattdm 20 0 9947.5m 926.0m 153.4m R 256.5 5.9 17:01.67 /usr/lib64/firefox/firefox -contentproc -childID 11 -is+
1091738 mattdm 20 0 7015.5m 874.0m 333.8m R 217.4 5.5 420:28.70 /usr/lib64/firefox/firefox
1091986 mattdm 20 0 15.6g 753.8m 79.3m R 69.6 4.8 200:07.41 /usr/lib64/firefox/firefox -contentproc -childID 6 -isF+
428142 mattdm 20 0 6585.8m 414.3m 213.0m S 30.4 2.6 228:51.23 /usr/bin/gnome-shell
1091846 mattdm 20 0 213.2m 27.3m 24.0m S 17.4 0.2 18:06.09 /usr/lib64/firefox/firefox -contentproc -parentBuildID +
----
top - 11:06:43 up 12 days, 22 min, 2 users, load average: 16.23, 10.20, 5.13
Tasks: 478 total, 10 running, 468 sleeping, 0 stopped, 0 zombie
%Cpu0 : 76.6/19.6 96[ ] %Cpu1 : 82.6/14.7 97[ ]
%Cpu2 : 80.9/14.5 95[ ] %Cpu3 : 73.8/23.4 97[ ]
%Cpu4 : 76.6/19.6 96[ ] %Cpu5 : 77.6/19.6 97[ ]
%Cpu6 : 93.6/6.4 100[ ] %Cpu7 : 68.2/27.3 95[ ]
GiB Mem : 15.4 total, 0.2 free, 9.3 used, 6.0 buff/cache
GiB Swap: 8.0 total, 4.5 free, 3.5 used. 2.5 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1182454 mattdm 20 0 70.8g 405.4m 135.7m R 282.7 2.6 1:40.82 /opt/google/chrome/chrome --type=renderer --enable-c+
1181925 mattdm 20 0 6.2m 1.4m 1.2m R 93.6 0.0 1:29.73 /usr/libexec/cgroupify app-gnome-google\x2dchrome-11+
1091738 mattdm 20 0 6417.2m 799.5m 317.4m R 59.1 5.1 423:32.97 /usr/lib64/firefox/firefox
428142 mattdm 20 0 6496.0m 409.7m 203.6m S 40.9 2.6 229:41.68 /usr/bin/gnome-shell
1181981 mattdm 20 0 16.8g 142.1m 99.0m R 38.2 0.9 0:15.39 /opt/google/chrome/chrome --type=gpu-process --field+
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
1 year, 11 months
Fedora 35 status and testing needed
by Adam Williamson
Hi folks! Just wanted to give an update on Fedora 35 status and beg for
testing :D
We are now down to either one or two blocker bugs. They are in quite
specific areas so the fixes will not be hugely impactful to anything
else. I'm hoping to be able to run an RC compose later today (Tuesday).
However, we're also only 2 days from go/no-go.
Given this, it'd be super helpful if people could help get the
validation tests run on the current nominated nightly compose. We don't
need to wait for an RC to run most tests; for the more complicated or
trickier tests, we can run them now against a nightly and the results
can be counted so long as nothing relevant changes in the RC.
I've just manually nominated the most recent compose (20211018.n.0) for
testing; it won't have the fixes currently in updates-testing (mainly
for plasma-discover), so take that into account. You can see the
summary page (which shows results from all individual pages) here:
https://fedoraproject.org/wiki/Test_Results:Current_Summary
you can enter results by editing individual sections from that page
(the wiki will automagically edit the correct individual page), or by
using the relval tool - just 'dnf install relval' then 'relval report-
results'.
You can look for tests that really need to be run here:
https://openqa.fedoraproject.org/testcase_stats/35/
each of the pages there shows a sort of 'over time view' of the test
cases of that type, showing when it was most recently run and a little
chart view that illustrates which composes the test has been run on and
what the results were (green for pass, orange for warn, red for
failed). Look out for tests that have release level 'Basic', 'Beta' or
'Final' and which have not been run recently or at all; these are the
ones to focus on. For instance, at
https://openqa.fedoraproject.org/testcase_stats/35/Desktop.html we can
see that several of the desktop tests have not yet been run on aarch64;
it'd be great if anyone with an aarch64 system capable of running
Workstation could run those tests and add the results.
Thanks everyone!
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
1 year, 11 months
Fedora Workstation WG minutes, 2021-10-19
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2021-10-19)
==============================================
Meeting started by brainycmurf at 16:23:11 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-10-19/workstation...
.
Meeting summary
---------------
* Rollcall (brainycmurf, 16:23:28)
* present: Tom, Chris, Michael, Matthias, Neal, Owen, Allan, Kalev
(brainycmurf, 16:23:29)
* regrets: (brainycmurf, 16:23:29)
* present guests: fborges (brainycmurf, 16:23:29)
* Approval of October 12 minutes (brainycmurf, 16:23:29)
* LINK:
https://meetbot.fedoraproject.org/teams/workstation/workstation.2021-10-1...
(brainycmurf, 16:23:29)
* AGREED: No objections - agreed (brainycmurf, 16:23:31)
* Announcements, follow-ups, status reports (brainycmurf, 16:23:33)
* Allan: New working group landing page on docs site
(https://docs.fedoraproject.org/en-US/workstation-working-group/ )
(brainycmurf, 16:23:35)
* State of Fedora Workstation 35 under freeze (brainycmurf, 16:23:38)
* LINK:
https://qa.fedoraproject.org/blockerbugs/milestone/35/final/buglist
(brainycmurf, 16:23:40)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2001837 still an
issue. Have had multiple rounds of fixes and testing. Owen still
helping out here, but thinks we have an initial working solution.
(brainycmurf, 16:23:42)
* Fedora Workstation release schedule / check list (brainycmurf,
16:23:47)
* LINK: https://pagure.io/fedora-workstation/issue/250 (brainycmurf,
16:23:51)
* Please check over the list and suggest necessary additions (Tomas
will ask Adam Williamson to review) (brainycmurf, 16:23:53)
* Tomas asks how it should be tracked: file issues in pagure, shared
google calendar, Fedora schedule page. Last option is likely best,
but how do we track the actionable? Neal says that could use
milestones in Pagure, possibly, but we should see how the calendar
looks first so we have a concrete idea. Tomas - should be
responsibility of workstation chair. (brainycmurf, 16:23:56)
* Fedora 36 chair (brainycmurf, 16:24:01)
* Allan volunteers - may need to delegate topics where he has a
contrarian view or that are highly technical. (brainycmurf,
16:24:03)
* AGREED: Allan will be the chair for the Fedora 36 cycle
(brainycmurf, 16:24:06)
* AGREED: Chris will be the vice/backup chair for the cycle
(brainycmurf, 16:24:08)
* Supporting status notifiers in Fedora Workstation by default
(brainycmurf, 16:24:10)
* LINK: https://pagure.io/fedora-workstation/issue/246 (brainycmurf,
16:24:12)
* Hans de Goede (co-maintainer of current extensions) feels it would
be suitable for inclusion as is (brainycmurf, 16:24:14)
* Allan has been doing research - trying out different implementations
on Linux, looking what Mac/Windows do. Will talk to peers at
Canonical, etc. Asks about whether this is a) something that we are
including purely for compatibility with other platforms b) something
that we want to recommend in other circumstances. (brainycmurf,
16:24:17)
* question raised whether we should enable extension by default now in
rawhide - Allan would like to have some time for design and
discussion - and does not thing that we should enable it if it has
xembed support that is broken for apps like dropbox and hexchat.
(Thought is that probably if we don't have xembed enabled, dropbox
will work via app-indicators.) (brainycmurf, 16:24:23)
* Neal suggests that if you install the RPM, it should be turned on by
default without an additional step. people were generally OK with
this. (brainycmurf, 16:24:28)
* ACTION: Neal will look into what that involves (brainycmurf,
16:24:31)
Meeting ended at 16:26:56 UTC.
Action Items
------------
* Neal will look into what that involves
Action Items, by person
-----------------------
* Neal
* Neal will look into what that involves
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* brainycmurf (32)
* zodbot (7)
* : (0)
* Neal (0)
Generated by `MeetBot`_ 0.3
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 11 months
