Installing ffmeg-free degrades firefox video support
by Otto Urpelainen
I have discovered that installing the ffmpeg-free package degrades
Firefox video support. Without any kind of ffmpeg installed, Firefox is
able to play all the videos I want to watch. Installing RPM Fusion's
ffmpeg package does not change this. But, installing ffmpeg-free from
Fedora repositories causes some videos not to play.
This is unexpected, because one would expect that installing any variant
of ffmpeg would improve video support, not degrade it. My hypothesis is
that Firefox prefers ffmpeg over openh264, but is not careful enough to
check if the ffmpeg it detects actually supports h264.
As a workaround, I can set media.ffmpeg.enabled in Firefox's
about:config to false. Then all videos play again, even with ffmpeg-free
installed.
Here is an example video from Youtube that can be used as a reproducer:
https://www.youtube.com/watch?v=ETsAH96BsBg
It seems clear that there is a bug somewhere, but I cannot decide,
where, hence this post to devel. Should Fedora's Firefox actually have
media.ffmpeg.enabled set to false by default, because Fedora's variant
of ffmpeg has this problem? Should upstream Firefox be smarted about
which decoder library it attempts to use? Or should ffmpeg-free package
do something to avoid this from happening. Any opinions are welcome!
2 years
Re: VirtualBox and HOST kernel-5.17.12 weirdness
by Alexander G. M. Smith
Ian Laurie wrote on Friday, 3 June 2022 at 11:17 p.m.:
> Is anyone else seeing crashes and other strange events in VirtualBox
> 6.1.34 (from RPMFusion) with Linux guests when the Linux host is running
> Fedora 36 with kernel-5.17.12?
Same thing here. Host is Fedora 35 with kernel 5.17.12, using
VirtualBox 6.1.34.
Lots of odd things like "curl" bombing out, dnf upgrades complaining
they can't write somewhere. Restarting nginx+passenger only works a
couple of times, then it stops responding. It's very repeatable too.
Same snapshot works fine with kernel 5.17.11.
The weird thing is that it works on other CPUs, an AMD Athlon X2 and an
Intel 10th generation i5-10500H. Just my IvyBridge Intel i7-4820K has
the problem. I did try the kernel boot parameter mitigations=off, in
case the Spectre or other workarounds were wrong for IvyBridge, but it
still didn't work.
You can run 5.17.12 inside the guest without problems. Your host just
needs to be 5.17.11.
So, what CPUs are other people with problems using?
- Alex
2 years
Tip for Reporting Spam on Mailing Lists
by Jeffrey Ollie
Do not reply to or forward spam emails back to the mailing list. You just
became part of the problem and many/most spam scanning services now
consider YOUR email to be spam. Gmail in particular makes it very difficult
to manage the spam status of individual emails (seems like you can only
report/unreport whole conversations).
--
Jeff Ollie
The majestik møøse is one of the mäni interesting furry animals in Sweden.
2 years
PSA: openQA failures in tests using Firefox
by Adam Williamson
Hi, folks. You may be noticing more failures than usual in openQA tests
that use Firefox. This is caused by a rather vexing combination of
Firefox wanting to show "helpful" popups on startup:
https://bugzilla.mozilla.org/show_bug.cgi?id=1703903
and what I think is some kind of odd regression in Firefox 100 which
makes typing into some text entry boxes in the Cockpit and FreeIPA web
UIs not work reliably (this affects realmd_join_cockpit and
upgrade_realmd_client).
I *think* I've figured out a way to deal with the popups for now (touch
wood, testing it right now). I'm still kinda stuck on the typing
problem. It's very late here now and I'll look into it more tomorrow. I
do apologize if an update is blocked on such a failure, I've been
restarting failed tests constantly all day but they keep hitting these
failure modes. I'll do my best to have it sorted by tomorrow one way or
another, and if I can't, I'll adjust the greenwave policy to
temporarily disable gating on the problematic tests.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
2 years
Fedora CoreOS Meeting Minutes 2022-06-15
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-06-15/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2022-06-15/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2022-06-15/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:30:11 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-06-15/fedora_core...
.
Meeting summary
---------------
* roll call (dustymabe, 16:30:18)
* Action items from last meeting (dustymabe, 16:36:26)
* jlebon has scheduled a meeting to discuss Fedora CoreOS layering use
cases (jlebon, 16:37:13)
* dustymabe scheduled met with jlebon, lucab, saqali this morning to
narrow down changes to discuss (dustymabe, 16:38:26)
* ACTION: cverna to open ticket for FCOS as an edition and update
(dustymabe, 16:39:24)
* New Package Request: qemu-user-static (dustymabe, 16:39:52)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1088
(dustymabe, 16:40:03)
* AGREED: For now we will include the qemu-user-static-x86 package on
non x86_64 FCOS images to allow "out of the box" access to the large
inventory of containers only built for x86_64. We may revisit this
in the future once CoreOS layering is more mature or if there comes
a time when containers for other architectures are as ubiquitous.
(dustymabe, 17:08:29)
* tracker: Fedora 37 changes considerations (dustymabe, 17:09:15)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1222
(dustymabe, 17:09:19)
* open floor (dustymabe, 17:34:59)
* ACTION: jlebon to open investigation tickets for the IMA/FIDO
changes (dustymabe, 17:38:27)
Meeting ended at 17:40:01 UTC.
Action Items
------------
* cverna to open ticket for FCOS as an edition and update
* jlebon to open investigation tickets for the IMA/FIDO changes
Action Items, by person
-----------------------
* jlebon
* jlebon to open investigation tickets for the IMA/FIDO changes
* **UNASSIGNED**
* cverna to open ticket for FCOS as an edition and update
People Present (lines said)
---------------------------
* dustymabe (130)
* jlebon (51)
* zodbot (22)
* miabbott (12)
* jdoss (6)
* walters (5)
* jmarrero (4)
* ravanelli (3)
* lorbus (2)
* saqali (1)
* aaradhak[m] (1)
* x3mboy (1)
* mnguyen (1)
Generated by `MeetBot`_ 0.4
.. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions
2 years
F37 proposal: Fallback Hostname (System-Wide Change proposal)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/FallbackHostname
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
== Summary ==
This proposal is for the fallback hostname for server like variants of
Fedora to use `localhost` as the fallback hostname.
== Owner ==
* Name: [[User:dustymabe| Dusty Mabe]] (Fedora CoreOS)
* Email: dustymabe(a)redhat.com
* Name: [[User:davdunc| David Duncan]] (Fedora Cloud)
* Email: davdunc(a)gmail.com
* Name: [[User:pwhalen| Paul Whalen]] (Fedora IoT)
* Email: pwhalen(a)redhat.com
* Name: [[User:salimma| Michel Alexandre Salim]] (Fedora Server)
* Email: michel(a)michel-slm.name
* Name: [[User:ngompa| Neal Gompa]] (Fedora Workstation/KDE)
* Email: ngompa13(a)gmail.com
== Detailed Description ==
In Fedora 33 the default fallback hostname was changed from
`localhost` to `fedora` for Fedora Linux instances that didn't get the
hostname set in any other way (i.e. it's the fallback if it's not set
anywhere else). This change came in a systemd update and was never
proposed as a change in Fedora itself.
The enablement upstream was in
https://github.com/systemd/systemd/pull/5175 and the BZ requesting the
change in Fedora was
https://bugzilla.redhat.com/show_bug.cgi?id=1392925. The original
reasoning being that `localhost` is a bad hostname for auto-discovery
protocols (think `avahi`) that are useful for more desktop
applications.
Unfortunately, this caused issues because setting the hostname via
reverse DNS lookups (via NetworkManager) stopped working along with
breaking third party tools that set the hostname. The NetworkManager
problem was subsequently fixed, but it still remains that a lot of
third party software will check to see if an instance's hostname is
"unset" by checking the current hostname against the string
"localhost". Additionally it appears this change will never be picked
up by Fedora's primary downstream in CentOS/RHEL (see
https://src.fedoraproject.org/rpms/systemd/c/13d1341b108a24d13f5922054307...).
The proposal here is to enable variants of Fedora Linux to configure
their default/fallback hostname and to set the default for variants
targetting servers (Cloud, CoreOS, IoT, Server) to `localhost`.
== Benefit to Fedora ==
With this change Fedora's server-like variants will become more
compatible with third party tools that expect a hostname of
`localhost` means the system is unconfigured. It also will mean system
administrator's will see `localhost` and assume the hostname is
unconfigured.
== Scope ==
* Proposal owners:
The feature owners will update the systemd compile time switch for
fallback hostname back to `localhost`. The `fedora-release` package
will be updated such that the Fedora Server, IoT, Cloud, and CoreOS
editions will use `localhost` as the fallback hostname. All other
variants of Fedora (the ones that target desktop/laptop uses) will
default to `fedora` as the fallback hostname.
The proposed changes are a relatively small amount of a work.
* Other developers:
For any variants other than Cloud, CoreOS, IoT, and Server they will
see no change. Work with QA to verify other editions continue to have
a fallback hostname of `fedora`.
For Cloud, CoreOS, IoT, and Server the default fallback hostname would
be `localhost`.
* Release engineering: No changes needed for release engineering.
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives: N/A
== Upgrade/compatibility impact ==
There will be NO upgrade impact to systems where:
* An admin statically set the hostname
* A hostname was provided to a system via DHCP
* A hostname was found for a system via reverse DNS lookup
In the case where none of the above are true for a system (i.e. a
fallback hostname will be used) the following upgrade impact will be
observed:
* Fedora Cloud: No impact. A booted Fedora Cloud 36 instance has
`/etc/hostname` written by `cloud-init` on first boot.
* Fedora CoreOS: No impact. Already using `localhost` as fallback hostname.
* Fedora IoT: Some impact. The fallback hostname will change from
`fedora` to `localhost` after upgrade.
* Fedora Server: Some impact. The fallback hostname will change from
`fedora` to `localhost` after upgrade.
For Fedora IoT and Fedora Server we will announce the change and
encourage users to statically set a hostname for their machines if
they don't want the change in behavior.
== How To Test ==
Boot an instance of the flavor of Fedora you are testing in an
environment where there is no DHCP hostname provided and no answer to
a reverse DNS lookup for the instance IP. Run `hostnamectl hostname`
and verify that it matches expectation. For Fedora Cloud, CoreOS, IoT,
Server it should be `localhost`. For all others it should be `fedora`.
== User Experience ==
For Cloud, CoreOS, IoT and Server users will notice intances now
default to `localhost` if a hostname is not provided to an instance by
any other means. For all other variants of Fedora there will be no
change.
== Dependencies ==
There will be changes to the `systemd` and `fedora-release` packages
for this change.
== Contingency Plan ==
* Contingency mechanism: Revert the pull requests to the `systemd` and
`fedora-release` packages.
* Contingency deadline: Final Freeze
* Blocks release? Yes
== Documentation ==
The fallback hostname has now changed to `localhost` for the Cloud,
CoreOS, IoT, and Server variants of Fedora.
== Release Notes ==
The fallback hostname has now changed for the Cloud, CoreOS, IoT, and
Server editions of Fedora to `localhost`. The fallback hostname is the
hostname that is set if the hostname cannot be determined by any other
mechanism (statically set, DHCP, or reverse DNS). This change was done
in order to conform to the common expectation that a hostname of
`localhost` on a system means the hostname is "unset".
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
2 years
