Re: toolbox not working after upgrade to 40

On 3/28/24 2:32 AM, Adam Williamson wrote: It's not generally necessary, but if we wanted to get this fix into F40 Final and it did not land before Final freeze on Tuesday, it would need an FE bug. Despite 6 other bugs being classified as a duplicate of this one, the bug has not received a lot

Re: toolbox not working after upgrade to 40

On Wed, 2024-03-27 at 15:32 +1100, Ian Laurie wrote: > On 3/27/24 3:11 PM, Ian Laurie wrote: > > Upstream bug: > > > > https://github.com/containers/toolbox/issues/1348 > > Given that there is an upstream bug, and my toolbox test day results > link to it, do you still want me to file a RHBZ as

Re: toolbox not working after upgrade to 40

On 3/27/24 3:11 PM, Ian Laurie wrote: Upstream bug: https://github.com/containers/toolbox/issues/1348 Given that there is an upstream bug, and my toolbox test day results link to it, do you still want me to file a RHBZ as well? -- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney

Re: toolbox not working after upgrade to 40

On 3/27/24 2:15 PM, Sumantro Mukherjee wrote: Hey Ian, I have upgraded from F39 to F40 and followed the steps you did, I can't replicate this error. Here's my log https://paste.centos.org/view/61931a20 I have found the underlying problem. "If a user

Re: toolbox not working after upgrade to 40

Hey Ian, I have upgraded from F39 to F40 and followed the steps you did, I can't replicate this error. Here's my log https://paste.centos.org/view/61931a20 On Wed, Mar 27, 2024 at 8:36 AM Sumantro Mukherjee wrote: > Can you please report this for the test day here >

Re: toolbox not working after upgrade to 40

Can you please report this for the test day here https://testdays.fedoraproject.org/events/181 and also file an issue at RHBZ under toolbox On Wed, Mar 27, 2024 at 8:25 AM Ian Laurie wrote: > I can create containers in toolbox but cannot enter them anymore. > > I issued a "podman system reset",

toolbox not working after upgrade to 40

I can create containers in toolbox but cannot enter them anymore. I issued a "podman system reset", followed by "toolbox create" and "toolbox enter" but I still get "Error: failed to start container fedora-toolbox-40". This is the first time trying to enter a container since upgrading from 39

Re: 39 to 40 upgrade report

as of today both bugs seems to be fixed. the last one with glib2-2.80.0-1.fc40.x86_64 -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: 39 to 40 upgrade report

in case someone want to move to F40 too 2 Bugs: thunderbird on gnome Xorg https://gitlab.gnome.org/GNOME/mutter/-/issues/3329 gnome-extensions-app: https://bugzilla.redhat.com/show_bug.cgi?id=2268929 -- ___ test mailing list --

39 to 40 upgrade report

all smooth (here) Thanks !!! -- ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List

Re: Fedora 39 to 40 upgrade experience

On Fri, 2024-02-16 at 11:29 +1100, Ian Laurie wrote: > On 2/16/24 4:20 AM, Adam Williamson wrote: > > Before removing it, it would be useful if you could try and figure out > > what pulled it in. Does anything suggests: or recommends: it, or does > > it enhances: or supplements: anything else? >

Re: Fedora 39 to 40 upgrade experience

On 2/16/24 4:20 AM, Adam Williamson wrote: Before removing it, it would be useful if you could try and figure out what pulled it in. Does anything suggests: or recommends: it, or does it enhances: or supplements: anything else? I'm going to need help wielding that sort of command line magic.

Re: Fedora 39 to 40 upgrade experience

On Thu, Feb 15, 2024 at 3:03 PM Felix Miata wrote: > > Ian Laurie composed on 2024-02-15 18:05 (UTC+1100): > > > (2) Password needed to be updated as per what happened with Rawhide a > > few weeks ago ~ login warning about my password expiring (it was set to > > never expire). I'm guessing a

Re: Fedora 39 to 40 upgrade experience

Ian Laurie composed on 2024-02-15 18:05 (UTC+1100): > (2) Password needed to be updated as per what happened with Rawhide a > few weeks ago ~ login warning about my password expiring (it was set to > never expire). I'm guessing a file format changed somewhere? I've done at least 3 upgrades

Re: Fedora 39 to 40 upgrade experience

On Thu, 2024-02-15 at 18:05 +1100, Ian Laurie wrote: > Yes I know we're just a day from the branch... but I upgraded an Xfce > workstation/Intranet server today to see how things would go. A few > observations: > > (1) The upgrade required the --allowerasing option which unin

Fedora 39 to 40 upgrade experience

Yes I know we're just a day from the branch... but I upgraded an Xfce workstation/Intranet server today to see how things would go. A few observations: (1) The upgrade required the --allowerasing option which uninstalled intel-media-driver from RPM Fusion due to a conflict with a related Fedora

Re: [Fedora Rawhide][x86 MacBook] Can’t boot after dnf system-upgrade 39 to Rawhide

> Can you display the GRUB menu (listing all the installed kernels), when you > repeatedly press F8 after starting the laptop? I tried, and as far as I could tell repeatedly pressing F8 did not display the GRUB menu. I started pressing as soon as I selected the partition. > (A question is

Re: [Fedora Rawhide][x86 MacBook] Can’t boot after dnf system-upgrade 39 to Rawhide

On Wed, Oct 18, 2023 at 7:37 PM Osama Albahrani via test < test@lists.fedoraproject.org> wrote: > Hi! > > I wanted to test Fedora Rawhide so I ran `dnf system-upgrade download > --releasever rawhide --exclude=sdubby` (as per > https://bugzilla.redhat.com/show_bug.cgi?id=22

[Fedora Rawhide][x86 MacBook] Can’t boot after dnf system-upgrade 39 to Rawhide

Hi! I wanted to test Fedora Rawhide so I ran `dnf system-upgrade download --releasever rawhide --exclude=sdubby` (as per https://bugzilla.redhat.com/show_bug.cgi?id=2243872#c12) to upgrade from Fedora 39 and it finished successfully. However after I ran `dnf system-upgrade reboot` and got a black

[Test-Announce] Fedora 39 Upgrade Test Day is underway!

Hey All, As we come closer to Fedora 39 release dates, it's time to test upgrades. Fedora 39 has a lot of changesets and it becomes essential that we test the graphical upgrade methods as well as the command line. As a part of this test day[0], we will test upgrading from a full updated, F37

Fedora 39 Upgrade Test Day is underway!

Hey All, As we come closer to Fedora 39 release dates, it's time to test upgrades. Fedora 39 has a lot of changesets and it becomes essential that we test the graphical upgrade methods as well as the command line. As a part of this test day[0], we will test upgrading from a full updated, F37

Re: Question to F39 who did a new install apart upgrade

> On Mon, 02 Oct 2023 17:03:12 - ... > > Given your data, I don't think either of these is your issue. I'm out > of ideas. anyway, thanks for support ! ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to

Re: Question to F39 who did a new install apart upgrade

On Mon, 02 Oct 2023 17:03:12 - "old sixpack13" wrote: > > On Sat, 30 Sep 2023 17:50:31 - > > "old sixpack13" > > > > > This is just a wild guess, but the tzdata package was recently > > dropped as required by some packages. Is it possible some fallout > > from this is the source of

Re: Question to F39 who did a new install apart upgrade

> On Sat, 30 Sep 2023 17:50:31 - > "old sixpack13" > > This is just a wild guess, but the tzdata package was recently dropped > as required by some packages. Is it possible some fallout from this is > the source of your problem? Do you have the tzdata package(s) > installed? > rpm

Re: Question to F39 who did a new install apart upgrade

On Sat, 30 Sep 2023 17:50:31 - "old sixpack13" wrote: > > On Thu, 2023-09-28 at 09:28 +0200, František Šumšal wrote: > > > > It looks like they are in 254.5, which is on its way to > > updates-testing for F39 now: > > https://bodhi.fedoraproject.org/updates/FEDORA-2023-3355cdb0a8 > >

Re: Question to F39 who did a new install apart upgrade

> On Thu, 2023-09-28 at 09:28 +0200, František Šumšal wrote: > > It looks like they are in 254.5, which is on its way to updates-testing > for F39 now: > https://bodhi.fedoraproject.org/updates/FEDORA-2023-3355cdb0a8 unfortunately, nit fixed with 254.5-2.fc39 still seeing: - journal: Realtime

Re: Question to F39 who did a new install apart upgrade

> > It looks like they are in 254.5, which is on its way to updates-testing > for F39 now: Thanks ! ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: Question to F39 who did a new install apart upgrade

On Thu, 2023-09-28 at 09:28 +0200, František Šumšal wrote: > On 9/28/23 01:11, old sixpack13 wrote: > > > On 9/27/23 17:44, old sixpack13 wrote: > > > > > > I don't know what is the exact journal message you're seeing, but [0] > > > (and [1]) > > > might be related. > > > > > > [0]

Re: Question to F39 who did a new install apart upgrade

> On 9/28/23 01:11, old sixpack13 wrote: > > As far as I know yes, the potential fixes from [1] are not in any released or > stable > systemd version. Okay, thanks for input/Clarification ___ test mailing list -- test@lists.fedoraproject.org To

Re: Question to F39 who did a new install apart upgrade

On 9/28/23 01:11, old sixpack13 wrote: On 9/27/23 17:44, old sixpack13 wrote: I don't know what is the exact journal message you're seeing, but [0] (and [1]) might be related. [0] https://github.com/systemd/systemd/issues/28250 [1] https://github.com/systemd/systemd/pull/29017 Exact !

Re: Question to F39 who did a new install apart upgrade

> On 9/27/23 17:44, old sixpack13 wrote: > > I don't know what is the exact journal message you're seeing, but [0] (and > [1]) > might be related. > > [0] https://github.com/systemd/systemd/issues/28250 > [1] https://github.com/systemd/systemd/pull/29017 Exact ! remaining question: is it in

Re: Question to F39 who did a new install apart upgrade

On 9/27/23 17:44, old sixpack13 wrote: since F38 it happens to me that the dir for the journals is filled up with a lot of small journals (~5 MB) and something regarding time I don't know what is the exact journal message you're seeing, but [0] (and [1]) might be related. [0]

Re: Question to F39 who did a new install apart upgrade

well, grandpa sixpack s/Question to F39/Question to F39 users/ ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct:

Question to F39 who did a new install apart upgrade

since F38 it happens to me that the dir for the journals is filled up with a lot of small journals (~5 MB) and something regarding time Is this still the case with F39 *new* installs (explicit *NOT* upgrades, e.g. F38 => F39) ___ test mailing list --

Re: system-upgrade on RPi fails

On Mon, Aug 21, 2023 at 2:06 PM Alessio wrote: > > Hello. > I don't remember if it has always been this way. > I was trying to upgrade from Fedora 38 to 39 on a Raspberry. > sudo dnf system-upgrade download --releasever=39 > > The point is that on the subsequent boot, f

system-upgrade on RPi fails

Hello. I don't remember if it has always been this way. I was trying to upgrade from Fedora 38 to 39 on a Raspberry. sudo dnf system-upgrade download --releasever=39 The point is that on the subsequent boot, following  dnf system-upgrade reboot the operation fails because the signature

Re: Post 38 to 39 upgrade cannot launch QEMU/KVM VMs via virt-manager

On 8/19/23 00:49, Adam Williamson wrote: Can you file a bug against libvirt on this, with details of how you upgraded? Can you also check the DNF logs and see if there's any relevant-looking output during the upgrade indicating that maybe a scriptlet went wrong? OK done: https

Re: Post 38 to 39 upgrade cannot launch QEMU/KVM VMs via virt-manager

gt; > sudo systemctl enable virtqemud > sudo systemctl start virtqemud > > I think this needs to be looked into. Before the upgrade stuff was > working fine. Can you file a bug against libvirt on this, with details of how you upgraded? Can you also check the DNF logs and

Re: Post 38 to 39 upgrade cannot launch QEMU/KVM VMs via virt-manager

as the reported problem I also had to do this: sudo systemctl enable virtqemud sudo systemctl start virtqemud I think this needs to be looked into. Before the upgrade stuff was working fine. -- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney

Re: Post 38 to 39 upgrade cannot launch QEMU/KVM VMs via virt-manager

On 8/18/23 11:40, Ian Laurie wrote: I upgraded a 38 workstation/server from 38 to 39.  The only casualty so far seems to be that virt-manager can no longer launch VMs. Trying to do so results in this: Error starting domain: Failed to connect socket

Post 38 to 39 upgrade cannot launch QEMU/KVM VMs via virt-manager

=== Can anyone offer some insight before I create a BZ for this? I suspect it is an upgrade issue maybe? Thanks, Ian -- Ian Laurie FAS: nixuser | IRC: nixuser TZ: Australia/Sydney ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe s

[Test-Announce] Fedora 38 Upgrade Test Day 2023-03-28

Hey All, As we come closer to Fedora 38 release dates, it's time to test upgrades. Fedora 38 has a lot of changesets and it becomes essential that we test the graphical upgrade methods as well as the command line. As a part of this test day[0], we will test upgrading from a full updated, F36

Fedora 38 Upgrade Test Day 2023-03-28

Hey All, As we come closer to Fedora 38 release dates, it's time to test upgrades. Fedora 38 has a lot of changesets and it becomes essential that we test the graphical upgrade methods as well as the command line. As a part of this test day[0], we will test upgrading from a full updated, F36

Re: How do I upgrade from F37 to Branched (F38)?

to rawhide. I'm gonna let it go for now.  None of this is on a production machine, anyway. I just did a system-upgrade to 38 branch on another PC. When it was all over, I tried dnf makecache followed by dnf upgrade. The proposal was to upgrade 6 fedora* packages to 39-0.1 versions. For now I've

Re: How do I upgrade from F37 to Branched (F38)?

g to rawhide. > > > I'm gonna let it go for now.  None of this is on a production machine, > > > anyway. > > I just did a system-upgrade to 38 branch on another PC. When it was all > > over, I > > tried dnf makecache followed by dnf upgrade. The proposal was to

Re: How do I upgrade from F37 to Branched (F38)?

a system-upgrade to 38 branch on another PC. When it was all over, I tried dnf makecache followed by dnf upgrade. The proposal was to upgrade 6 fedora* packages to 39-0.1 versions. For now I've simply added fedora-re*39* to exclude= in dnf.conf. Yeah, sounds like we've got a bug

Re: How do I upgrade from F37 to Branched (F38)?

Scott Beamer composed on 2023-02-12 18:11 (UTC-0800): > I just now did a fresh install of the latest branched version, and the > repos are still pointing to rawhide. > I'm gonna let it go for now.  None of this is on a production machine, > anyway. I just did a system-upgrade

Re: How do I upgrade from F37 to Branched (F38)?

On 2/12/23 4:50 PM, Felix Miata wrote: Scott Beamer composed on 2023-02-12 15:09 (UTC-0800): Felix Miata wrote: Scott Beamer composed on 2023-02-12 09:22 (UTC-0800): My attempts to upgrade landed me in Rawhide instead of Branched. My last one, on a Core2Duo, did too, but I caught

Re: How do I upgrade from F37 to Branched (F38)?

Scott Beamer composed on 2023-02-12 15:09 (UTC-0800): > Felix Miata wrote: >> Scott Beamer composed on 2023-02-12 09:22 (UTC-0800): >>> My attempts to upgrade landed me in Rawhide instead of Branched. >> My last one, on a Core2Duo, did too, but I caught it right awa

Re: How do I upgrade from F37 to Branched (F38)?

On 2/12/2023 10:24 AM, Felix Miata wrote: Scott Beamer composed on 2023-02-12 09:22 (UTC-0800): My attempts to upgrade landed me in Rawhide instead of Branched. My last one, on a Core2Duo, did too, but I caught it right away and fixed the repo configs with dnf config-manager IIRC followed

Re: How do I upgrade from F37 to Branched (F38)?

Scott Beamer composed on 2023-02-12 09:22 (UTC-0800): > My attempts to upgrade landed me in Rawhide instead of Branched. My last one, on a Core2Duo, did too, but I caught it right away and fixed the repo configs with dnf config-manager IIRC followed by simply dnf upgrade --releasever=38 --s

How do I upgrade from F37 to Branched (F38)?

Greetings. My attempts to upgrade landed me in Rawhide instead of Branched. I know I've been successful in the past with these types of upgrades, but I don't recall how I did it, and Googling hasn't given me the answer. TIA Scott ___ test mailing

Re: What to do after a system crash during dnf upgrade

On Sun, 2023-01-29 at 02:40 +, George R Goffe via test wrote: > Hi, > > Running dnf upgrade during periods of system instability seems to > leave the system in an unknown state. > > How does one recover from this situation? > checkdupes: package-cleanup --dupes packa

Re: What to do after a system crash during dnf upgrade

On Sun, 29 Jan 2023, George R Goffe via test wrote: Running dnf upgrade during periods of system instability seems to leave the system in an unknown state. How does one recover from this situation? I believe the standard advice is to make a backup and reinstall. Making a backup likely

Re: What to do after a system crash during dnf upgrade

On Sun, 29 Jan 2023 02:40:58 + (UTC) George R Goffe via test wrote: > Running dnf upgrade during periods of system instability seems to > leave the system in an unknown state. > > How does one recover from this situation? I assume you are on rawhide, since you are asking on t

What to do after a system crash during dnf upgrade

Hi, Running dnf upgrade during periods of system instability seems to leave the system in an unknown state. How does one recover from this situation? Best regards, George... ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send

First glance issues after upgrade (Nautilus & display properties)

After upgrading from Fedora 36 testing to Fedora 37 testing the following first glance issues appeared: Display: The desktop wallpaper was lost; monitor refresh rate had to be readjusted. Nautilus (43.0-1.fc37): Column settings were lost; there seems to be a scrolling issue; the star column

Re: Upgrade blocker /usr/bin/WebKitWebDriver

That was the problem. I enabled the testing repo and the upgrade process finished successfully. Thank you ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct

Re: Upgrade blocker /usr/bin/WebKitWebDriver

On Fri, Sep 23, 2022 at 12:12 PM RS wrote: > When trying to upgrade to Fedora 37 Beta with the system-upgrade Plugin > like so: > > sudo dnf system-upgrade download --releasever=37 > > I get the following error: > > Error: Transaction test error: > file /usr/bin/W

Re: Upgrade blocker /usr/bin/WebKitWebDriver

I tried the suggested additional arguments but it didn´t change the output. Maybe it is helpful to add that the testing machine uses the updates-testing repository like so: dnf update --enablerepo=updates-testing ___ test mailing list --

Re: Upgrade blocker /usr/bin/WebKitWebDriver

Hello, have you fully updated your system before trying to perform the upgrade? The recommended workflow is: 1. dnf update --refresh 2. dnf system-upgrade download --releasever=37 You might want to use the following arguments with the second command that will remove conflicting packages

Upgrade blocker /usr/bin/WebKitWebDriver

When trying to upgrade to Fedora 37 Beta with the system-upgrade Plugin like so: sudo dnf system-upgrade download --releasever=37 I get the following error: Error: Transaction test error: file /usr/bin/WebKitWebDriver from install of webkit2gtk4.1-2.37.91-1.fc37.x86_64 conflicts with file

Re: Upgrade upgrade-testing Of kf5-akonadi-mime Fails

On Saturday, May 21, 2022 2:34:53 AM EDT Samuel Sieb wrote: > On 2022-05-20 15:23, Garry T. Williams wrote: > > Anyone know what I managed to mess up here? > > > > Update using updates-testing gives this error: > > > > Error: Transaction test error: > >file

Re: Upgrade upgrade-testing Of kf5-akonadi-mime Fails

On Fri, 20 May 2022 23:34:53 -0700 Samuel Sieb wrote: > On 2022-05-20 15:23, Garry T. Williams wrote: > > Anyone know what I managed to mess up here? > > > > Update using updates-testing gives this error: > > > > Error: Transaction test error: > >file

Re: Upgrade upgrade-testing Of kf5-akonadi-mime Fails

On 2022-05-20 15:23, Garry T. Williams wrote: Anyone know what I managed to mess up here? Update using updates-testing gives this error: Error: Transaction test error: file /usr/share/config.kcfg/specialmailcollections.kcfg from install of kf5-akonadi-mime-22.04.1-1.fc36.x86_64 conflicts

Upgrade upgrade-testing Of kf5-akonadi-mime Fails

Anyone know what I managed to mess up here? Update using updates-testing gives this error: Error: Transaction test error: file /usr/share/config.kcfg/specialmailcollections.kcfg from install of kf5-akonadi-mime-22.04.1-1.fc36.x86_64 conflicts with file from package

Re: dnf system-upgrade conflict

On Fri, 2022-03-04 at 07:14 -0500, Neal Gompa wrote: > > It is planned to fix it: https://pagure.io/fesco/issue/2765 Oh. Great. Thank you. A. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to

Re: dnf system-upgrade conflict

On Fri, Mar 4, 2022 at 6:46 AM Alessio wrote: > > It is not the first time that performing a system-upgrade from 35 to > 36, I get: > > Error: > Problem: problem with installed package mlocate-0.26-31.fc35.x86_64 > - package plocate-1.1.15-2.fc36.x86_64 conflicts wi

dnf system-upgrade conflict

It is not the first time that performing a system-upgrade from 35 to 36, I get: Error: Problem: problem with installed package mlocate-0.26-31.fc35.x86_64 - package plocate-1.1.15-2.fc36.x86_64 conflicts with mlocate provided by mlocate-0.26-46.fc36.x86_64 - mlocate-0.26-31.fc35.x86_64 does

Re: Bug 1949417 - Fedora 34 does not boot after upgrade (edit)

On Wed, Dec 8, 2021 at 8:28 AM wrote: Hi Joe, > I just tested this and it now works correctly. Can I > makr it as closed? Since you're the person who originally reported it, please feel free to close it. (CLOSED->CURRENTRELEASE). If you have any trouble with that, please let me know directly

Bug 1949417 - Fedora 34 does not boot after upgrade (edit)

Hi Folks, I just tested this and it now works correctly. Can I makr it as closed? Joe Pesco ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: system-upgrade blocked by grubby/grub2-tools-minimal

> >>>> # rpm -qa | egrep 'grub|prober|shim' > >>>> # > > > >>>> This F34 installation has no need of any bootloader. Yet: > >>>> # dnf system-upgrade download --releasever=35 --skip-broken > --allowerasing --best > >>&

Re: system-upgrade blocked by grubby/grub2-tools-minimal

On 10/27/21 17:02, Felix Miata wrote: Chris Murphy composed on 2021-10-27 19:40 (UTC-0400): Adam Williamson wrote: On Wed, 2021-10-27 at 02:32 -0400, Felix Miata wrote: # rpm -qa | egrep 'grub|prober|shim' # This F34 installation has no need of any bootloader. Yet: # dnf system-upgrade

Re: system-upgrade blocked by grubby/grub2-tools-minimal

Chris Murphy composed on 2021-10-27 19:40 (UTC-0400): > Adam Williamson wrote: >> On Wed, 2021-10-27 at 02:32 -0400, Felix Miata wrote: >>> # rpm -qa | egrep 'grub|prober|shim' >>> # >>> This F34 installation has no need of any bootloader. Yet: >>>

Re: system-upgrade blocked by grubby/grub2-tools-minimal

On Wed, Oct 27, 2021 at 6:12 PM Adam Williamson wrote: > > On Wed, 2021-10-27 at 02:32 -0400, Felix Miata wrote: > > # rpm -qa | egrep 'grub|prober|shim' > > # > > > > This F34 installation has no need of any bootloader. Yet: > > # dnf system-upgrade do

Re: system-upgrade blocked by grubby/grub2-tools-minimal

On Wed, 2021-10-27 at 02:32 -0400, Felix Miata wrote: > # rpm -qa | egrep 'grub|prober|shim' > # > > This F34 installation has no need of any bootloader. Yet: > # dnf system-upgrade download --releasever=35 --skip-broken --allowerasing > --best > ... > Error: > Prob

Re: system-upgrade blocked by grubby/grub2-tools-minimal

On Wed, Oct 27, 2021 at 2:32 AM Felix Miata wrote: > > # rpm -qa | egrep 'grub|prober|shim' > # > > This F34 installation has no need of any bootloader. Yet: > # dnf system-upgrade download --releasever=35 --skip-broken --allowerasing > --best > ... > Error: > P

system-upgrade blocked by grubby/grub2-tools-minimal

# rpm -qa | egrep 'grub|prober|shim' # This F34 installation has no need of any bootloader. Yet: # dnf system-upgrade download --releasever=35 --skip-broken --allowerasing --best ... Error: Problem: package grubby-8.40-55.fc35.x86_64 requires grub2-tools-minimal, but none of the providers can

[Test-Announce] Fedora 35 Upgrade Test Day 2021-10-07

Hey All, As we come closer to Fedora 35 release dates, it's time to test upgrades. Fedora 35 has a lot of changesets [0] and it becomes essential that we test the graphical upgrade methods as well as the command line. As a part of this test day[1], we will test upgrading from a full updated, F33

Fedora 35 Upgrade Test Day 2021-10-07

Hey All, As we come closer to Fedora 35 release dates, it's time to test upgrades. Fedora 35 has a lot of changesets [0] and it becomes essential that we test the graphical upgrade methods as well as the command line. As a part of this test day[1], we will test upgrading from a full updated, F33

Fedora 35 Testing Upgrade Day #2 2021

Hey! Updated a VM now with the latest 34 Respin ISO from September to 35 and it worked fine :) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct:

attempting to upgrade apitrace on fc35 system gives error messages

Howdy, It seems like I've been seeing this set of error messages for several weeks. I'm running an otherwise up to date FC35 (x86_64) system. Can I provide information related to this system and apitrace"*"? Best regards, George... Running transaction check Error: transaction check vs

Re: tty broken after "latest" upgrade

behaviour implies that one or more recent packages in rawhide repositories have bugs. Has anyone experienced this recently? Perhaps I should investigate further. Regards Onyeibo On Sun, 25 Apr 2021 21:38:59 + (UTC) George R Goffe via test wrote: > Hi, > > I ran a system upgr

tty broken after "latest" upgrade

Hi, I ran a system upgrade late last night and at reboot noticed a major problem with tty (possibly). I run this system with the multi-user target active, which means I get a text based invitation to login and have to start X manually. This is NOT a new change. Instead of seeing text

Re: F33 upgrade to F34 fails to boot on VMWare Fusion

> On 6 Apr 2021, at 14:37, Sergio Correia wrote: > > Hi, > > On Sat, Apr 3, 2021 at 5:36 AM Barry Scott wrote: >> >> I have a working F33 VM that I run using VMWare Fusion 12.1.1. >> >> I used dnf system-upgrade download/reboot to do the upgrade. >

Re: F33 -> F34 upgrade resulted in unbootable system

9) chroot /mnt/fedora 10) mount boot volumes mount /boot mount /boot/efi 11) upgrade dracut dnf upgrade --advisory=FEDORA-2021-50707f8501 12) rebuild initrd - you should check your using the versions your system boots from dracut --force /boot/initramfs-5.11.12-300.fc34.x86_64.img 5.11.12

Re: F33 -> F34 upgrade resulted in unbootable system

Hi, On Wed, Apr 14, 2021 at 9:42 AM Jeb Wilkins wrote: [snip] > [ OK ] Reached target: Local encrypted volumes > [ <=> ] A start job is running for /dev/mapper/. (Xmin Ys / no limit) > This seems like the issue this dracut update resolves:

F33 -> F34 upgrade resulted in unbootable system

>> Repost from users@ since I was advised this is the correct place I thought I'd test the F34 upgrade to look for bugs but its resulted in an non-booting laptop. I've a fairly stock Fedora install on a Dell XPS 13 developer edition. The latop was originally an ubuntu install, its g

Re: Fedora 34 Upgrade Test Day 2021-04-07

ect: Re: Fedora 34 Upgrade Test Day 2021-04-07 > To: For testing and quality assurance of Fedora releases < > test@lists.fedoraproject.org>, > > > Having some spare time today, so testing out in Virtualbox currently so > far an upgrade from Fedora 33 -> 34 via DNF has gon

Re: Fedora 34 Upgrade Test Day 2021-04-07

Having some spare time today, so testing out in Virtualbox currently so far an upgrade from Fedora 33 -> 34 via DNF has gone fine other then a GNOME 40 bug On Mon, Apr 5, 2021 at 9:01 PM Sumantro Mukherjee wrote: > Hey All, > > As we come closer to Fedora 34 release dates, it's

Re: F33 upgrade to F34 fails to boot on VMWare Fusion

On Tue, Apr 6, 2021 at 3:31 PM Barry Scott wrote: > > > Its this BLS entry: > > # more 084dd537129740f79629efc0ef6893f7-5.11.11-200.fc33.x86_64.conf > title Fedora (5.11.11-200.fc33.x86_64) 33 (Thirty Three) > version 5.11.11-200.fc33.x86_64 > linux /vmlinuz-5.11.11-200.fc33.x86_64 > initrd

Re: F33 upgrade to F34 fails to boot on VMWare Fusion

> On 6 Apr 2021, at 13:31, Marc Dionne wrote: > > On Sat, Apr 3, 2021 at 5:32 AM Barry Scott wrote: >> >> I have a working F33 VM that I run using VMWare Fusion 12.1.1. >> >> I used dnf system-upgrade download/reboot to do the upgrade. >> >> Whe

Re: F33 upgrade to F34 fails to boot on VMWare Fusion

> On 6 Apr 2021, at 13:31, Marc Dionne wrote: > > On Sat, Apr 3, 2021 at 5:32 AM Barry Scott wrote: >> >> I have a working F33 VM that I run using VMWare Fusion 12.1.1. >> >> I used dnf system-upgrade download/reboot to do the upgrade. >> >> Whe

Re: F33 upgrade to F34 fails to boot on VMWare Fusion

Hi, On Sat, Apr 3, 2021 at 5:36 AM Barry Scott wrote: > > I have a working F33 VM that I run using VMWare Fusion 12.1.1. > > I used dnf system-upgrade download/reboot to do the upgrade. > > When the VM rebooted I see it stuck: > > [ OK ] Finished Wait for udev To COmplet

Re: F33 upgrade to F34 fails to boot on VMWare Fusion

On Sat, Apr 3, 2021 at 5:32 AM Barry Scott wrote: > > I have a working F33 VM that I run using VMWare Fusion 12.1.1. > > I used dnf system-upgrade download/reboot to do the upgrade. > > When the VM rebooted I see it stuck: > > [ OK ] Finished Wait for udev To COmplet

[Test-Announce] Fedora 34 Upgrade Test Day 2021-04-07

Hey All, As we come closer to Fedora 34 release dates, it's time to test upgrades. Fedora 34 has a lot of changesets [0] and it becomes essential that we test the graphical upgrade methods as well as the command line. As a part of this test day[1], we will test upgrading from a full updated, F32

Fedora 34 Upgrade Test Day 2021-04-07

Hey All, As we come closer to Fedora 34 release dates, it's time to test upgrades. Fedora 34 has a lot of changesets [0] and it becomes essential that we test the graphical upgrade methods as well as the command line. As a part of this test day[1], we will test upgrading from a full updated, F32

Re: F33 upgrade to F34 fails to boot on VMWare Fusion

> On 3 Apr 2021, at 09:32, Barry Scott wrote: > > I have a working F33 VM that I run using VMWare Fusion 12.1.1. > > I used dnf system-upgrade download/reboot to do the upgrade. > > When the VM rebooted I see it stuck: > > [ OK ] Finished Wait for udev To COmp

F33 upgrade to F34 fails to boot on VMWare Fusion

I have a working F33 VM that I run using VMWare Fusion 12.1.1. I used dnf system-upgrade download/reboot to do the upgrade. When the VM rebooted I see it stuck: [ OK ] Finished Wait for udev To COmplete Deveice initialization [ *** ] (2 of 2) A start job is running for /dev/mapp

Upgrade on F34 -> F34 on x11 utils split

Hey all, I attempted to do a distro-sync to upgrade my system to latest F34 pre-release packages, but I got the following error: Error: Transaction test error: file /usr/bin/iceauth conflicts between attempted installs of xorg-x11-server-utils-7.7-39.fc34.x86_64 and iceauth-1.0.8-1.fc34.x86_64

  1   2   3   4   5   6   7   >