test

test@lists.fedoraproject.org

56784 discussions

[f37] (hint) your fstab has been modified, but systemd still uses...
by Felix Miata 18 Sep '22

18 Sep '22

# mountsrv mount: (hint) your fstab has been modified, but systemd still uses the old version; use 'systemctl daemon-reload' to reload. mount: (hint) your fstab has been modified, but systemd still uses the old version; use 'systemctl daemon-reload' to reload. mount: (hint) your fstab has been modified, but systemd still uses the old version; use 'systemctl daemon-reload' to reload. mount: (hint) your fstab has been modified, but systemd still uses the old version; use 'systemctl daemon-reload' to reload. mountsrv is a shell alias to mount 4 noauto nfs mounts that I have used in fstabs since around when nfs V4 went mainstream. Nothing in fstab has been changed WRT nfs mounts. The only changes to fstab are: 1-because of cloning 36 so that the clone could be upgraded to 37 while keeping 36 intact, with only change being related to the / filesystem's new device name, UUID and LABEL post-cloning; and 2-an extra mount during system-upgrade process, for a filesystem mounted to /var/lib/dnf/system-upgrade to prevent exhaustion of freespace by downloading all before installing any. Running systemctl daemon-reload doesn't change anything apparent, or stop the "hints" from recurring after each reboot. Is this a bug? BZ search for "daemon-reload" turned up nothing looking similar. Is there some required new fstab construct I haven't heard about? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

1 0

F37 Final blocker status update
by Ben Cotton 16 Sep '22

16 Sep '22

Fedora Linux 37 Final freeze begins Tuesday 4 October. Action summary ==================== Accepted blockers ----------------- 1. anaconda — Custom partitioning with 2 drives selected, bootloader fails to install due to one drive not having a BIOS Boot partition — ON_QA ACTION: QA to verify FEDORA-2022-c20d42f3bc 2. gnome-contacts — When a single contact is edited, it results in multiple contacts of the same name. — ON_QA ACTION: QA to verify FEDORA-2022-acbfee2ce8 3. gnome-initial-setup — Unable to set up enterprise account with gnome-initial-setup, clicking continue does not join the domain — ASSIGNED ACTION: dgilmore to test https://koji.fedoraproject.org/koji/taskinfo?taskID=92037333 4. gnome-shell — GNOME Initial Setup uses the English keyboard, instead of the default keyboard — ASSIGNED ACTION: Upstream to diagnose and resolve issue 5. gnome-shell — Attempting to disconnect VPN connection from system menu does nothing — VERIFIED ACTION: (none) 6. gnome-software — Can't install a local rpm package anymore, Install button missing (for certain RPMs) — VERIFIED ACTION: (none) 7. greenboot — greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open `/boot/grub2/grubenv.new`: No such file or directory." — NEW ACTION: Maintainers to diagnose issue 8. grub2 — Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader — NEW ACTION: Maintainers to diagnose issue or provide status update 9. mesa — totem: nouveau_pushbuf_data(): totem killed by SIGABRT — NEW ACTION: Maintainers to update mesa with fixes for F37 10. uboot-tools — Regression booting Fedora on rockchip devices installed on PCIe NVME drives — ON_QA ACTION: QA to verify FEDORA-2022-c1d9e8daa9 Proposed blockers ----------------- 1. chrome-gnome-shell — Project name and source repository changed to gnome-browser-connector — NEW ACTION: Reviewer to approve new gnome-browser-connector package. 2. gnome-shell — screencast doesn't record the top layer — NEW ACTION: QA to verify if behavior still exists 3. gnome-shell-extension-background-logo — Update gnome-shell-extension-background-logo to 43.0 — NEW ACTION: Maintainer to update package 4. systemd — Czech qwerty layout configured in anaconda, but qwertz layout used in disk unlock and in VT console — NEW ACTION: kbd maintainers to reconsider the -legacy subpackage split Bug-by-bug detail ============= Accepted blockers ----------------- 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2088113 — ON_QA Custom partitioning with 2 drives selected, bootloader fails to install due to one drive not having a BIOS Boot partition When using custom partitioning on two drives with /boot on a RAID 1 device, the installer only creates one BIOS boot. grub2-install is run against both drives, but the second fails because it has no BIOS boot partition. FEDORA-2022-c20d42f3bc contains a candidate fix. 2. gnome-contacts — https://bugzilla.redhat.com/show_bug.cgi?id=2111003 — ON_QA When a single contact is edited, it results in multiple contacts of the same name. Editing a contact results in the contact being properly updated, but an empty contact is created with the same name. FEDORA-2022-acbfee2ce8 contains a candidate fix. 3. gnome-initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=2123494 — ASSIGNED Unable to set up enterprise account with gnome-initial-setup, clicking continue does not join the domain Initially the buttons were missing. Update FEDORA-2022-50e585b456 fixed that issue, however clicking the button does not joing the domain. Instead, the user is returned to the domain credentials screen, resulting in an endless loop. https://koji.fedoraproject.org/koji/taskinfo?taskID=92037333 contains a backport of upstream's change which may fix it. 4. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2121110 — ASSIGNED GNOME Initial Setup uses the English keyboard, instead of the default keyboard Regardless of the default keyboard setting, g-i-s uses the English keyboard. Relatedly, new users have the English keyboard selected, even though another language is shown as the default. FEDORA-2022-52cdfc7920 failed to fix this issue. 5. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2125252 — VERIFIED Attempting to disconnect VPN connection from system menu does nothing Disabling a VPN doesn't disable the VPN. Fixed in FEDORA-2022-50e585b456. 6. gnome-software — https://bugzilla.redhat.com/show_bug.cgi?id=2124869 — VERIFIED Can't install a local rpm package anymore, Install button missing (for certain RPMs) What it says on the tin. Fixed in FEDORA-2022-b6246d02fa. 7. greenboot — https://bugzilla.redhat.com/show_bug.cgi?id=2121944 — NEW greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open `/boot/grub2/grubenv.new`: No such file or directory." greenboot service fails on a file-not-found error. This also results in rebase tests failing because of conflicts with the rebase triggered by the greenboot failure. 8. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2049849 — NEW Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader Dual-booting recent Windows 10 system with TPM 2.0 fails because bitlocker can't be unsealed by the TPM. This was waived to F37 under the "difficult to fix" exception. No additional updates have been provided. 9. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2123274 — NEW totem: nouveau_pushbuf_data(): totem killed by SIGABRT totem plays ~1 second of video and then crashes. This appears to happen with all video formats. This appears to be an issue in multithreading support in the nouveau driver, which is fixed upstream. The fix is large and may not be suitable for backporting, but would be available in a mesa-22.3 update. 10. uboot-tools — https://bugzilla.redhat.com/show_bug.cgi?id=2124127 — ON_QA Regression booting Fedora on rockchip devices installed on PCIe NVME drives uboot-tools introducted a regression when used with 5.19.x kernels. FEDORA-2022-c1d9e8daa9 contains a candidate fix. Proposed blockers ----------------- 1. chrome-gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2106868 — NEW Project name and source repository changed to gnome-browser-connector Upstream has split this into two packages. Package review pending for renamed package: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2127314 2. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2125439 — NEW screencast doesn't record the top layer Typing and popup windows don't show when recording a screencast. This may be fixed in pipewire-gstreamer-0.3.57-1. 3. gnome-shell-extension-background-logo — https://bugzilla.redhat.com/show_bug.cgi?id=2127192 — NEW Update gnome-shell-extension-background-logo to 43.0 The Fedora logo is not displayed and the package is not compatible with gnome-shell 43. 4. systemd — https://bugzilla.redhat.com/show_bug.cgi?id=2121106 — NEW Czech qwerty layout configured in anaconda, but qwertz layout used in disk unlock and in VT console The wrong keymap is used when unlocking disks or virtual terminals. It looks like this may have never worked. It looks like an issue with how layouts are mapped between console and xkb. Adam is thinking about how to approach this: https://bugzilla.redhat.com/show_bug.cgi?id=2121106#c24 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 0

Re: [Test-Announce] Fedora Linux 37 Beta Release Announcement
by Peter Robinson 16 Sep '22

16 Sep '22

On Tue, Sep 13, 2022 at 3:04 PM Tomas Hrcka <thrcka(a)redhat.com> wrote: > > Fedora Linux 37 Beta Released > ------------------------------------------ > > The Fedora Project is pleased to announce the immediate availability > of Fedora Linux 37 Beta, the next step towards our planned Fedora Linux 37 release > at the end of October. > > Download the prerelease from our Get Fedora site: > * Get Fedora 37 Beta Workstation: https://getfedora.org/workstation/download/ > * Get Fedora 37 Beta Server: https://getfedora.org/server/download/ > * Get Fedora 37 IoT: https://getfedora.org/iot/download/ > > Or, check out one of our popular variants, including KDE Plasma, Xfce, > and other desktop environments, as well as images for ARM devices: > > * Get Fedora 37 Beta Spins: https://spins.fedoraproject.org/prerelease > * Get Fedora 37 Beta Labs: https://labs.fedoraproject.org/prerelease > * Get Fedora 37 Beta ARM: https://arm.fedoraproject.org/prerelease Please drop the arm.fp.o links, they're for ARMv7 which is retired with F-37, all the aarch64 pieces are part of the main getfedora.org site. > ## Beta Release Highlights > > # Gnome 43 > # Retire ARMv7 > # Python 3.11, Perl 5.36, Golang 1.19 > # RPM content is now signed with IMA signatures > > For more details about the release, read the full announcement at > > * https://fedoramagazine.org/announcing-fedora-37-beta/ > > or look for the prerelease pages in the download sections at > > * https://getfedora.org/ > > Since this is a Beta release, we expect that you may encounter bugs or > missing features. To report issues encountered during testing, contact > the Fedora QA team via the test(a)lists.fedoraproject.org mailing list or > in #fedora-qa on Libera Chat or the #qa:fedoraproject.org Matrix room. > > Regards, > Tomas Hrcka, Fedora Release Engineering. > _______________________________________________ > test-announce mailing list -- test-announce(a)lists.fedoraproject.org > To unsubscribe send an email to test-announce-leave(a)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-announce@lists.fedorapro… > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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, report it: https://pagure.io/fedora-infrastructure/new_issue

3 2

Fedora-MATE_Compiz-Live-x86_64-37_Beta-1.5.iso ... Does NOT boot.
by Andre Gompel 14 Sep '22

14 Sep '22

Fedora-MATE_Compiz-Live-x86_64-37_Beta-1.5.iso Does NOT boot. sh256sum says it is "OK" But it does not boot, says methinks like : "file /sbin.sysctl file is missing. Bad ISO it seems. I use a Ventoy formatted USB drive, where other ISO's including Fedora 36 boot OK It may be a bad build. I have not tried any other F37 Beta, only this one. AG

3 2

Re: [Fedocal] Reminder meeting : Prioritized bugs and issues
by Luna Jernberg 14 Sep '22

14 Sep '22

Sorry i missed the meeting today On 9/6/22, Ben Cotton <bcotton(a)redhat.com> wrote: > On Tue, Sep 6, 2022 at 6:00 AM <bcotton(a)redhat.com> wrote: >> >> You are kindly invited to the meeting: >> Prioritized bugs and issues on 2022-09-07 from 10:00:00 to 11:00:00 >> America/Indiana/Indianapolis >> At fedora-meeting-1(a)irc.libera.chat >> >> More information available at: >> https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/ > > There are no nominated or accepted bugs, so the meeting is cancelled. > > > > -- > Ben Cotton > He / Him / His > Fedora Program Manager > Red Hat > TZ=America/Indiana/Indianapolis > _______________________________________________ > triage mailing list -- triage(a)lists.fedoraproject.org > To unsubscribe send an email to triage-leave(a)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/triage@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >

1 0

Re: Thoughts welcome: interface between automated test gating and the "critical path"
by Adam Williamson 13 Sep '22

13 Sep '22

On Fri, 2022-09-02 at 08:37 +0000, Zbigniew Jędrzejewski-Szmek wrote: > > > > Now, because I glued openQA to the critpath because it was handy, there > > are two sets of consequences to a package being in critical path: > > > > 1. Tighter Bodhi requirements > > 2. openQA tests are run, and results gate the update (except Rawhide) > > > > So, one of the implicit questions here is, is it OK to keep twinning > > these two sets of consequences, or should we split them up? Splitting > > them up kinda implies answer 2) from my original mail: "Keep the > > current "critical path" concept but define a broader group > > of "gated packages" somewhere". Because we would then need some new > > concept that isn't "critical path". As I said, that's more *work* - > > it'd require us to write new code in several places[0]. Even if we > > decide it'd be nice to do this, is it nice *enough* to be worth doing > > that work? > > I'd still vote for keeping a single critpath list and using it as > "the list of packages that require extra care and testing". > > As you describe, the original meaning of critpath has shifted, but > it's because the way we do updates and QA has also shifted. Doing > gating tests for a package seems much more useful than just keeping > it longer in 'updates-testing' in hope that somebody discovers an > important regresion in the second week. Well, there's a caveat there - openQA doesn't test everything. On the whole we cover quite a lot with the set of tests that gets run on updates, but there's certainly lots of potential for there to be important bugs it misses, that a human tester might catch. So I think there is still a case for the higher karma requirements too. > > So yeah, I don't think it makes sense to do the extra work to split > the concepts. Also because we have way too many concepts and processes > in Fedora already. On the whole, though, I agree with you. I just don't trust my own opinion because it's obviously biased by what's convenient for me. :D > > If we don't think it's worth doing that work, then we're kinda stuck > > with openQA glomming onto the critpath definition to decide which > > updates to test and gate, because I don't have any other current viable > > choices for that, really. And we'd have to figure out a critpath > > definition that's as viable as possible for both purposes. > > > > > > BTW, one other thought I've had in relation to all this is that we > > could enhance the current critpath definition somewhat. Right now, it's > > built out of package groups in comps which are kinda topic-separated: > > there's a critpath-kde, a critpath-gnome, a critpath-server, and so on. > > But the generated critical path package list is a monolith: it doesn't > > distinguish between a package that's on the GNOME critpath and a > > package that's on the KDE critpath, you just get a big list of all > > critpath packages. It might be nice if we actually did distinguish > > between those - the critpath definition could keep track of which > > critpath topic(s) a package is included in, and Bodhi could display > > that information in the web UI and provide it via the API. That way > > manual testers could get a bit more info on why a package is critpath > > and what areas to test, and openQA could potentially target its test > > runs to conserve resources a bit, though this might require a bit more > > coding work on the gating stuff now I think about it. > > That sounds useful. We only need a volunteer to figure out the details > and do the work ;) I actually did a huge rewrite of the thing that generates the critpath data this week, and it probably wouldn't be tooooo much work, honestly. The most annoying bit would be the Bodhi frontend stuff, but that's because I'm bad at frontend dev in general. :P But yeah, this is definitely off in sky-castle land. I'll add it to my ever-growing list of sky-castle projects to do when I get a couple of years of spare time... -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Re: Release criteria proposal: require GNOME Shell extension install/remove to work
by Adam Williamson 13 Sep '22

13 Sep '22

On Tue, 2022-09-13 at 09:00 -0500, Michael Catanzaro wrote: > I would make the criterion a little more generic than that. E.g. we > don't want to block Fedora release if https://extensions.gnome.org/ > goes down due to a server problem, or if GNOME decides to change the > way extension installation works. For the first part, we can add a footnote clarifying that we expect the site to be working. For the second, if that happens, we can just change the criterion. It's only text. I'm not sure I can write it any more generically without losing all meaning or unexpectedly broadening the scope. For instance if we just say it must be possible to install extensions, what does that *mean*? Is it OK if you can only do it by hacking around with gsettings values manually? Or on the other end of the scale, does it require that *any possible method* of installing extensions works? That just feels too vague to me. Do you have a suggestion for improved wording? -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Release criteria proposal: require GNOME Shell extension install/remove to work
by Adam Williamson 13 Sep '22

13 Sep '22

Hey folks! So a bug came up at today's blocker review meeting: https://bugzilla.redhat.com/show_bug.cgi?id=2106868 it takes a minute to parse, but the tl;dr is that right now in Fedora 37, you can't go to https://extensions.gnome.org and install extensions. We agreed that it doesn't violate any existing release criteria, but to me, this is actually kind of a significant problem. Anecdotally, I get the impression that a lot of our Workstation users do use extensions, and not being able to easily install them on a fresh install would be a big problem for them, and make us look pretty bad. We have a handful of extensions packaged, though I'm not sure how well they're kept up to date. Aside from those, I don't know of any other really practical way for regular users to install extensions besides https://extensions.gnome.org . Is there one? Assuming for now that there isn't, I'm gonna propose this as a Final release criterion to see how people feel about it, to come after "Default panel functionality": ##### === GNOME extensions === On Fedora Workstation, it must be possible to install and remove extensions by visiting https://extensions.gnome.org in the default web browser, after installing the required browser extension. ##### Do folks think this is important enough to block Final release on? Desktop folks, do you consider it "supportable"? Thanks! -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

8 14

Re: [Test-Announce] 2022-09-12 @ 15:00 UTC - Fedora QA Meeting
by Luna Jernberg 12 Sep '22

12 Sep '22

Won't have time to attend this or the Blocker Review meeting as i have other plans on Monday On 9/10/22, Adam Williamson <adamwill(a)fedoraproject.org> wrote: > # Fedora Quality Assurance Meeting > # Date: 2022-09-12 > # Time: 15:00 UTC > (https://fedoraproject.org/wiki/Infrastructure/UTCHowto) > # Location: #fedora-meeting on irc.libera.chat > > Greetings testers! > > We didn't meet for a couple of weeks, and the Beta release has been > signed off, so let's get together and check in. > > If anyone has any other items for the agenda, please reply to this > email and suggest them! Thanks. > > == Proposed Agenda Topics == > > 1. Previous meeting follow-up > 2. Fedora 37 Beta check-in and final steps > 3. Fedora CoreOS release criteria / test case revisions > 4. Test Day / community event status > 5. Open floor > -- > Adam Williamson > Fedora QA > IRC: adamw | Twitter: adamw_ha > https://www.happyassassin.net > > _______________________________________________ > test-announce mailing list -- test-announce(a)lists.fedoraproject.org > To unsubscribe send an email to test-announce-leave(a)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-announce@lists.fedorapro… > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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, report it: > https://pagure.io/fedora-infrastructure/new_issue >

1 2

2022-09-12 - Fedora QA Meeting - Minutes
by Adam Williamson 12 Sep '22

12 Sep '22

================================== #fedora-meeting: Fedora QA meeting ================================== Meeting started by adamw at 15:00:04 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2022-09-12/fedora-qa.2022-… . Meeting summary --------------- * Roll Call (adamw, 15:00:12) * Previous meeting follow-up (adamw, 15:07:56) * no action items from previous meeting (adamw, 15:08:11) * Fedora 37 Beta check-in and final steps (adamw, 15:13:34) * ACTION: adamw to work on F37 Beta common issues (adamw, 15:19:32) * LINK: https://getfedora.org/en/iot/download/ (SumantroMukherje, 15:38:48) * Fedora CoreOS release criteria / test case revisions (adamw, 15:45:57) * adamw, sumantro and dustymabe are working on release criteria and test coverage for CoreOS at https://github.com/coreos/fedora-coreos-tracker/issues/1239 (adamw, 15:58:21) * Test Day / community event status (adamw, 15:58:31) * GNOME and i18n test weeks are ongoing: https://fedoraproject.org/wiki/Test_Day:2022-09-07_Fedora_37_GNOME_43_Final , https://fedoraproject.org/wiki/Test_Day:2022-09-06_I18N_Test_Day (adamw, 16:11:38) * IoT test week is next week: https://pagure.io/fedora-qa/issue/710 (adamw, 16:12:14) * upgrade, virt, and GNOME apps test events are all upcoming (adamw, 16:12:28) * Open floor (adamw, 16:12:30) Meeting ended at 16:21:12 UTC. Action Items ------------ * adamw to work on F37 Beta common issues Action Items, by person ----------------------- * adamw * adamw to work on F37 Beta common issues * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * adamw (82) * kparal (35) * SumantroMukherje (14) * zodbot (11) * coremodule (11) * lruzicka (11) * nirik (4) * bcotton (3) * AhmedA (2) * pboy (1) * tflink[m] (1) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

test