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
Drawing glitches in virtual machine and Firefox in f35
by Milan Crha
Hi,
since I upgraded to Fedora 35 I immediately noticed drawing glitches in
a virtual machine (virt-manager) and since an update to Firefox 94.0
also there (for example when opening menus), thus I guess it has
something to do with the graphics drivers or something like that. I run
X.org under MATE and I had never any such issue before the upgrade to
f35 (I do run many virtual machines for various testing reasons, thus
I'd surely notice). I tried to record the screen, but the created video
does not exhibit the problem.
The graphics stack is kinda foggy for me, I know basically nothing
about it. I do not know where to start the investigation and what to
look for.
Any suggestion, please?
Thanks and bye,
Milan
P.S.: The hwinfo says:
47: PCI 02.0: 0300 VGA compatible controller (VGA)
[Created at pci.386]
Unique ID: _Znp.46Z08LJqVYC
SysFS ID: /devices/pci0000:00/0000:00:02.0
SysFS BusID: 0000:00:02.0
Hardware Class: graphics card
Device Name: "Onboard IGD"
Model: "Intel UHD Graphics 630 (Mobile)"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x3e9b "UHD Graphics 630 (Mobile)"
SubVendor: pci 0x1028 "Dell"
SubDevice: pci 0x0905
Driver: "i915"
Driver Modules: "i915"
Memory Range: 0xeb000000-0xebffffff (rw,non-prefetchable)
Memory Range: 0x80000000-0x8fffffff (ro,non-prefetchable)
I/O Ports: 0x4000-0x403f (rw)
Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
IRQ: 148 (249285 events)
Module Alias: "pci:v00008086d00003E9Bsv00001028sd00000905bc03sc00i00"
Driver Info #0:
Driver Status: i915 is active
Driver Activation Cmd: "modprobe i915"
Config Status: cfg=new, avail=yes, need=no, active=unknown
1 year, 10 months
Should we have rpm package policies tying extension packages to the
GNOME versions they'll work with?
by Matthew Miller
See this Ask Fedora topic: https://ask.fedoraproject.org/t/fedora-34-extensions-installed-from-dnf-d...
In short, some rpm-packaged GNOME Shell extensions don't work with the GNOME
Shell we are shipping, but this isn't expressed in the dependencies.
I looked at the package which triggered the question, and:
$ rpm -qRp gnome-shell-extension-sound-output-device-chooser-39^1.8c90ed0-1.fc35.noarch.rpm
gnome-shell-extension-common
python3
rpmlib(CaretInVersions) <= 4.15.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsZstd) <= 5.4.18-1
and
$ rpm2cpio gnome-shell-extension-sound-output-device-chooser-39^1.8c90ed0-1.fc35.noarch.rpm |cpio -i --quiet --to-stdout './usr/share/gnome-shell/extensions/*/metadata.json'|jq '."shell-version"'
[
"3.32",
"3.34",
"3.36",
"3.38",
"40"
]
Would it make sense to have an automatic dependency generator which requires
gnome-shell to be one of those versions? (Or conflicts with gnome-shell which is
_not_ those versions?)
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
1 year, 10 months
Fedora Workstation WG minutes, 2021-11-23
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2021-11-23)
==============================================
Meeting started by brainycmurf at 21:13:14 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-11-23/workstation...
.
Meeting summary
---------------
* Present members: Chris, Allan, Tomas, Michael, Neal (left early),
Jens, (brainycmurf, 21:13:31)
* Present guests: Felipe (brainycmurf, 21:13:31)
* Regrets: Kalev, Matthias (brainycmurf, 21:13:31)
* Missing: Owen, Langdon (brainycmurf, 21:13:31)
* Secretary: Jens (brainycmurf, 21:13:31)
* Actions from last week (brainycmurf, 21:13:32)
* In Repository Gnome Shell Extensions Need Some TLC (brainycmurf,
21:13:38)
* LINK: https://pagure.io/fedora-workstation/issue/254 (brainycmurf,
21:13:40)
* Automatically install the OpenH264 codec (brainycmurf, 21:13:58)
* LINK: https://pagure.io/fedora-workstation/issue/84 (brainycmurf,
21:14:00)
* Software is recommending proprietary software (brainycmurf, 21:14:08)
* LINK: https://pagure.io/fedora-workstation/issue/203 (brainycmurf,
21:14:10)
* Announcements & status updates (brainycmurf, 21:14:15)
* Last week's minutes have been posted (brainycmurf, 21:14:21)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-11-16/workstation...
(brainycmurf, 21:14:25)
Meeting ended at 21:14:35 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* brainycmurf (33)
* zodbot (7)
* Allan (0)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 10 months
Fedora Workstation WG minutes, 2021-11-16
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2021-11-16)
==============================================
Meeting started by brainycmurf at 17:42:19 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-11-16/workstation...
.
Meeting summary
---------------
* Present members: Matthias, Owen, Chris, Allan, Neal, Michael,
(brainycmurf, 17:42:50)
* Present guests: Felipe, Zac (brainycmurf, 17:42:50)
* Regrets: Jens, Tomas (brainycmurf, 17:42:50)
* Secretary: Chris (brainycmurf, 17:42:50)
* Call for F36 workstation changes (brainycmurf, 17:42:50)
* ACTION: Neal will post to desktop@ list (brainycmurf, 17:42:56)
* Improve the user feedback for OOM situations (brainycmurf, 17:42:58)
* LINK: https://pagure.io/fedora-workstation/issue/202 (brainycmurf,
17:43:00)
* LINK:
https://github.com/systemd/systemd/issues/20649#issuecomment-914401230
(brainycmurf, 17:43:04)
* 2 minute shutdown timer is too long (brainycmurf, 17:43:09)
* LINK: https://pagure.io/fedora-workstation/issue/163 (brainycmurf,
17:43:11)
* ACTION: chris will attempt to locate a PK reproducer and file a bug
(brainycmurf, 17:43:17)
* ACTION: Matthias to reach out to Zbyszek (brainycmurf, 17:43:19)
* Enable full preemption (brainycmurf, 17:43:21)
* LINK: https://pagure.io/fedora-workstation/issue/228 (brainycmurf,
17:43:23)
* LINK:
https://www.codeblueprint.co.uk/2019/12/23/linux-preemption-latency-throu...
(brainycmurf, 17:43:52)
* ACTION: chris will ask anaconda devs about how to do this so we've
got an idea (brainycmurf, 17:43:54)
* Status updates & announcements (brainycmurf, 17:43:56)
* Last week's minutes have been posted (brainycmurf, 17:44:04)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-11-02/workstation...
(brainycmurf, 17:44:06)
Meeting ended at 17:44:13 UTC.
Action Items
------------
* Neal will post to desktop@ list
* chris will attempt to locate a PK reproducer and file a bug
* Matthias to reach out to Zbyszek
* chris will ask anaconda devs about how to do this so we've got an idea
Action Items, by person
-----------------------
* **UNASSIGNED**
* Neal will post to desktop@ list
* chris will attempt to locate a PK reproducer and file a bug
* Matthias to reach out to Zbyszek
* chris will ask anaconda devs about how to do this so we've got an
idea
People Present (lines said)
---------------------------
* brainycmurf (41)
* zodbot (7)
* Allan (0)
Generated by `MeetBot`_ 0.3
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
1 year, 10 months
