Fedora-Cloud-33-20210306.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-33-20210305.0):

ID: 801763  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/801763
ID: 801770  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/801770

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] 389 DS nightly 2021-03-06 - 95% PASS

[vashirov]

https://fedorapeople.org/groups/389ds/ci/nightly/2021/03/06/report-389-ds-base-2.0.3-20210306gite9b4eb594.fc33.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora rawhide compose report: 20210305.n.1 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20210304.n.0
NEW: Fedora-Rawhide-20210305.n.1

= SUMMARY =
Added images:1
Dropped images:  4
Added packages:  38
Dropped packages:7
Upgraded packages:   202
Downgraded packages: 0

Size of added packages:  614.67 MiB
Size of dropped packages:4.86 MiB
Size of upgraded packages:   2.68 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -80.22 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20210305.n.1.iso

= DROPPED IMAGES =
Image: Comp_Neuro live x86_64
Path: Labs/x86_64/iso/Fedora-Comp_Neuro-Live-x86_64-Rawhide-20210304.n.0.iso
Image: Scientific vagrant-virtualbox x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20210304.n.0.x86_64.vagrant-virtualbox.box
Image: Design_suite live x86_64
Path: Labs/x86_64/iso/Fedora-Design_suite-Live-x86_64-Rawhide-20210304.n.0.iso
Image: Scientific vagrant-libvirt x86_64
Path: 
Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20210304.n.0.x86_64.vagrant-libvirt.box

= ADDED PACKAGES =
Package: atari800-4.2.0-2.fc35
Summary: An emulator of 8-bit Atari personal computers
RPMs:atari800
Size:2.47 MiB

Package: bdftopcf-1.1-1.fc35
Summary: Font compiler for the X server and font server
RPMs:bdftopcf
Size:158.89 KiB

Package: fonttosfnt-1.2.1-1.fc35
Summary: Tool to wrap bdf or pcf bitmap fonts in an sfnt wrapper
RPMs:fonttosfnt
Size:142.39 KiB

Package: galera-26.4.7-2.module_f35+11590+65e5d6ba
Summary: Synchronous multi-master wsrep provider (replication engine)
RPMs:galera
Size:10.03 MiB

Package: golang-github-prometheus-node-exporter-1.1.1-1.fc35
Summary: Exporter for machine metrics
RPMs:golang-github-prometheus-node-exporter 
golang-github-prometheus-node-exporter-devel
Size:20.88 MiB

Package: j4-dmenu-desktop-2.18-4.fc35
Summary: Generic menu for desktop managers
RPMs:j4-dmenu-desktop
Size:319.15 KiB

Package: lightly-0.4.1-1.fc35
Summary: A modern style for qt applications
RPMs:lightly
Size:1.88 MiB

Package: luit-1.1.1-1.fc35
Summary: Locale to UTF-8 encoding filter
RPMs:luit
Size:149.53 KiB

Package: mariadb-3:10.5.9-1.module_f35+11590+65e5d6ba
Summary: A very fast and robust SQL database server
RPMs:mariadb mariadb-backup mariadb-common mariadb-connect-engine 
mariadb-cracklib-password-check mariadb-devel mariadb-embedded 
mariadb-embedded-devel mariadb-errmsg mariadb-gssapi-server 
mariadb-oqgraph-engine mariadb-rocksdb-engine mariadb-s3-engine mariadb-server 
mariadb-server-galera mariadb-server-utils mariadb-sphinx-engine mariadb-test 
mariadb-tokudb-engine
Size:570.09 MiB

Package: mkfontscale-1.2.1-1.fc35
Summary: Tool to generate legacy X11 font system index files
RPMs:mkfontscale
Size:157.25 KiB

Package: oclock-1.0.4-1.fc35
Summary: A simple analog clock
RPMs:oclock
Size:98.07 KiB

Package: openjdk-asmtools-7.0.b10-0.1.20210122.git7eadbbf.fc35
Summary: To develop tools create proper & improper Java '.class' files
RPMs:openjdk-asmtools openjdk-asmtools-javadoc
Size:1003.60 KiB

Package: perl-SQL-Abstract-Pg-1.0-1.fc35
Summary: PostgreSQL features for SQL::Abstract
RPMs:perl-SQL-Abstract-Pg
Size:18.38 KiB

Package: python-amply-0.1.4-1.fc35
Summary: A Python package for AMPL/GMPL datafile parsing
RPMs:python3-amply
Size:33.36 KiB

Package: python-backrefs-5.0.1-5.fc35
Summary: A wrapper around re and regex that adds additional back references
RPMs:python3-backrefs python3-backrefs+extras
Size:300.03 KiB

Package: python-libcst-0.3.17-4.fc35
Summary: A concrete syntax tree with AST-like properties for Python 3
RPMs:python-libcst-doc python3-libcst
Size:2.01 MiB

Package: python-mock-ssh-server-0.8.2-2.fc35
Summary: Mock SSH server for testing purposes
RPMs:python3-mock-ssh-server
Size:30.35 KiB

Package: python-reedsolo-1.5.4-4.fc35
Summary: Pure-Python Reed Solomon encoder/decoder
RPMs:python3-reedsolo
Size:1008.20 KiB

Package: rgb-1.0.6-40.fc35
Summary: X color name database
RPMs:rgb
Size:89.29 KiB

Package: rust-case-1.0.0-1.fc35
Summary: Set of letter case string helpers
RPMs:rust-case+default-devel rust-case-devel
Size:18.53 KiB

Package: trelby-2.4.2-1.fc35
Summary: The free, multiplatform, feature-rich screenwriting program
RPMs:trelby
Size:1.50 MiB

Package: x11perf-1.6.1-1.fc35
Summary: X11 server performance test program
RPMs:x11perf
Size:393.74 KiB

Package: xbiff-1.0.4-1.fc35
Summary: Graphical notification of new e-mail
RPMs:xbiff
Size:100.43 KiB

Package: xclipboard-1.1.3-1.fc35
Summary: Utility to collect and display text selections
RPMs:xclipboard
Size:137.15 KiB

Package: xclock-1.0.9-1.fc35
Summary: The classic X Window System clock utility
RPMs:xclock
Size:190.43 KiB

Package: xconsole-1.0.7-1.

[Bug 1936048] New: perl-HTTP-Message-6.29 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1936048

Bug ID: 1936048
   Summary: perl-HTTP-Message-6.29 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-HTTP-Message
  Keywords: FutureFeature, Triaged
  Assignee: ppi...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Latest upstream release: 6.29
Current version/release in rawhide: 6.28-1.fc35
URL: http://search.cpan.org/dist/HTTP-Message/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from anitya:
https://release-monitoring.org/project/2977/


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Request to include package: coreboot

[Reon Beon via devel]

Should be fine but they suggest a git version.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Request to include package: coreboot

[Reon Beon via devel]

Preferably someone else because I haven't done packaging on Fedora (or Linux) 
for that matter. Just some minor editing of existing packages.

So I don't really think I am up for it.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: heads up: kernel-5.12-rc1 and swapfile corruption

[Chris Murphy]

On Fri, Mar 5, 2021 at 5:06 PM Kevin Kofler via devel
 wrote:
>
> Kevin Fenzi wrote:
> > Just a heads up for anyone running rawhide and using swapfiles: There's
> > some nasty corruption in 5.12-rc1. ;(
>
> Note that this corrupts not only the swapfile as hinted at in the subject,
> but also random data and/or metadata on the entire containing partition!
>
> This is explained more in detail at the given link:
> > https://lwn.net/Articles/848265/ has details.
>

If using btrfs:

sudo btrfs scrub start /
watch -n 10 sudo btrfs scrub status /#optional

That'll read every data and metadata block. Corruptions are reported
in dmesg. If there's redundancy (e.g. dup or raid1+) it'll try to
repair it from a good copy. Without a scrub, the same error detection
(and fixups if possible) happens passively as blocks are read.

-- 
Chris Murphy
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: heads up: kernel-5.12-rc1 and swapfile corruption

[Kevin Kofler via devel]

Kevin Fenzi wrote:
> Just a heads up for anyone running rawhide and using swapfiles: There's
> some nasty corruption in 5.12-rc1. ;(

Note that this corrupts not only the swapfile as hinted at in the subject, 
but also random data and/or metadata on the entire containing partition!

This is explained more in detail at the given link:
> https://lwn.net/Articles/848265/ has details.

Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[389-devel] please review: PR 4657 - remove problematic language from UI/CLI/CI

[Mark Reynolds]

https://github.com/389ds/389-ds-base/pull/4657

--

389 Directory Server Development Team
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: heads up: kernel-5.12-rc1 and swapfile corruption

[Peter Robinson]

On Fri, Mar 5, 2021 at 7:06 PM Kevin Fenzi  wrote:
>
> Just a heads up for anyone running rawhide and using swapfiles: There's
> some nasty corruption in 5.12-rc1. ;(

Note it's only for swap files, not partitions or zram/zswap, so most
default Fedora use cases should be unaffected.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Self introduction

[Kevin Fenzi]

On Fri, Mar 05, 2021 at 09:52:22PM +0300, Alex Fails wrote:

Welcome! 

You may want to adjust your email client to include a plain/text part
for this list. :) 

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

heads up: kernel-5.12-rc1 and swapfile corruption

[Kevin Fenzi]

Just a heads up for anyone running rawhide and using swapfiles: There's
some nasty corruption in 5.12-rc1. ;( 

https://lwn.net/Articles/848265/ has details. 

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Self introduction

[Alex Fails]

Hello everyone,My name is Alexey Gorgurov, and I would like to participate in the community life.I'm experienced mainly in C++, Qt, .net, python, etc., interested in Linux and have some experience in open source contributing.I like to help people with programming issues and like to spend some time in the community and hope to be helpful for Fedora Project. Thanks. Kind regards,Alexey  ___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Tom Seewald]

> Could you modify fprintd.service, to set G_MESSAGES_DEBUG=all[1] and
> then grab a log of that?

Here's what I see from systemctl status fprintd.service:

Getting authorization to perform Polkit action 
net.reactivated.fprint.device.verify
Authorization granted to AuthenTec AES2550/AES2810 to call method 
'ListEnrolledFingers' for device :1.72!
file_storage_discover_prints() for user 'tom' in '/var/lib/fprint/tom/aes2550/0'
scan_dev_storedir(): opendir("/var/lib/fprint/tom/aes2550/0") failed: Error 
opening directory “/var/lib/fprint/tom/aes2550/0”: No such file or directory
Requesting device 'AuthenTec AES2550/AES2810' authorization for method 
ListEnrolledFingers from :1.74
Getting authorization to perform Polkit action 
net.reactivated.fprint.device.setusername
Getting authorization to perform Polkit action 
net.reactivated.fprint.device.verify
Authorization granted to AuthenTec AES2550/AES2810 to call method 
'ListEnrolledFingers' for device :1.74!
file_storage_discover_prints() for user 'tom' in '/var/lib/fprint/tom/aes2550/0'
scan_dev_storedir(): opendir("/var/lib/fprint/tom/aes2550/0") failed: Error 
opening directory “/var/lib/fprint/tom/aes2550/0”: No such file or directory

It looks like "/var/lib/fprint/" is a completely empty directory on my system.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive maintainer check for jstanley

[Miro Hrončok]

On 05. 03. 21 19:03, Jon Stanley wrote:

On Fri, Mar 5, 2021 at 11:12 AM Miro Hrončok  wrote:


Hello,

there are several bugzillas wrt Python 2 usage in trac plugins maintained by
user jstanley with no response for a year and a half. I don't see any recent
packaging activity by Jon, do you know if they are still interested in their
Fedora packages?


I'm alive!


Glad to hear that!


My time in Fedora has been.limited to non-existent :).
Would you or someone else like ownership of these? More than happy to
oblige.


My motivation is to get the packages removed if they cannot be ported to Python 
3, because they are non-functional now when trac was switched. But I don't want 
to own them :/


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Non-responsive maintainer check for jstanley

[Jon Stanley]

On Fri, Mar 5, 2021 at 11:12 AM Miro Hrončok  wrote:
>
> Hello,
>
> there are several bugzillas wrt Python 2 usage in trac plugins maintained by
> user jstanley with no response for a year and a half. I don't see any recent
> packaging activity by Jon, do you know if they are still interested in their
> Fedora packages?

I'm alive! My time in Fedora has been.limited to non-existent :).
Would you or someone else like ownership of these? More than happy to
oblige.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Benjamin Berg]

On Fri, 2021-03-05 at 17:20 +, Tom Seewald wrote:
> > Can you please provide output of `authselect current`?
> # authselect current
> Profile ID: sssd
> Enabled features:
> - with-fingerprint
> - with-silent-lastlog
> 
> # authselect check
> Current configuration is valid.
> 
> I have verified that both sssd and fprintd are running, and are not
> logging any errors.

Hmm, that might be a different issue then. I don't have a good idea
right now, GDM complaining repeatedly generally means that the
fingerprint-auth stack is failing with an error (other than
PAM_AUTHINFO_UNAVAIL)

Could you modify fprintd.service, to set G_MESSAGES_DEBUG=all[1] and
then grab a log of that?
This will also tell us what is going on in pam_fprintd, and maybe from
there we understand why the fingerprint-auth stack seems to be throwing
errors.

Benjamin

[1] You can use systemd edit fprintd.service, then write:

[Service]
Environment=G_MESSAGES_DEBUG=all

and safe that.


signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Plymouth, themes and console clearing: https://bugzilla.redhat.com/show_bug.cgi?id=1933378

[Zbigniew Jędrzejewski-Szmek]

On Fri, Mar 05, 2021 at 10:03:31AM +0100, Hans de Goede wrote:
> Hi,
> 
> On 3/4/21 11:45 PM, Adam Williamson wrote:
> > On Thu, 2021-03-04 at 22:40 +0100, Hans de Goede wrote:
> >>
> >>> Starting from a minimal install with plymouth omitted, adding just
> >>> plymouth itself pulls in 3 packages (plymouth, plymouth-core-libs,
> >>> plymouth-scripts) with an installed size of 621K. Adding plymouth-
> >>> system-theme pulls in 32 packages with an installed size of 24M. So
> >>> putting plymouth-system-theme in @core would substantially inflate the
> >>> size of @core in terms of both number of packages and overall installed
> >>> size. Removing plymouth from @core would not save a lot in terms of
> >>> packages or space.
> >>>
> >>> So, I guess the question here is, what do we do?
> >>>
> >>> 1) Remove plymouth from @core
> >>> 2) Add plymouth-system-theme to @core
> >>> 3) Make Hans/Ray/someone fix the plymouth bug
> >>
> >> 1) clearly gets my vote, not just because I don't have time to work on 3)
> >> but also because to me it seems like the right thing to do. Plymouth is
> >> a boot splash, its goal is to make the boot look pretty / hide all the
> >> scary log messages in use-cases where we want this.  The text fallback
> >> splash is not pretty. In general if it shows instead of the graphical
> >> splash the fact that the text fallback shows is considered a bug.
> > 
> > Well, you could still argue it's prettier than a wall-o-text boot. And
> > it *does* hide the wall-o-text.
> > 
> >> So either the server spin wants a pretty boot and then they should fix the
> >> bug of the text splash showing by installing plymouth-system-theme, or the
> >> server spin does not want a pretty boot and then there should be no
> >> plymouth at all.
> > 
> > What if we want something arguably-prettier than wall-o-text, but don't
> > want an extra 32 packages and 24M of storage used up?
> 
> Systemd has you covered here, you can tell it to not log any startup
> status or to only log errors by specifying systemd.show_status=no or
> systemd.show_status=auto on the kernel commandline.

I believe we don't show stuff by default any more.
https://github.com/systemd/systemd/commit/0d066dd1a4:

pid1: add new mode systemd.show-status=error and use it when 'quiet' is 
passed

systemd.show-status=error is useful for the case where people care about 
errors
only.

If people want to have a quiet boot, they most likely don't want to see all
status output even if there is a delay in boot, so make "quiet" imply
systemd.show-status=error instead of systemd.show-status=auto.

And we specify 'quiet' by default.

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Request to include package: coreboot

[Stephen John Smoogen]

On Fri, 5 Mar 2021 at 01:11, romulasry via devel <
devel@lists.fedoraproject.org> wrote:

> Preferribly a git version with all packages would be nice
>
>
Are you proposing to do the work? Or are you looking for people to do the
work?



> Hope this is the right place to put this, if not what list, thanks in
> advance.
> https://www.coreboot.org/
>
>
> Sent with ProtonMail  Secure Email.
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 
Stephen J Smoogen.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Plymouth, themes and console clearing: https://bugzilla.redhat.com/show_bug.cgi?id=1933378

[Stephen Gallagher]

On Fri, Mar 5, 2021 at 12:27 PM Kevin Fenzi  wrote:
>
> On Thu, Mar 04, 2021 at 03:52:04PM -0500, Matthew Miller wrote:
> > On Thu, Mar 04, 2021 at 12:14:07PM -0800, Adam Williamson wrote:
> > > If you don't have plymouth installed, you get a very old-school "wall
> > > of text" boot process; if there are encrypted system partitions, you
> > > get a plain text prompt for the encryption passphrase, with no keyboard
> > > layout indicator (I'm not sure if the text theme indicates the keyboard
> > > layout either).
> >
> > I, for one, am for it. I _expect_ my servers to provide an old-school wall
> > of text boot.
>
> Same here. I'm fine removing it...

+1
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Zbigniew Jędrzejewski-Szmek]

On Fri, Mar 05, 2021 at 11:35:37AM -0500, Matthew Miller wrote:
> On Fri, Mar 05, 2021 at 05:12:34PM +0100, Tomasz Torcz wrote:
> > > > This is another one for which it is questionable to have it running, or 
> > > > is this a machine with
> > > > ECC RAM ? And even then I'm not sure if it adds a lot of value, or if 
> > > > just like smartd it
> > > > just logs some stuff into syslog (where normal users won't see it).
> > > 
> > > I disagree that those logs are useless -- I often help normal users, and
> > > running commands to look back in the logs for problems is a common
> > > diagnostic step. This could be better, of course.
> > 
> >   They are useful. smartd even sends emails – that's how I was informed
> > about one of my disks dying, few weeks ago,
> 
> It can, but most people don't have a good setup for even local mail
> delivery. Out of the box, we don't really do anything useful. It'd be nice
> for our desktop offerings to have some kind of way of showing these
> messages in a helpful way.

Once we reach the noble goal of having 0 warnings during boot by default,
we could just issue a notification whenever anything pops up. We do that
for kernel oops already.

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Status update for the new AAA system

[Kevin Fenzi]

On Fri, Mar 05, 2021 at 11:02:54AM -, Aurelien Bompard wrote:
> An update again!
> 
> We've sent an email to folks that have an account in both Fedora & CentOS but 
> registered with different email addresses. If that's your case, please choose 
> one address for both accounts, it'll help us migrate.
> 
> We are now in the middle of the final sprint for production deployment. We're 
> trying to fit the dates for the beta release to avoid causing delays, so 
> we're targeting March 18th as a deployment date. We want to aim for the right 
> timeslot between Ireland's national holiday on the 17th and Fedora's beta 
> release the week after. We are conscious that we're planning a critical 
> production deployment the morning after St Patrick's day... Let the sysadmin 
> who has never deployed with a headache cast the first stone. ;-)

The 'preferred' date for Beta is the 16th. ;) Hopefully we will hit
that. But we may want to move this to the next week in case Beta is the
second slot (The 23rd)

> After production deployment, FAS will be made read-only to avoid breaking 
> applications that haven't been migrated yet, but its data will start drifting 
> away from the real production data, so we encourage you to switch as soon as 
> you can. We haven't decided how long we'll keep FAS running, but it's 
> probably not going to be very long because of the associated maintenance 
> ressources.

Hopefully there are not too many people directly querying fas. :) 

I'll note that people just using their Fedora account to login to other
things will be automatically switched when we cut over. The only things
using fas left would be scripts that users have that queries the fas
api. 

> The URL for Noggin will be accounts.fedoraproject.org. It's more in line with 
> our naming conventions, and we will add a warning on FAS's page to let users 
> know that it's read-only and deprecated with a link to Noggin. Eventually, 
> we'll set a redirect.
> 
> If you are a group admin, please check that your group's description is still 
> up-to-date, because changing it will require opening an infra ticket in the 
> future and it's going to be less easy (until we find cycles to add this 
> feature of course -- or until you do!).
> 
> We're doing our best to avoid breaking anything accidentally, but if that 
> happens please open a ticket or contact us on IRC at #fedora-aaa.

Thanks for the updates!

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1935417] perl-HTML-Parser-3.76 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1935417

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #2 from Fedora Update System  ---
FEDORA-2021-c620c81807 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
--advisory=FEDORA-2021-c620c81807`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-c620c81807

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Tom Seewald]

> Can you please provide output of `authselect current`?
# authselect current
Profile ID: sssd
Enabled features:
- with-fingerprint
- with-silent-lastlog

# authselect check
Current configuration is valid.

I have verified that both sssd and fprintd are running, and are not logging any 
errors.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

CPE Weekly: 2021-03-05

[Aoife Moloney]

Hi Everyone,


If you would like to see this report and toggle to the section you are
most interested in, I would suggest visiting this link
https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view and use the header bar
on your left to skip to where you want to go!

## Initiative FYI Links
Initiatives repo here: https://pagure.io/cpe/initiatives-proposal
2021 Quarterly Planning timetable here:
https://docs.fedoraproject.org/en-US/cpe/time_tables/
Details on initiative requesting/how to work with us on new projects
here: https://docs.fedoraproject.org/en-US/cpe/initiatives/


### Misc
* CentOS Newsletter for March is out!
https://blog.centos.org/2021/03/centos-community-newsletter-march-2021-2103/
* CentOS Dojo scheduled for May 13th & 14th CFP is open, details on
event and CFP link can be found here
https://wiki.centos.org/Events/Dojo/May2021
* New community podcast is out from Red Hat Community
https://twitter.com/redhatopen/status/1367113857936809984
* Lightning Talks & some others from DevConf.cz are now uploaded!
https://www.youtube.com/c/DevConf_INFO/featured
* Check out the most recent blog post on the Fedora Code of Conduct
here https://communityblog.fedoraproject.org/fedora-code-of-conduct-report-2020/


## Project Updates
*The below updates are pulled directly from our CPE team call we have
every week.*

### Fedora
* Still in Beta Freeze
* Working on progressing flatpak-indexer, its currently in staging
* Processed 100+ fedscm requests!
* In staging got pagure on dist-git working with the git user instead
of each packager having their own shell account
* Working with debuginfo-d folks to get them set up with resources to
enable it in Fedora infra

### Noggin/AAA
* Reviewing dates for a planned outage in March - early estimated
dates are 18th & 19th for production migration. Formal email to follow
to all fedora lists once outage period is confirmed early next week.
* Community blog coming middle of next week on the new account system work
* The work tracker for this project can be found here
https://github.com/orgs/fedora-infra/projects/6
* The team use #fedora-aaa for discussions on IRC
* And please report any issues you find in the repo
https://github.com/fedora-infra/noggin



## CentOS Updates

### CentOS
* Legacy CentOS CI Infra Openshift 3.6 has been retired
* CentOS CI OCP clusters updated to 4.6.18


### CentOS Stream
* Testing centpkg against the new buildsystem and CBS
* Developing a style guide for CentOS Stream - first draft will be in
a repo on git.centos.org to view/comment by mid-March
* Building CentOS Stream only packages, eg logos, etc for Stream 9



## Team Info
### Background:
The Community Platform Engineering group, or CPE for short, is the Red
Hat team combining IT and release engineering from Fedora and CentOS.
Our goal is to keep core servers and services running and maintained,
build releases, and other strategic tasks that need more dedicated
time than volunteers can give.


See our wiki page here for more
information:https://docs.fedoraproject.org/en-US/cpe/

-- 

Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Plymouth, themes and console clearing: https://bugzilla.redhat.com/show_bug.cgi?id=1933378

[Kevin Fenzi]

On Thu, Mar 04, 2021 at 03:52:04PM -0500, Matthew Miller wrote:
> On Thu, Mar 04, 2021 at 12:14:07PM -0800, Adam Williamson wrote:
> > If you don't have plymouth installed, you get a very old-school "wall
> > of text" boot process; if there are encrypted system partitions, you
> > get a plain text prompt for the encryption passphrase, with no keyboard
> > layout indicator (I'm not sure if the text theme indicates the keyboard
> > layout either).
> 
> I, for one, am for it. I _expect_ my servers to provide an old-school wall
> of text boot.

Same here. I'm fine removing it... 

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: getting EPEL 9 started [was Re: ELN SIG First Meeting]

[Kevin Fenzi]

On Thu, Mar 04, 2021 at 02:31:14PM -0800, Michel Alexandre Salim wrote:
> Sorry for jumping in late, I'm sporadically online while on parental
> leave (haven't been able to touch my laptop for the past few days!)

No need to be sorry. :) Congrats!

> Mass-branching does seem too different from what we currently do (EPEL
> branches are opt-in for a package); building in COPR sounds more
> workable (Miro does mass-rebuilds of Python packages to test for
> compatibility with upcoming Python releases that way).
> 
> Selecting which packages to build is tricky though - we wouldn't
> necessarily want to mass build packages that will never be packaged in
> EPEL, as that will just be wasted cycles.
> 
> And we have packages that are in EPEL for various reasons:
> - the package itself is useful to end users (e.g. tools as Matthew
> mentioned, but also libraries that might be dependencies for some
> software that is itself not in EL/EPEL
> - the package is a dependency of a package that is useful
>   -> in this case, automatically branching might not be a good idea
>   if e.g. this is a parallel installable new version of a library
>   already in EL, and for ELN said library is not needed
> 
> How about this approach, though?
> - create epel(N+1) (and epel(N+1)-next, now that we're doing Stream
> first) as soon as ELN starts targeting EL (N+1) - so in this case, we
> want to create epel10 / epel10-next now
> - if said branch exists for a package:
>   - if a spec is found, use it for building against ELN
>   - if a spec is not found, build the Rawhide branch against ELN

What makes the list of packages there?
Everything in epel8? Everything in fedora?

The build ordering there would be difficult to know and definitely
require people work. 

> Maintainers interested in EPEL can thus get early notification as to if
> they need to make any change (or if they need to chase missing
> dependencies and get those branched)
> 
> This will tie in nicely with what the EPEL Packagers SIG is working on
> - we want to have the SIG eventually be added as collaborators (on
> epel* branches) to packages where we identify a need for EL use, but
> where the primary maintainer is not interested: having the branch
> available earlier will reduce the need to scramble at the last minute
> to chase packages' dependencies.

Well, perhaps. But also it means they have to maintain another branch
(epel10) for like 3 or so more years, no? Deps in eln will change,
things will be added, etc. I think avoiding a last minue scramble might
be nice, but making it a 3 extra years of maint is... a bit much. 

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Matthew Miller]

On Fri, Mar 05, 2021 at 05:12:34PM +0100, Tomasz Torcz wrote:
> > > This is another one for which it is questionable to have it running, or 
> > > is this a machine with
> > > ECC RAM ? And even then I'm not sure if it adds a lot of value, or if 
> > > just like smartd it
> > > just logs some stuff into syslog (where normal users won't see it).
> > 
> > I disagree that those logs are useless -- I often help normal users, and
> > running commands to look back in the logs for problems is a common
> > diagnostic step. This could be better, of course.
> 
>   They are useful. smartd even sends emails – that's how I was informed
> about one of my disks dying, few weeks ago,

It can, but most people don't have a good setup for even local mail
delivery. Out of the box, we don't really do anything useful. It'd be nice
for our desktop offerings to have some kind of way of showing these
messages in a helpful way.

-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Tomasz Torcz]

Dnia Fri, Mar 05, 2021 at 10:17:17AM -0500, Matthew Miller napisał(a):
> On Fri, Mar 05, 2021 at 03:05:00PM +0100, Hans de Goede wrote:
> > >   mcelog.service   loaded active running 
> > > Machine Check Exception Logging Daemon
> > This is another one for which it is questionable to have it running, or is 
> > this a machine with
> > ECC RAM ? And even then I'm not sure if it adds a lot of value, or if just 
> > like smartd it
> > just logs some stuff into syslog (where normal users won't see it).
> 
> I disagree that those logs are useless -- I often help normal users, and
> running commands to look back in the logs for problems is a common
> diagnostic step. This could be better, of course.

  They are useful. smartd even sends emails – that's how I was informed
about one of my disks dying, few weeks ago,

-- 
Tomasz Torcz “God, root, what's the difference?”
to...@pipebreaker.pl   “God is more forgiving.”
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Non-responsive maintainer check for jstanley

[Miro Hrončok]

Hello,

there are several bugzillas wrt Python 2 usage in trac plugins maintained by 
user jstanley with no response for a year and a half. I don't see any recent 
packaging activity by Jon, do you know if they are still interested in their 
Fedora packages?


https://bugzilla.redhat.com/show_bug.cgi?id=1935820

https://bugzilla.redhat.com/show_bug.cgi?id=1739024
https://bugzilla.redhat.com/show_bug.cgi?id=1739032
https://bugzilla.redhat.com/show_bug.cgi?id=1739042

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Request to include package: coreboot

[Qiyu Yan]

romulasry via devel  于2021年3月5日周五 下午2:04写道：
>
> Preferribly a git version with all packages would be nice
>
> Hope this is the right place to put this, if not what list, thanks in advance.
> https://www.coreboot.org/
Is coreboot intended to be shipped as part of distribution? I think it
should be something that being shipped with a hardware.
>
>
> Sent with ProtonMail Secure Email.
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-IoT-34-20210305.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 4/15 (aarch64), 1/16 (x86_64)

New failures (same test not failed in Fedora-IoT-34-20210304.0):

ID: 800883  Test: aarch64 IoT-dvd_ostree-iso podman@uefi
URL: https://openqa.fedoraproject.org/tests/800883
ID: 800884  Test: aarch64 IoT-dvd_ostree-iso podman_client@uefi
URL: https://openqa.fedoraproject.org/tests/800884

Old failures (same test failed in Fedora-IoT-34-20210304.0):

ID: 800864  Test: x86_64 IoT-dvd_ostree-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/800864
ID: 800873  Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi
URL: https://openqa.fedoraproject.org/tests/800873
ID: 800880  Test: aarch64 IoT-dvd_ostree-iso base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/800880

Soft failed openQA tests: 3/16 (x86_64), 1/15 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-IoT-34-20210304.0):

ID: 800856  Test: x86_64 IoT-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/800856
ID: 800857  Test: x86_64 IoT-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/800857
ID: 800858  Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/800858
ID: 800872  Test: aarch64 IoT-dvd_ostree-iso install_default_upload@uefi
URL: https://openqa.fedoraproject.org/tests/800872

Passed openQA tests: 12/16 (x86_64), 10/15 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Matthew Miller]

On Fri, Mar 05, 2021 at 03:05:00PM +0100, Hans de Goede wrote:
> >   mcelog.service   loaded active running 
> > Machine Check Exception Logging Daemon
> This is another one for which it is questionable to have it running, or is 
> this a machine with
> ECC RAM ? And even then I'm not sure if it adds a lot of value, or if just 
> like smartd it
> just logs some stuff into syslog (where normal users won't see it).

I disagree that those logs are useless -- I often help normal users, and
running commands to look back in the logs for problems is a common
diagnostic step. This could be better, of course.

> So given that I got a couple of "go for it" reactions and that I was
> already toying with the idea anyways I might actually try to make such
> a spin happen.
> 
> The biggest problem for doing such a spin is finding the time for it...
> 
> Are there any people who would be interested in working on / co-maintaining
> such a spin with me ?

I am interested in it happening but can't sign up for more stuff. :)

It seems like this kind of parallels the Minimization objective (which
focuses on package dependencies). That's kind of mothballed right now (I
think because Adam is working on RHEL 9 stuff?) and I wouldn't want to
overload that more, but maybe there's some kind of useful connection?

-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Matthew Miller]

On Fri, Mar 05, 2021 at 12:56:57PM +, Zbigniew Jędrzejewski-Szmek wrote:
> I think there's still plenty of stuff to improve that will apply everywhere.
> homed, alsactl, geoclue, colord just shouldn't need to be there all the time.

firewalld, too. For most users it's just putting a static configuration into
place once. A little more complicated with virtual machine networking
(possibly container stuff too) but even then it's not something that really
needs to be always on.

-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-34-20210305.n.0 compose check report

[Fedora compose checker]

No missing expected images.

Failed openQA tests: 8/187 (x86_64), 12/126 (aarch64)

New failures (same test not failed in Fedora-34-20210304.n.0):

ID: 800577  Test: x86_64 KDE-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/800577
ID: 800610  Test: aarch64 Server-dvd-iso support_server@uefi
URL: https://openqa.fedoraproject.org/tests/800610
ID: 800625  Test: aarch64 Server-dvd-iso 
install_repository_nfs_variation@uefi
URL: https://openqa.fedoraproject.org/tests/800625

Old failures (same test failed in Fedora-34-20210304.n.0):

ID: 800550  Test: x86_64 Workstation-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/800550
ID: 800559  Test: x86_64 Workstation-live-iso 
desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/800559
ID: 800563  Test: x86_64 Workstation-live-iso desktop_login
URL: https://openqa.fedoraproject.org/tests/800563
ID: 800568  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/800568
ID: 800578  Test: x86_64 KDE-live-iso desktop_browser
URL: https://openqa.fedoraproject.org/tests/800578
ID: 800579  Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL: https://openqa.fedoraproject.org/tests/800579
ID: 800605  Test: aarch64 Minimal-raw_xz-raw.xz base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/800605
ID: 800606  Test: aarch64 Minimal-raw_xz-raw.xz base_selinux@uefi
URL: https://openqa.fedoraproject.org/tests/800606
ID: 800607  Test: aarch64 Minimal-raw_xz-raw.xz 
base_service_manipulation@uefi
URL: https://openqa.fedoraproject.org/tests/800607
ID: 800608  Test: aarch64 Minimal-raw_xz-raw.xz release_identification@uefi
URL: https://openqa.fedoraproject.org/tests/800608
ID: 800619  Test: aarch64 Server-dvd-iso install_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/800619
ID: 800624  Test: aarch64 Server-dvd-iso 
install_repository_hd_variation@uefi
URL: https://openqa.fedoraproject.org/tests/800624
ID: 800670  Test: aarch64 Workstation-raw_xz-raw.xz desktop_browser@uefi
URL: https://openqa.fedoraproject.org/tests/800670
ID: 800686  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/800686
ID: 800763  Test: aarch64 universal install_asian_language@uefi
URL: https://openqa.fedoraproject.org/tests/800763
ID: 800797  Test: aarch64 universal upgrade_2_server_domain_controller@uefi
URL: https://openqa.fedoraproject.org/tests/800797
ID: 800802  Test: aarch64 universal upgrade_2_realmd_client@uefi
URL: https://openqa.fedoraproject.org/tests/800802

Soft failed openQA tests: 57/126 (aarch64), 91/187 (x86_64)
(Tests completed, but using a workaround for a known bug)

New soft failures (same test not soft failed in Fedora-34-20210304.n.0):

ID: 800653  Test: aarch64 Server-raw_xz-raw.xz 
install_arm_image_deployment_upload@uefi
URL: https://openqa.fedoraproject.org/tests/800653
ID: 800658  Test: aarch64 Server-raw_xz-raw.xz base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/800658
ID: 800782  Test: aarch64 universal install_with_swap@uefi
URL: https://openqa.fedoraproject.org/tests/800782
ID: 800792  Test: aarch64 universal install_simple_encrypted@uefi
URL: https://openqa.fedoraproject.org/tests/800792
ID: 800799  Test: aarch64 universal upgrade_server_64bit@uefi
URL: https://openqa.fedoraproject.org/tests/800799

Old soft failures (same test soft failed in Fedora-34-20210304.n.0):

ID: 800491  Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/800491
ID: 800492  Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/800492
ID: 800494  Test: x86_64 Server-dvd-iso install_repository_nfs_graphical
URL: https://openqa.fedoraproject.org/tests/800494
ID: 800497  Test: x86_64 Server-dvd-iso install_blivet_btrfs_preserve_home
URL: https://openqa.fedoraproject.org/tests/800497
ID: 800498  Test: x86_64 Server-dvd-iso 
install_blivet_btrfs_preserve_home_uefi@uefi
URL: https://openqa.fedoraproject.org/tests/800498
ID: 800499  Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4
URL: https://openqa.fedoraproject.org/tests/800499
ID: 800500  Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/800500
ID: 800501  Test: x86_64 Server-dvd-iso 
install_blivet_standard_partition_ext4
URL: https://openqa.fedoraproject.org/tests/800501
ID: 800502  Test: x86_64 Server-dvd-iso 
install_blivet_standard_partition_ext4@uefi
URL: https://openqa.fedoraproject.org/tests/800502
ID: 800503  Test: x86_64 Server-dvd-iso install_btrfs_preserve_home
URL: https://openqa.fedoraproject.org/tests/800503
ID: 800504  Test: x86_64 Server-dvd-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/800504
ID: 800505  Test: x86_64 Server-dvd-iso install_default_upload

[Test-Announce] Fedora-IoT 34 RC 20210305.0 nightly compose nominated for testing

[rawhide]

Announcing the creation of a new nightly release validation test event
for Fedora-IoT 34 RC 20210305.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/34iot

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_34_RC_20210305.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_34_RC_20210305.0_General

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-IoT-35-20210305.0 compose check report

[Fedora compose checker]

Missing expected images:

Iot dvd x86_64
Iot dvd aarch64

Failed openQA tests: 2/16 (x86_64), 3/15 (aarch64)

New failures (same test not failed in Fedora-IoT-35-20210304.0):

ID: 800818  Test: x86_64 IoT-dvd_ostree-iso release_identification
URL: https://openqa.fedoraproject.org/tests/800818
ID: 800833  Test: aarch64 IoT-dvd_ostree-iso release_identification@uefi
URL: https://openqa.fedoraproject.org/tests/800833

Old failures (same test failed in Fedora-IoT-35-20210304.0):

ID: 800812  Test: x86_64 IoT-dvd_ostree-iso base_services_start
URL: https://openqa.fedoraproject.org/tests/800812
ID: 800821  Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi
URL: https://openqa.fedoraproject.org/tests/800821
ID: 800828  Test: aarch64 IoT-dvd_ostree-iso base_services_start@uefi
URL: https://openqa.fedoraproject.org/tests/800828

Soft failed openQA tests: 3/16 (x86_64), 1/15 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-IoT-35-20210304.0):

ID: 800804  Test: x86_64 IoT-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/800804
ID: 800805  Test: x86_64 IoT-dvd_ostree-iso install_default_upload
URL: https://openqa.fedoraproject.org/tests/800805
ID: 800806  Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/800806
ID: 800820  Test: aarch64 IoT-dvd_ostree-iso install_default_upload@uefi
URL: https://openqa.fedoraproject.org/tests/800820

Passed openQA tests: 11/16 (x86_64), 11/15 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Hans de Goede]

Hi,

On 3/5/21 1:56 PM, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Mar 04, 2021 at 07:50:11PM +0100, Hans de Goede wrote:
>>> I am not sure about this. What services are you seeing which are 
>>> extraneous? I do see ps aux is going on miles and miles, but of the 218 
>>> processes I see from startup time on my workstation, I see 165 of them are 
>>> kernel processes versus user space ones. Of the remaining 53, most of them 
>>> seem hardware oriented (irqbalance, bluetooth, modemmanager, smartd, 
>>> udisksd, upowerd, etc). Looking at the rest we have about 20 processes 
>>> which seem outside of 'I don't want my laptop to work with modern hardware' 
>>> and that would be abrt, atd/crond/cupsd, packagekitd, colord, and the sssd 
>>> processes. So while ps auxww has a lot more going on in it, I actually see 
>>> a lot fewer extraneous processes than I remember from my Fedora 18 days.
>>
>> 20 processes is still a lot when e.g. booting from an eMMC or a sdcard those 
>> add a significant amount of time to the startupo time.
> 
> I agree, we really have too many things starting, to many things
> running, and too many things generating errors.
> 
> Instead of 'ps aux', 'systemctl -t service --state running' is easier to 
> interpret:
>   UNIT LOAD   ACTIVE SUB 
> DESCRIPTION   
>   accounts-daemon.service  loaded active running Accounts 
> Service
>   alsa-state.service   loaded active running Manage 
> Sound Card State (restore and store)
> ^ do we really need this

This used to be a startup / shutdown job thing only, but now I think it 
periodically saves
the state. It might be good to file a (polite) bug against alsa-lib for this 
and see what
Jaroslav has to say about this.

> 
>   avahi-daemon.service loaded active running Avahi 
> mDNS/DNS-SD Stack
>   bluetooth.serviceloaded active running 
> Bluetooth service
>   colord.service   loaded active running Manage, 
> Install and Generate Color Profiles
>   cups.service loaded active running CUPS 
> Scheduler
> ^ this should be socket activated, I haven't printed *anything* on this 
> machine ever

Agreed

>   dbus-:1.2-org.freedesktop.problems@0.service loaded active running 
> dbus-:1.2-org.freedesktop.problems@0.service
>   dbus-broker.service  loaded active running D-Bus 
> System Message Bus
>   firewalld.serviceloaded active running 
> firewalld - dynamic firewall daemon
>   gdm.service  loaded active running GNOME 
> Display Manager
>   geoclue.service  loaded active running Location 
> Lookup Service
>   gpm.service  loaded active running Console 
> Mouse manager
>   iio-sensor-proxy.service loaded active running IIO 
> Sensor Proxy service
>   libvirtd.service loaded active running 
> Virtualization daemon
>   low-memory-monitor.service   loaded active running Low 
> Memory Monitor
> ^ this is interesting. gnome-shell.rpm requires lower-memory-monitor.rpm, 
> and the default preset is on.
>   Do we still want this with systemd-oomd being on by default?
> 
>   mcelog.service   loaded active running Machine 
> Check Exception Logging Daemon

This is another one for which it is questionable to have it running, or is this 
a machine with
ECC RAM ? And even then I'm not sure if it adds a lot of value, or if just like 
smartd it
just logs some stuff into syslog (where normal users won't see it).

>   ModemManager.service loaded active running Modem 
> Manager
>   NetworkManager.service   loaded active running Network 
> Manager
>   pcscd.serviceloaded active running PC/SC 
> Smart Card Daemon
>   pmcd.service loaded active running 
> Performance Metrics Collector Daemon
>   pmie.service loaded active running 
> Performance Metrics Inference Engine
>   pmlogger.service loaded active running 
> Performance Metrics Archive Logger
>   polkit.service   loaded active running 
> polkit.service
>   sssd-kcm.service loaded active running SSSD 
> Kerberos Cache Manager
>   sssd.service loaded active running System 
> Security Services Daemon
>   switcheroo-control.service   loaded active running 
> Switcheroo Control Proxy service
>   systemd-homed.serviceloaded active running Home 
> Area Manager
> ^ hmm, I would think this would be go away on its own. Maybe something to 
> fix upstream.

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Hans de Goede]

Hi,

On 3/5/21 11:59 AM, Pavel Březina wrote:
> On 3/4/21 5:11 PM, Hans de Goede wrote:
>> Hi,
>>
>> On 3/4/21 11:50 AM, Pavel Březina wrote:
>>> On 3/3/21 6:11 PM, Hans de Goede wrote:
 Hi,

 On 3/2/21 5:20 PM, Pavel Březina wrote:
> On 3/2/21 4:25 PM, Ray Strode wrote:
>> Hi,
>>
>> Ahh, okay.
>>
>> On Tue, Mar 2, 2021 at 9:31 AM Hans de Goede  wrote:
>>> sudo authselect select minimal
>>> sudo authselect apply-changes
>>>
>>> Which results in the following /etc/pam.d/fingerprint-auth file:
>>>
>>> [hans@x1 linux]$ sudo cat /etc/pam.d/fingerprint-auth
>>> # Generated by authselect on Tue Mar  2 15:24:53 2021
>>> # Do not modify this file manually.
>
> minimal profile does not support fingerprint

 So it seems there are 4 profiles:

 [hans@x1 ~]$ authselect list
 - minimal Local users only for minimal installations
 - nis Enable NIS for system authentication
 - sssd    Enable SSSD for system authentication (also for local users 
 only)
 - winbind Enable winbind for system authentication

 What I want is a profile which uses just the good old /etc files to
 avoid the overhead of running a local daemon (sssd tends to show up as
 one of the top 10 wakeup sources in powertop on an idle system) and I
 also don't want a config which tries to go out on the network.

 So minimal seems to meet my needs; and although I personally do not
 have much of a need for fingerprint auth, I don't really see why we
 could not do fingerprint auth with the minimal config. I'm pretty
>>>
>>> I'd say the answer is simple - if you go with minimal, you don't need 
>>> fingerprint. And you wrote it yourself - you don't need fingerprint auth. 
>>> Just because something can be done, does not mean it is worth to maintain 
>>> it. More info below.
>>>
 sure I can manually create a pam-config where this works just fine.

 I guess its in the name minimal, where as "local" might be (1) a better
>>>
>>> That's the point - it's minimal not local, not without-sssd. The readme 
>>> explicitly says that it reserved for cases when you really care about disk 
>>> and memory footprint.
>>>
>>> It has very limited functionality by design. If you do not want to use 
>>> SSSD, you can keep using sssd profile and just disable the service. It will 
>>> keep working. The minimal profile is there for users that also want to 
>>> remove sssd packages to safe resources, but in that case you probably don't 
>>> care about fingerprint and smartcards either.
>>
>> The problem is that IMHO having sssd enabled by default is really the wrong 
>> thing to do for like 95% of our users and defaults should be the settings 
>> which are best for most / almost all users.
>>
>> This is really just a symptom of a much bigger problem though, which is that 
>> we simply have way too much services / daemon's starting up by default. The 
>> output of "ps aux" after a default Fedora workstation install is just way 
>> way too long. Once upon a time Linux users used to make fun of Windows with 
>> all its background processes in the mean time a default Fedora WS install 
>> has gotten worse then Windows wrt background processes. Any of these are 
>> totally unnecessary for most of our users.
>>
>> We really should be smarter here and the config tools which allows a user to 
>> enroll in an authentication domain enable the sssd config when that happens 
>> and not have this on by default for everyone.
>>
>> So what I would really like to see is a local profile which uses just /etc 
>> files + fprintd if there are fingerprints enrolled. Smartcards are a 
>> different story, because those likely also need significant extra setup.
>>
>> Where as fingerprints can easily be enrolled from the local UI tools.
>>
 name. Note I'm not suggesting to add another profile just for this
 but it would be nice if fingerprint auth would at least be a
 (default off) feature for the minimal config.

 Shall I file a RFE issue for this at:
 https://github.com/authselect/authselect/issues/
>>>
>>> If you need fingerprint auth then open the ticket please - but no promises 
>>> here. If you don't need it then just don't open the ticket :-)
>>
>> Rather then opening a ticket, what I would really like to see is a good 
>> discussion about why the sssd profile is the default, because IMHO it is a 
>> bad default for most users.
> 
> I hear you. From authselect perspective, SSSD was enabled by default through 
> a change page that was accepted by community. Therefore authselect is 
> advertising this profile as the main and only. If you want to run without 
> sssd, you can disable the service but you don't have to switch to other 
> profile.
> 
> Whether or not it should be enabled by default is a different discussion. 
> But... The SSSD team does acknowledge that it does not have to be enabled by 
> 

[rpms/perl-PDF-API2] PR #1: Tests

[Jitka Plesnikova]

jplesnik opened a new pull-request against the project: `perl-PDF-API2` that 
you are following:
``
Tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-PDF-API2/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora 34 compose report: 20210305.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-34-20210304.n.0
NEW: Fedora-34-20210305.n.0

= SUMMARY =
Added images:0
Dropped images:  2
Added packages:  0
Dropped packages:0
Upgraded packages:   0
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   0 B
Size of downgraded packages: 0 B

Size change of upgraded packages:   0 B
Size change of downgraded packages: 0 B

= ADDED IMAGES =

= DROPPED IMAGES =
Image: KDE raw-xz aarch64
Path: Spins/aarch64/images/Fedora-KDE-34-20210304.n.0.aarch64.raw.xz
Image: KDE raw-xz armhfp
Path: Spins/armhfp/images/Fedora-KDE-34-20210304.n.0.armhfp.raw.xz

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =

= DOWNGRADED PACKAGES =
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: PHP 8 mass rebuild in rawhide - DONE

[Remi Collet]

Le 04/03/2021 à 09:08, Remi Collet a écrit :

Hi,

I start working on PHP 8 for Fedora 35
https://fedoraproject.org/wiki/Changes/php80


PHP 8.0.3 will be shortly in rawhide

https://bodhi.fedoraproject.org/updates/FEDORA-2021-6efb3c293c

FTBFS
-
#1934995swig
#1934996graphviz
#1934997mlt
#1935576php-pecl-radius
#1935612libkolabxml
#1935622mapserver
#1935626ming
#1935712redland-bindings

All mostly related to swig not compatible yet


Cheers,
Remi
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Zbigniew Jędrzejewski-Szmek]

On Thu, Mar 04, 2021 at 07:50:11PM +0100, Hans de Goede wrote:
> > I am not sure about this. What services are you seeing which are 
> > extraneous? I do see ps aux is going on miles and miles, but of the 218 
> > processes I see from startup time on my workstation, I see 165 of them are 
> > kernel processes versus user space ones. Of the remaining 53, most of them 
> > seem hardware oriented (irqbalance, bluetooth, modemmanager, smartd, 
> > udisksd, upowerd, etc). Looking at the rest we have about 20 processes 
> > which seem outside of 'I don't want my laptop to work with modern hardware' 
> > and that would be abrt, atd/crond/cupsd, packagekitd, colord, and the sssd 
> > processes. So while ps auxww has a lot more going on in it, I actually see 
> > a lot fewer extraneous processes than I remember from my Fedora 18 days.
> 
> 20 processes is still a lot when e.g. booting from an eMMC or a sdcard those 
> add a significant amount of time to the startupo time.

I agree, we really have too many things starting, to many things
running, and too many things generating errors.

Instead of 'ps aux', 'systemctl -t service --state running' is easier to 
interpret:
  UNIT LOAD   ACTIVE SUB 
DESCRIPTION   
  accounts-daemon.service  loaded active running Accounts 
Service
  alsa-state.service   loaded active running Manage 
Sound Card State (restore and store)
^ do we really need this

  avahi-daemon.service loaded active running Avahi 
mDNS/DNS-SD Stack
  bluetooth.serviceloaded active running Bluetooth 
service
  colord.service   loaded active running Manage, 
Install and Generate Color Profiles
  cups.service loaded active running CUPS 
Scheduler
^ this should be socket activated, I haven't printed *anything* on this 
machine ever
  dbus-:1.2-org.freedesktop.problems@0.service loaded active running 
dbus-:1.2-org.freedesktop.problems@0.service
  dbus-broker.service  loaded active running D-Bus 
System Message Bus
  firewalld.serviceloaded active running firewalld 
- dynamic firewall daemon
  gdm.service  loaded active running GNOME 
Display Manager
  geoclue.service  loaded active running Location 
Lookup Service
  gpm.service  loaded active running Console 
Mouse manager
  iio-sensor-proxy.service loaded active running IIO Sensor 
Proxy service
  libvirtd.service loaded active running 
Virtualization daemon
  low-memory-monitor.service   loaded active running Low Memory 
Monitor
^ this is interesting. gnome-shell.rpm requires lower-memory-monitor.rpm, 
and the default preset is on.
  Do we still want this with systemd-oomd being on by default?

  mcelog.service   loaded active running Machine 
Check Exception Logging Daemon
  ModemManager.service loaded active running Modem 
Manager
  NetworkManager.service   loaded active running Network 
Manager
  pcscd.serviceloaded active running PC/SC 
Smart Card Daemon
  pmcd.service loaded active running 
Performance Metrics Collector Daemon
  pmie.service loaded active running 
Performance Metrics Inference Engine
  pmlogger.service loaded active running 
Performance Metrics Archive Logger
  polkit.service   loaded active running 
polkit.service
  sssd-kcm.service loaded active running SSSD 
Kerberos Cache Manager
  sssd.service loaded active running System 
Security Services Daemon
  switcheroo-control.service   loaded active running Switcheroo 
Control Proxy service
  systemd-homed.serviceloaded active running Home Area 
Manager
^ hmm, I would think this would be go away on its own. Maybe something to 
fix upstream.

  systemd-journald.service loaded active running Journal 
Service
  systemd-logind.service   loaded active running User Login 
Management
  systemd-machined.service loaded active running Virtual 
Machine and Container Registration Service
  systemd-networkd.service loaded active running Network 
Service
  systemd-resolved.service loaded active running Network 
Name Resolution
  systemd-timesyncd.serviceloaded active running Network 
Time Synchronization
  systemd-udevd.serviceloaded active running Rule-based 
Manager for Device Events and 

Re: Status update for the new AAA system

[Aurelien Bompard]

An update again!

We've sent an email to folks that have an account in both Fedora & CentOS but 
registered with different email addresses. If that's your case, please choose 
one address for both accounts, it'll help us migrate.

We are now in the middle of the final sprint for production deployment. We're 
trying to fit the dates for the beta release to avoid causing delays, so we're 
targeting March 18th as a deployment date. We want to aim for the right 
timeslot between Ireland's national holiday on the 17th and Fedora's beta 
release the week after. We are conscious that we're planning a critical 
production deployment the morning after St Patrick's day... Let the sysadmin 
who has never deployed with a headache cast the first stone. ;-)

After production deployment, FAS will be made read-only to avoid breaking 
applications that haven't been migrated yet, but its data will start drifting 
away from the real production data, so we encourage you to switch as soon as 
you can. We haven't decided how long we'll keep FAS running, but it's probably 
not going to be very long because of the associated maintenance ressources.

The URL for Noggin will be accounts.fedoraproject.org. It's more in line with 
our naming conventions, and we will add a warning on FAS's page to let users 
know that it's read-only and deprecated with a link to Noggin. Eventually, 
we'll set a redirect.

If you are a group admin, please check that your group's description is still 
up-to-date, because changing it will require opening an infra ticket in the 
future and it's going to be less easy (until we find cycles to add this feature 
of course -- or until you do!).

We're doing our best to avoid breaking anything accidentally, but if that 
happens please open a ticket or contact us on IRC at #fedora-aaa.

Thanks!

Aurélien
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Pavel Březina]

On 3/4/21 9:11 PM, Tom Seewald wrote:

On rawhide I upgraded to authselect-1.2.2-3.fc35 yet I am still encountering 
the issue of gdm repeatedly complaining about authentication via fingerprint. 
I've checked and authselect is using the 'ssd' profile.


Can you please provide output of `authselect current`?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: F34 gdm login prompt goes crazy when a fingerprint reader with no enrolled prints is present

[Pavel Březina]

On 3/4/21 5:11 PM, Hans de Goede wrote:

Hi,

On 3/4/21 11:50 AM, Pavel Březina wrote:

On 3/3/21 6:11 PM, Hans de Goede wrote:

Hi,

On 3/2/21 5:20 PM, Pavel Březina wrote:

On 3/2/21 4:25 PM, Ray Strode wrote:

Hi,

Ahh, okay.

On Tue, Mar 2, 2021 at 9:31 AM Hans de Goede  wrote:

sudo authselect select minimal
sudo authselect apply-changes

Which results in the following /etc/pam.d/fingerprint-auth file:

[hans@x1 linux]$ sudo cat /etc/pam.d/fingerprint-auth
# Generated by authselect on Tue Mar  2 15:24:53 2021
# Do not modify this file manually.


minimal profile does not support fingerprint


So it seems there are 4 profiles:

[hans@x1 ~]$ authselect list
- minimal Local users only for minimal installations
- nis Enable NIS for system authentication
- sssd    Enable SSSD for system authentication (also for local users only)
- winbind Enable winbind for system authentication

What I want is a profile which uses just the good old /etc files to
avoid the overhead of running a local daemon (sssd tends to show up as
one of the top 10 wakeup sources in powertop on an idle system) and I
also don't want a config which tries to go out on the network.

So minimal seems to meet my needs; and although I personally do not
have much of a need for fingerprint auth, I don't really see why we
could not do fingerprint auth with the minimal config. I'm pretty


I'd say the answer is simple - if you go with minimal, you don't need 
fingerprint. And you wrote it yourself - you don't need fingerprint auth. Just 
because something can be done, does not mean it is worth to maintain it. More 
info below.


sure I can manually create a pam-config where this works just fine.

I guess its in the name minimal, where as "local" might be (1) a better


That's the point - it's minimal not local, not without-sssd. The readme 
explicitly says that it reserved for cases when you really care about disk and 
memory footprint.

It has very limited functionality by design. If you do not want to use SSSD, 
you can keep using sssd profile and just disable the service. It will keep 
working. The minimal profile is there for users that also want to remove sssd 
packages to safe resources, but in that case you probably don't care about 
fingerprint and smartcards either.


The problem is that IMHO having sssd enabled by default is really the wrong 
thing to do for like 95% of our users and defaults should be the settings which 
are best for most / almost all users.

This is really just a symptom of a much bigger problem though, which is that we simply 
have way too much services / daemon's starting up by default. The output of "ps 
aux" after a default Fedora workstation install is just way way too long. Once upon 
a time Linux users used to make fun of Windows with all its background processes in the 
mean time a default Fedora WS install has gotten worse then Windows wrt background 
processes. Any of these are totally unnecessary for most of our users.

We really should be smarter here and the config tools which allows a user to 
enroll in an authentication domain enable the sssd config when that happens and 
not have this on by default for everyone.

So what I would really like to see is a local profile which uses just /etc 
files + fprintd if there are fingerprints enrolled. Smartcards are a different 
story, because those likely also need significant extra setup.

Where as fingerprints can easily be enrolled from the local UI tools.


name. Note I'm not suggesting to add another profile just for this
but it would be nice if fingerprint auth would at least be a
(default off) feature for the minimal config.

Shall I file a RFE issue for this at:
https://github.com/authselect/authselect/issues/


If you need fingerprint auth then open the ticket please - but no promises 
here. If you don't need it then just don't open the ticket :-)


Rather then opening a ticket, what I would really like to see is a good 
discussion about why the sssd profile is the default, because IMHO it is a bad 
default for most users.


I hear you. From authselect perspective, SSSD was enabled by default 
through a change page that was accepted by community. Therefore 
authselect is advertising this profile as the main and only. If you want 
to run without sssd, you can disable the service but you don't have to 
switch to other profile.


Whether or not it should be enabled by default is a different 
discussion. But... The SSSD team does acknowledge that it does not have 
to be enabled by default for vast majority of Fedora users and we plan 
to submit a change page that will address this. However, I am not going 
to dive into details in this thread yet, since they are still developing,





Regards,

Hans
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 

Re: Plymouth, themes and console clearing: https://bugzilla.redhat.com/show_bug.cgi?id=1933378

[Oğuz Ersen via devel]

Is changing the default theme from "text" to "details" an option? It is already 
there so there is no need to install another package and I think it is a better 
wall-of-text experience than removing plymouth altogether.

--
Best Regards
Oğuz Ersen
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1935417] perl-HTML-Parser-3.76 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1935417



--- Comment #1 from Fedora Update System  ---
FEDORA-2021-c620c81807 has been submitted as an update to Fedora 34.
https://bodhi.fedoraproject.org/updates/FEDORA-2021-c620c81807


-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1935378] perl-PDF-API2-2.039 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1935378

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[Bug 1935417] perl-HTML-Parser-3.76 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=1935417

Jitka Plesnikova  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-HTML-Parser-3.76-1.fc3
   ||5




-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[rpms/perl-HTML-Parser] PR #2: Tests

[Jitka Plesnikova]

jplesnik merged a pull-request against the project: `perl-HTML-Parser` that you 
are following.

Merged pull-request:

``
Tests
``

https://src.fedoraproject.org/rpms/perl-HTML-Parser/pull-request/2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[rpms/perl-HTML-Parser] PR #2: Tests

[Jitka Plesnikova]

jplesnik opened a new pull-request against the project: `perl-HTML-Parser` that 
you are following:
``
Tests
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-HTML-Parser/pull-request/2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Plymouth, themes and console clearing: https://bugzilla.redhat.com/show_bug.cgi?id=1933378

[Tomasz Torcz]

Dnia Thu, Mar 04, 2021 at 12:14:07PM -0800, Adam Williamson napisał(a):
> Starting from a minimal install with plymouth omitted, adding just
> plymouth itself pulls in 3 packages (plymouth, plymouth-core-libs,
> plymouth-scripts) with an installed size of 621K. Adding plymouth-
> system-theme pulls in 32 packages with an installed size of 24M. So
> putting plymouth-system-theme in @core would substantially inflate the
> size of @core in terms of both number of packages and overall installed
> size. Removing plymouth from @core would not save a lot in terms of
> packages or space.

  plymouth-theme-hot-dog  is only 400 KiB ;)

/ducks

-- 
Tomasz Torcz “God, root, what's the difference?”
to...@pipebreaker.pl   “God is more forgiving.”
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Fedora-Cloud-32-20210305.0 compose check report

[Fedora compose checker]

No missing expected images.

Soft failed openQA tests: 1/7 (x86_64), 1/7 (aarch64)
(Tests completed, but using a workaround for a known bug)

Old soft failures (same test soft failed in Fedora-Cloud-32-20210304.0):

ID: 800427  Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/800427
ID: 800434  Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/800434

Passed openQA tests: 6/7 (x86_64), 6/7 (aarch64)
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Plymouth, themes and console clearing: https://bugzilla.redhat.com/show_bug.cgi?id=1933378

[Hans de Goede]

Hi,

On 3/4/21 11:45 PM, Adam Williamson wrote:
> On Thu, 2021-03-04 at 22:40 +0100, Hans de Goede wrote:
>>
>>> Starting from a minimal install with plymouth omitted, adding just
>>> plymouth itself pulls in 3 packages (plymouth, plymouth-core-libs,
>>> plymouth-scripts) with an installed size of 621K. Adding plymouth-
>>> system-theme pulls in 32 packages with an installed size of 24M. So
>>> putting plymouth-system-theme in @core would substantially inflate the
>>> size of @core in terms of both number of packages and overall installed
>>> size. Removing plymouth from @core would not save a lot in terms of
>>> packages or space.
>>>
>>> So, I guess the question here is, what do we do?
>>>
>>> 1) Remove plymouth from @core
>>> 2) Add plymouth-system-theme to @core
>>> 3) Make Hans/Ray/someone fix the plymouth bug
>>
>> 1) clearly gets my vote, not just because I don't have time to work on 3)
>> but also because to me it seems like the right thing to do. Plymouth is
>> a boot splash, its goal is to make the boot look pretty / hide all the
>> scary log messages in use-cases where we want this.  The text fallback
>> splash is not pretty. In general if it shows instead of the graphical
>> splash the fact that the text fallback shows is considered a bug.
> 
> Well, you could still argue it's prettier than a wall-o-text boot. And
> it *does* hide the wall-o-text.
> 
>> So either the server spin wants a pretty boot and then they should fix the
>> bug of the text splash showing by installing plymouth-system-theme, or the
>> server spin does not want a pretty boot and then there should be no
>> plymouth at all.
> 
> What if we want something arguably-prettier than wall-o-text, but don't
> want an extra 32 packages and 24M of storage used up?

Systemd has you covered here, you can tell it to not log any startup
status or to only log errors by specifying systemd.show_status=no or
systemd.show_status=auto on the kernel commandline.

Note I'm not claiming there is no bug in plymouth (1) here, but I also
believe that dropping plymouth completely from e.g. the server-spin is
the right thing to do.  And that has the nice side effect of significant
lowering the priority of the plymouth bug.  Which I must admit does
make the chance of me actually looking into the plymouth bug a lot smaller.

Regards,

Hans


1) There have been a lot of tty/console code changes in the kernel recently
to deal with a bunch of security issues. I would not be surprised if one of
those turns out to be the root cause.  This makes me wonder how hard it
would be for you to try and reproduce this with the latest F34 rootfs +
a kernel from when openQA did not hit this yet ?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure