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
4 months, 3 weeks
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
pipewire -- firefox keeps getting lost
by Matthew Miller
Sooo, on F34 branched, I am now haveing a problem where periodically (not
narrowed down when), Firefox stops making noise. This is my new desktop
system so I'm not doing anything super complicated, but it has built-in Navi
10 HDMI audio, which I'm not using, and a CM106-like device, which I am
(because it has 4.0 surround).
In the GNOME Settings, CM106-like is set as the output. But when I run
pavucontrol, I see that Firefox has decided to switch to the Navi 10 audio.
It looks like I can go to Configuration and turn off the things I don't
need... but is it normal that I should have to do this? Shouldn't picking an
Output Device in Settings mean "use this for all of the things"?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
2 years
Here's something to be proud of!
by Matthew Miller
😀
Neal pointed this video out to me... https://www.youtube.com/watch?v=xNcYSMOGtEQ
Lots of good stuff, and nice to see how everyone's work here is really
paying off in perception wins in the Linux enthusiast world and social media
spaces. You all rock and should be super-proud of this! Thanks everyone!
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
2 years, 1 month
Fedora Workstation WG minutes, 2021-02-16
by Chris Murphy
==============================================
#fedora-meeting-2: Workstation WG (2021-02-16)
==============================================
Meeting started by cmurf at 06:21:31 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-02-17/workstation...
.
Meeting summary
---------------
* Rollcall (cmurf, 06:21:50)
* present: Allan, Chris, Jens, Kalev, Langdon, Michael, Matthias,
Neal, Tomas (cmurf, 06:21:51)
* regrets: (cmurf, 06:21:53)
* present guests: (cmurf, 06:21:55)
* Approval of Feb 9 minutes (cmurf, 06:21:57)
* LINK:
https://meetbot.fedoraproject.org/fedora-meeting-2/2021-02-11/workstation...
(cmurf, 06:21:59)
* AGREED: no objections (cmurf, 06:22:01)
* Announcements, follow-ups, status reports (cmurf, 06:22:03)
* Neal has Fedora Btrfs talk at DevConf.cz at 11:30am EST on Thursday
(2/18): (cmurf, 06:22:05)
* LINK:
https://devconfcz2021.sched.com/event/gmLp/btrfs-the-butter-of-fedora
(cmurf, 06:22:07)
* Allan has made a mockup to fix recommending proprietary software
(cmurf, 06:22:09)
* LINK: https://pagure.io/fedora-workstation/issue/203#comment-714868
(cmurf, 06:22:11)
* Guidance what to do with vte copy paste regression (cmurf, 06:22:15)
* LINK: https://pagure.io/fedora-workstation/issue/216 (cmurf,
06:22:17)
* AGREED: Revert the commit that causes this regression (+8, 1, -0)
(cmurf, 06:22:21)
* ACTION: Chris to file a bug about this to get it into release notes
(cmurf, 06:22:23)
* Updated activities overview design for GNOME 40 / F34 (cmurf,
06:22:25)
* LINK: https://pagure.io/fedora-workstation/issue/210 (cmurf,
06:22:27)
* GNOME 40 Beta tarballs are being made this week, will land into
Fedora 34 and Rawhide by the end of this week (cmurf, 06:22:29)
* Allan will make a Fedora Magazine article about the GNOME 40 stuff
after his upstream GNOME blogging stuff is done (cmurf, 06:22:31)
* Broadcom wireless (cmurf, 06:22:33)
* LINK: https://pagure.io/fedora-workstation/issue/116 (cmurf,
06:22:35)
* Broadcom firmware is the only remaining unsolved hardware issue
(cmurf, 06:22:37)
* RPM Fusion b43-firmware spec seems to have standard firmware license
tag? (cmurf, 06:22:39)
* LINK:
https://pkgs.rpmfusion.org/cgit/nonfree/b43-firmware.git/tree/b43-firmwar...
(cmurf, 06:22:41)
* ACTION: Matthias will reach out to Christian Schaller and Hans De
Geode on this (cmurf, 06:22:43)
* Open Floor (cmurf, 06:22:45)
* DevConf.cz is this weekend (2/18-2/20) (cmurf, 06:22:47)
* LINK: https://hopin.com/events/devconf-cz-2021 (cmurf, 06:22:49)
Meeting ended at 06:23:12 UTC.
Action Items
------------
* Chris to file a bug about this to get it into release notes
* Matthias will reach out to Christian Schaller and Hans De Geode on
this
Action Items, by person
-----------------------
* **UNASSIGNED**
* Chris to file a bug about this to get it into release notes
* Matthias will reach out to Christian Schaller and Hans De Geode on
this
People Present (lines said)
---------------------------
* cmurf (35)
* zodbot (7)
* mcatanzaro (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
2 years, 1 month
GNOME terminal limits select-all to what's visible
by Chris Murphy
As it turns out there's a bug where copying a large amount of selected
text can cause Terminal to crash. The work around, which I'm
experiencing in Rawhide, is worse than the bug: select-all is limited
to just the immediately visible text.
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/288#note_1015588
Any ideas on a work around for the work around? I don't really want to
have to run script all the time just because I might want to extract a
bunch of text, and then have to deal with ensuing encoding problems. I
also don't want to have to track down a replacement terminal
application either. So far my work around has been to just not fight
this and reboot Fedora 33 where the problem doesn't happen.
--
Chris Murphy
2 years, 1 month
