Re: updating the GRUB bootloader on EFI systems while upgrading

On Wed Apr16'25 12:59:45AM, Patrick O'Callaghan wrote: > From: Patrick O'Callaghan > Date: Wed, 16 Apr 2025 00:59:45 +0100 > To: users@lists.fedoraproject.org > Reply-To: Community support for Fedora users > Subject: Re: updating the GRUB bootloader on EFI syste

Re: updating the GRUB bootloader on EFI systems while upgrading

> > Is the command called something else? > > FYI: There a a number of ways to answer this question yourself. > > 1. ls /usr/bin/*fwupd* > 2. rpm -ql fwupd > > I use the rpm -ql frequently when I'm not sure what an RPM installed and > where it put it. > Thanks very much for this information!

Re: updating the GRUB bootloader on EFI systems while upgrading

Ranjan Maitra: >> It is my understanding that my GRUB2 is installed on UEFI systems. Marco Moock: > In most cases it is, as it also provides an EFI bootloader that can > boot Linux. Even if there are ways to boot the Linux kernel directly > from the UEFI, most operating systems ship a boot loader

Re: updating the GRUB bootloader on EFI systems while upgrading

> On 16 Apr 2025, at 00:54, Ranjan Maitra via users > wrote: > > $ sudo fwupd > sudo: fwupd: command not found > > However, fwupd is installed. Why can it not be found? > > $ sudo dnf install fwupd > Updating and loading repositories: > Repositories loade

Re: updating the GRUB bootloader on EFI systems while upgrading

On Wed Apr16'25 12:38:41AM, Patrick O'Callaghan wrote: > From: Patrick O'Callaghan > Date: Wed, 16 Apr 2025 00:38:41 +0100 > To: users@lists.fedoraproject.org > Reply-To: Community support for Fedora users > Subject: Re: updating the GRUB bootloader on EFI syste

Re: updating the GRUB bootloader on EFI systems while upgrading

nity support for Fedora users > > Subject: Re: updating the GRUB bootloader on EFI systems while upgrading > > > > On Tue, 2025-04-15 at 18:00 -0500, Ranjan Maitra via users wrote: > > > Thanks! But I get fwupd: command not found. > > > > > > Is that not

Re: updating the GRUB bootloader on EFI systems while upgrading

On Tue, 2025-04-15 at 18:00 -0500, Ranjan Maitra via users wrote: > Thanks! But I get fwupd: command not found. > > Is that not different from an update not found? > $ rpm -qi fwupd Name: fwupd Version : 1.9.29 Release : 1.fc41 Architecture: x86_64 Install Date: Thu 20 Mar 2025 09

Re: updating the GRUB bootloader on EFI systems while upgrading

On Wed Apr16'25 12:20:56AM, greg wrote: > From: greg > Date: Wed, 16 Apr 2025 00:20:56 +0200 > To: Community support for Fedora users > Reply-To: Community support for Fedora users > Subject: Re: updating the GRUB bootloader on EFI systems while upgrading > > >

Re: updating the GRUB bootloader on EFI systems while upgrading

> Why do I get fwupd not found? The commands to use - as root - are: # fwupdmgr get-updates If updates are available for any devices on the system, they'll be displayed. # fwupdmgr update This will download and apply all updates for your system. (Taken from /usr/share/doc/fwupd/README.md) Also t

Re: updating the GRUB bootloader on EFI systems while upgrading

Thanks for your response! On Tue Apr15'25 09:07:27PM, Marco Moock wrote: > From: Marco Moock > Date: Tue, 15 Apr 2025 21:07:27 +0200 > To: users@lists.fedoraproject.org > Reply-To: Community support for Fedora users > Subject: Re: updating the GRUB bootloader on EFI sys

Re: updating the GRUB bootloader on EFI systems while upgrading

> On 15 Apr 2025, at 19:59, Ranjan Maitra via users > wrote: > > However, the installed or embedded bootloaders are never updated > automatically. If you mean the fedora efi code; it is updated in /boot/efi when there is a change. I have personally verified this works recently. Barry --

Re: updating the GRUB bootloader on EFI systems while upgrading

Am 15.04.2025 um 13:25:14 Uhr schrieb Ranjan Maitra via users: > According to > https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/ > systems with the BIOS firmware have the GRUB RPM packages updated. > However, the installed or embedded bootloaders are never updated > automa

updating the GRUB bootloader on EFI systems while upgrading

According to https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/ systems with the BIOS firmware have the GRUB RPM packages updated. However, the installed or embedded bootloaders are never updated automatically. It is my understanding that my GRUB2 is installed on UEFI sy

Re: key updating (was: Signal-Desktop & nodejs-electron GPG key problem)

Tim via users wrote: >> If you remove the key and run dnf again, it should prompt >> you to install the current key, which will (hopefully) work. >> >> In other words: >> >> $ sudo rpm -e gpg-pubkey-17280ddf > > I've encountered that kind of thing before, but why does it require > manual int

key updating (was: Signal-Desktop & nodejs-electron GPG key problem)

Todd Zullinger > > Another possibility is that the keys have been updated since > > you initially installed them and you need to remove the > > current key to allow dnf to import the updated key. Todd Zullinger: > I think this is the case. > > I was able to copy the yum repo file from there and i

Re: Updating failed midway. System will not boot.

On Thu, Jul 18, 2024 at 10:45 AM murph nj wrote: > > I got it running. The write-up will not be super complete, but here goes. > > When I checked for kernels, I saw that there was a new one available > (6.9.9?) That installed OK, and seemed to resolve the uname-r issue. > > Another package (ko-s

Re: Updating failed midway. System will not boot.

I got it running. The write-up will not be super complete, but here goes. When I checked for kernels, I saw that there was a new one available (6.9.9?) That installed OK, and seemed to resolve the uname-r issue. Another package (ko-something) that was part of the plamsa desktop was causing a pr

Re: Updating failed midway. System will not boot.

Reinstalling all of those did not seem to resolve it. As kernel-uname-r is part of kernel-core, I tried reinstalling kernel-core 6.8.8, which is installed, but not currently running. I got "Installed package kernel-core-6.8.8-300.fc40.x86_64 (From @System) not available." I already removed the 6.

Re: Updating failed midway. System will not boot.

On Wed, Jul 17, 2024 at 10:20 PM murph nj wrote: > > Progress: > > I've added mirrors.fedoraproject.org and mirror.math.princeton.edu to > my /etc/hosts, and can do some dnf work: > > When I do a dnf distro-sync I get an error: > > package kernel-modules-extra-6.8.9-300.fc.x86_64 from @System requ

Re: Updating failed midway. System will not boot.

n, resolvectl status gives me: "sd_bus_open_system: > > Connection refused" > > > > Still working on it, hints woudl be welcome. If I can get name > > resoluction working, I might be able to try to run updates again. > > > > > > On Tue, Jul 16, 202

Re: Updating failed midway. System will not boot.

try to run updates again. > > > On Tue, Jul 16, 2024 at 6:51 PM Samuel Sieb wrote: > > > > On 7/16/24 3:27 PM, murph nj wrote: > > > I had not used my Fedora partition on my old laptop for a few weeks. > > > Came back to a lot of updates that needed running.

Re: Updating failed midway. System will not boot.

wrote: > > I had not used my Fedora partition on my old laptop for a few weeks. > > Came back to a lot of updates that needed running. In the midst of > > updating, an overlooked intemittent (thermal) hardware problem cropped > > up, locking the machine. I had to hard boot it.

Re: Updating failed midway. System will not boot.

On 7/16/24 3:27 PM, murph nj wrote: I had not used my Fedora partition on my old laptop for a few weeks. Came back to a lot of updates that needed running. In the midst of updating, an overlooked intemittent (thermal) hardware problem cropped up, locking the machine. I had to hard boot it

Updating failed midway. System will not boot.

I had not used my Fedora partition on my old laptop for a few weeks. Came back to a lot of updates that needed running. In the midst of updating, an overlooked intemittent (thermal) hardware problem cropped up, locking the machine. I had to hard boot it. Now, it will not boot correctly. I can

Re: Problem with updating powerdevil and libddcutil from F38

On Wed, Nov 15, 2023 at 8:42 AM Qiyu Yan wrote: > > Just looked into the issue, the root cause is due to that 2 different > updates are being built and pushed simultaneously in 2 different > side-tags for 2 different sobumps, and one overrides another. > > This is being be sorted out by following

Re: Problem with updating powerdevil and libddcutil from F38

Hi, Just looked into the issue, the root cause is due to that 2 different updates are being built and pushed simultaneously in 2 different side-tags for 2 different sobumps, and one overrides another. This is being be sorted out by following update: https://bodhi.fedoraproject.org/updates/FED

Re: Problem with updating powerdevil and libddcutil from F38

> On 15 Nov 2023, at 12:55, Jeffrey Walton wrote: > > Thanks Barry. It looks like no joy. > > I opened a KDE bug, which was subsequently closed: > . I then opened the > Fedora-specific bug: > . >

Re: Problem with updating powerdevil and libddcutil from F38

On Wed, Nov 15, 2023 at 7:43 AM Barry Scott wrote: > >> On 15 Nov 2023, at 11:35, Jeffrey Walton wrote: >> >> I see a couple of other specific questions about powerdevil and >> libddcutil from F38, but I don't see a clear path forward. >> >> How do I fix the problem? > > These are the version I s

Re: Problem with updating powerdevil and libddcutil from F38

> On 15 Nov 2023, at 11:35, Jeffrey Walton wrote: > > I see a couple of other specific questions about powerdevil and > libddcutil from F38, but I don't see a clear path forward. > > How do I fix the problem? These are the version I see: [root@armf38 ~]# rpm -q powerdevil libddcutil powerdev

Problem with updating powerdevil and libddcutil from F38

Hi Everyone, I'm trying to upgrade a KDE-based workstation from F38 to F39. I delayed the upgrade to ensure this workstation would remain available. The delay allowed a problem with powerdevil and libddcutil to creep in. It is causing `dnf update` and `dnf update --refresh` to fail. I use only Fe

Re: Solution: OVMF 4M-based VMs broken after updating to F39

On Nov 10, 2023, at 17:03, Sam Varshavchik wrote: > > I had an EFI VM that was configured to use > /usr/share/edk2/ovmf-4m/OVMF_CODE.secboot.fd as its bootloader in F38. > > The edk2-ovmf package in F39 no longer installs it. This results in an error > message starting any VM that uses OVMF 4M

Solution: OVMF 4M-based VMs broken after updating to F39

I had an EFI VM that was configured to use /usr/share/edk2/ovmf-4m/OVMF_CODE.secboot.fd as its bootloader in F38. The edk2-ovmf package in F39 no longer installs it. This results in an error message starting any VM that uses OVMF 4M images. The /usr/share/edk2/ovmf-4m directory no longer exis

Don't use reinstall while updating the rescue kernel

depmod: WARNING: could not open modules.order at /lib/modules/6.2.0-63.fc38.x86_64 https://bugzilla.redhat.com/show_bug.cgi?id=2173984 Some web sites suggest running "dnf reinstall 'kernel-core*'" after deleting "/boot/*-rescue-*". Until the bug is fixed, don't! -- George N. White III ___

Re: Updating grub after dnf-system-upgrade

On Thu, 27 Apr 2023 01:47:58 -0400 Jeffrey Walton wrote: > (I have open questions about systems that claim both BIOS and UEFI, > but I have not been able to find answers. If I need to back up a bit, > then please say so). This may or may not be helpful, but when I make a "universal" boot USB stic

Re: Updating grub after dnf-system-upgrade

On 4/26/23 22:47, Jeffrey Walton wrote: I just dnf-upgraded my last system from F37 to F38. One of the post-upgrade task is "Update GRUB bootloader on BIOS systems" (https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/): Systems with the BIOS firmware have the GRUB RPM packag

Updating grub after dnf-system-upgrade

Hi Everyone, I just dnf-upgraded my last system from F37 to F38. One of the post-upgrade task is "Update GRUB bootloader on BIOS systems" (https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/): Systems with the BIOS firmware have the GRUB RPM packages updated. However, the

Re: Updating F32 (with Nvidia drivers) and startup hangs.

On 02/01/2022 14:43, Ed Greshko wrote: On 02/01/2022 20:15, John Pilkington wrote: My reply was intended to give some evidence about what the rpmfusion packages provided, and to hint, in response to the preceding post, that it might give a complete version of the cuda set.   I posted a list of

Re: Updating F32 (with Nvidia drivers) and startup hangs.

On 02/01/2022 20:15, John Pilkington wrote: My reply was intended to give some evidence about what the rpmfusion packages provided, and to hint, in response to the preceding post, that it might give a complete version of the cuda set.   I posted a list of installed nvidia packages earlier, but

Re: Updating F32 (with Nvidia drivers) and startup hangs.

On 02/01/2022 11:42, Ed Greshko wrote: On 02/01/2022 19:07, John Pilkington wrote: On 02/01/2022 09:39, francis.montag...@inria.fr wrote: Hi On Sat, 01 Jan 2022 13:26:47 -0700 Jerry James wrote: On Sat, Jan 1, 2022 at 1:07 PM wrote: Can you confirm that you need CUDA and not only the nvid

Re: Updating F32 (with Nvidia drivers) and startup hangs.

On 02/01/2022 19:07, John Pilkington wrote: On 02/01/2022 09:39, francis.montag...@inria.fr wrote: Hi On Sat, 01 Jan 2022 13:26:47 -0700 Jerry James wrote: On Sat, Jan 1, 2022 at 1:07 PM wrote: Can you confirm that you need CUDA and not only the nvidia drivers ? If yes, I suggest to not

Re: Updating F32 (with Nvidia drivers) and startup hangs.

On 02/01/2022 09:39, francis.montag...@inria.fr wrote: Hi On Sat, 01 Jan 2022 13:26:47 -0700 Jerry James wrote: On Sat, Jan 1, 2022 at 1:07 PM wrote: Can you confirm that you need CUDA and not only the nvidia drivers ? If yes, I suggest to not use the rpmfusion repositories since they do

Re: Updating F32 (with Nvidia drivers) and startup hangs.

Hi On Sat, 01 Jan 2022 13:26:47 -0700 Jerry James wrote: > On Sat, Jan 1, 2022 at 1:07 PM wrote: >> Can you confirm that you need CUDA and not only the nvidia drivers ? >> If yes, I suggest to not use the rpmfusion repositories since they don't >> provide CUDA. See below. > They don't? Then

RE: Updating F32 (with Nvidia drivers) and startup hangs.

John Pilkington wrote: > There have been several posts in the last few days arising from the shift of > some nvidia cards to 'legacy' status. Cards supported by the > 470 series driver but not by 495 now have to add the 470xx tag to the > rpmfusion package name. > > The GTX2060 is listed as supp

Re: Updating F32 (with Nvidia drivers) and startup hangs.

Fulko Hew wrote on 2022/01/02 2:52: I'm not sure where the problem lies, so I'll start out with where I'm coming from... I built a machine 2 years ago to support the Folding@Home project using F32 and an Nvidia 2060 card. If I can't get to a GUI screen to be able to fetch and install newer N

Re: Updating F32 (with Nvidia drivers) and startup hangs.

On Jan 1, 2022, at 16:59, John Pilkington wrote: > There have been several posts in the last few days arising from the shift of > some nvidia cards to 'legacy' status. Cards supported by the 470 series > driver but not by 495 now have to add the 470xx tag to the rpmfusion package > name. That

Re: Updating F32 (with Nvidia drivers) and startup hangs.

On 01/01/2022 17:52, Fulko Hew wrote: I'm not sure where the problem lies, so I'll start out with where I'm coming from... I built a machine 2 years ago to support the Folding@Home project using F32 and an Nvidia 2060 card. It's been running non-stop ever since. But I want to update the system

Re: Updating F32 (with Nvidia drivers) and startup hangs.

On Sat, Jan 1, 2022 at 1:07 PM wrote: > Can you confirm that you need CUDA and not only the nvidia drivers ? > > If yes, I suggest to not use the rpmfusion repositories since they don't > provide CUDA. See below. They don't? Then what are the xorg-x11-drv-nvidia-cuda and xorg-x11-drv-nvidia-cuda

Re: Updating F32 (with Nvidia drivers) and startup hangs.

Hi. On Sat, 01 Jan 2022 12:52:46 -0500 Fulko Hew wrote: > But I want to update the system to the latest and greatest release and > drivers > (since it appears that my old? CUDA drivers have stopped working with F@H) Can you confirm that you need CUDA and not only the nvidia drivers ? If yes, I

Updating F32 (with Nvidia drivers) and startup hangs.

I'm not sure where the problem lies, so I'll start out with where I'm coming from... I built a machine 2 years ago to support the Folding@Home project using F32 and an Nvidia 2060 card. It's been running non-stop ever since. But I want to update the system to the latest and greatest release and d

Re: problem to updating to fedora 34

On 05/10/2021 20:24, Angelo Moreschini wrote: :-( the same problem (<*gpg.errors.GPGMEError: GPGME: Invalid crypto engine*>) with the command <*sudo dnf system-upgrade download --releasever=33*> Any update on the problems you're facing? -- On Facebook it is called Vaguebooking. __

Re: problem to updating to fedora 34

On 05/10/2021 20:42, Ed Greshko wrote: It may take a bit of time as it is late in my day. A cat woke me One more thing to also try. sudo dnf system-upgrade clean sudo dnf clean all sudo rpm --import /etc/pki/rpm-gpg/* sudo dnf system-upgrade download --releasever=33 -- On Facebook i

Re: problem to updating to fedora 34

On 05/10/2021 20:24, Angelo Moreschini wrote: :-( the same problem (<*gpg.errors.GPGMEError: GPGME: Invalid crypto engine*>) with the command <*sudo dnf system-upgrade download --releasever=33*> OK Let me do some checking.  The --nogpgcheck was just a work around that I was hoping would

Re: problem to updating to fedora 34

:-( the same problem (<*gpg.errors.GPGMEError: GPGME: Invalid crypto engine*>) with the command <*sudo dnf system-upgrade download --releasever=33*> - here the output : - Downloading Packages: [SKIPPED] gstreamer1-plugin-openh264-1.16.2-2.fc33.x86_64.rpm: Already downloaded [SKIP

Re: problem to updating to fedora 34

ok thank you, I begin :-) On Tue, Oct 5, 2021 at 2:48 PM Ed Greshko wrote: > On 05/10/2021 19:11, Angelo Moreschini wrote: > > > > I didn't finish upgrading to Fedora 32. > > I think you meant to write that you've updated your F32 system. Yes? > > > > > I have to perform two commands : > > >

Re: problem to updating to fedora 34

On 05/10/2021 19:11, Angelo Moreschini wrote: I didn't finish upgrading to Fedora 32. I think you meant to write that you've updated your F32 system.  Yes? I have to perform two commands : 1. sudo dnf system-upgrade download --releasever=34 * sudo dnf system-upgrade reboot. I have

Re: problem to updating to fedora 34

hi Ed , I didn't finish upgrading to Fedora 32. I have to perform two commands : 1. sudo dnf system-upgrade download --releasever=34 - sudo dnf system-upgrade reboot. I waited to do it, fearing that in my (particular) environment I needed to use some special switch like it was for the

Re: problem to updating to fedora 34

this the output : Installed: criu-libs-3.15-1.fc32.x86_64 fwupd-plugin-uefi-capsule-data-1.5.7-1.fc32.x86_64 jetty-util-ajax-9.4.40-1.fc32.noarch kernel-5.11.22-100.fc32.x86_64 kernel-core-5.11.22-100.fc32.x86_64 kernel-modules-5.11.22-100.fc32.x86_64 kernel-modules-extra-5.11.22-100.fc32.

Re: problem to updating to fedora 34

this (sudo dnf --nogpgcheck upgrade) worked ... :- ) Now I have to call . (I think) On Mon, Oct 4, 2021 at 5:28 PM Ed Greshko wrote: > On 04/10/2021 22:10, Angelo Moreschini wrote: > > [angelo_dev@localhost ~]$ dnf clean all > > 0 files removed > > Sorry, I forgot to include "sudo". This w

Re: problem to updating to fedora 34

On Mon, 4 Oct 2021 10:02:26 +0300 Angelo Moreschini wrote: > I get this error > > > > when I do the command : > > sudo dnf system-upgrade download --releasever=34 --allowerasing > can get an help ? Older crypto policies have been turned off in the latest fedora versions. Try the command,

Re: problem to updating to fedora 34

On 04/10/2021 22:10, Angelo Moreschini wrote: [angelo_dev@localhost ~]$ dnf clean all 0 files removed Sorry, I forgot to include "sudo".  This won't remove the files downloaded by root. sudo dnf upgrade gpg.errors.GPGMEError: GPGME: Invalid crypto engine   (again ...) sudo dnf upgrade gpg

Re: problem to updating to fedora 34

[angelo_dev@localhost ~]$ dnf clean all 0 files removed sudo dnf upgrade gpg.errors.GPGMEError: GPGME: Invalid crypto engine (again ...) sudo dnf upgrade gpg.errors.GPGMEError: GPGME: Invalid crypto engine (again the same problem...) what do you think to uninstall pgp and after reinstall i

Re: problem to updating to fedora 34

On 04/10/2021 21:18, Angelo Moreschini wrote: yes I am to fedora 32 Out of warranty.  :-) :-) I  already tried to update but without success with  nothing (the output not) change Perhaps I made mistakes using PGP Still see criu-libs in the output?  If so, how about with sud

Re: problem to updating to fedora 34

yes I am to fedora 32 I already tried to update but without success with nothing (the output not) change Perhaps I made mistakes using PGP On Mon, Oct 4, 2021 at 4:08 PM Ed Greshko wrote: > On 04/10/2021 20:59, Angelo Moreschini wrote: > > ok > > I get this : > > > > Skypeforli

Re: problem to updating to fedora 34

On 04/10/2021 20:59, Angelo Moreschini wrote: ok I get this : Skypeforlinux - stable                          4.0 kB/s | 2.9 kB     00:00 Dependencies resolved.  Package                           Arch   Versi

Re: problem to updating to fedora 34

ok I get this : Skypeforlinux - stable 4.0 kB/s | 2.9 kB 00:00 Dependencies resolved. Package Arch VersionRepo Size ==

Re: problem to updating to fedora 34

On 04/10/2021 19:07, Angelo Moreschini wrote: thank you  for answering me Ed, I get this message (<*gpg.errors.GPGMEError: GPGME: Invalid crypto engine*>) after the command  <*sudo dnf upgrade --refresh*> in my opinion this is a problem connected to PGP ... (...something about the keys usage-

Re: problem to updating to fedora 34

thank you for answering me Ed, I get this message (<*gpg.errors.GPGMEError: GPGME: Invalid crypto engine*>) after the command <*sudo dnf upgrade --refresh*> in my opinion this is a problem connected to PGP ... (...something about the keys usage---) I know this tip, but not enough to do any se

Re: problem to updating to fedora 34

On 04/10/2021 15:02, Angelo Moreschini wrote: Hi I get this error when I do the command : sudo dnf system-upgrade download  --releasever=34 --allowerasing I am not able to understand what is a Invalid crypto engine> (this happen when I try to update my computer to fedora 34) can get an

problem to updating to fedora 34

Hi I get this error when I do the command : sudo dnf system-upgrade download --releasever=34 --allowerasing I am not able to understand what is a Invalid crypto engine> (this happen when I try to update my computer to fedora 34) can get an help ? thank you angelo _

Re: usual torment after updating firefox

Samuel Sieb: >> Are you using some custom css rules to do this? That's entirely at >> your own risk. François Patte: > What is the "risk"? That they'll redesign the interface, and your custom CSS may need rewriting to work on the new one. And that /that/ can happen every time they release a new

Re: usual torment after updating firefox

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 25/06/2020 à 19:54, Samuel Sieb a écrit : > On 6/25/20 9:16 AM, François Patte wrote: >> I updated my firefox and, as usual, the syntax to configure the >> place of the tab bar has changed So, my tab bar is at the top >> of all bars and I want i

Re: usual torment after updating firefox

On Thu, 2020-06-25 at 09:47 -0700, PGNet Dev wrote: > fyi, I find this > > https://github.com/Aris-t2/CustomCSSforFx > > > to be very useful in removing/modifying the many 'annoying' > assumptions forced by upstream ... We'd all be at a lot less risk from malicious websites (or malicious adve

Re: usual torment after updating firefox

On 6/25/20 9:16 AM, François Patte wrote: I updated my firefox and, as usual, the syntax to configure the place of the tab bar has changed So, my tab bar is at the top of all bars and I want it just above the tabs themselves... Are you using some custom css rules to do this? That's entirel

Re: usual torment after updating firefox

On 6/25/20 9:16 AM, François Patte wrote: > If someone has the recipe to change the place of the tab bar, I will > be happy to know it. fyi, I find this https://github.com/Aris-t2/CustomCSSforFx to be very useful in removing/modifying the many 'annoying' assumptions forced by upstream ...

Re: usual torment after updating firefox

On Thu, 25 Jun 2020 18:16:59 +0200 François Patte wrote: > I updated my firefox and, as usual, the syntax to configure the place > of the tab bar has changed So, my tab bar is at the top of all > bars and I want it just above the tabs themselves... Can't help with this, though it is probably

usual torment after updating firefox

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonjour, I updated my firefox and, as usual, the syntax to configure the place of the tab bar has changed So, my tab bar is at the top of all bars and I want it just above the tabs themselves... This happens everytime developpers have some gas I

Re: No DNF updating again today -

On 2020-06-13 01:08, Jon LaBadie wrote: Read the first line quoted in your posting. It contains the path to the history database. jon -- Jon H. LaBadie ° Yes, that appears to have been all it needed, it remains to be seen what happens with the next dnf update/ I simply did rm /var/lib/dnf/

Re: No DNF updating again today -

On 6/14/20 6:29 AM, stan via users wrote: On Sat, 13 Jun 2020 12:11:41 -0700 Samuel Sieb wrote: His history database has become corrupted somehow. Several people have explained how to delete it and Jerry rep[lied to the other thread with a possible way to recover the database. Great! I did

Re: No DNF updating again today -

On Sat, 13 Jun 2020 12:11:41 -0700 Samuel Sieb wrote: > His history database has become corrupted somehow. Several people > have explained how to delete it and Jerry rep[lied to the other > thread with a possible way to recover the database. Great! I didn't see another thread, must have missed

Re: No DNF updating again today -

On 6/13/20 11:57 AM, stan via users wrote: On Sat, 13 Jun 2020 12:43:47 -0400 Bob Goodwin wrote: Error: SQLite error on "/var/lib/dnf/history.sqlite": Reading a row failed: database disk image is malformed I have not rebboted or logged out since doing that, if that is requured? But the erro m

Re: No DNF updating again today -

On Sat, 13 Jun 2020 12:43:47 -0400 Bob Goodwin wrote: > Error: SQLite error on "/var/lib/dnf/history.sqlite": Reading a row > failed: database disk image is malformed > > I have not rebboted or logged out since doing that, if that is > requured? But the erro messag always points to SQLite ...

Re: No DNF updating again today -

On 2020-06-12 12:38, stan via users wrote: I suggest that you re-install the dnf package from koji, https://koji.fedoraproject.org/koji/packageinfo?packageID=14310 Or even update dnf via rpm. Use rpm to do it instead of dnf. e.g. rpm --reinstall -vh dnf[version].rpm rpm -Uvh dnf[version].rpm

Re: No DNF updating again today -

On Fri, Jun 12, 2020 at 09:43:51AM -0400, Bob Goodwin wrote: > > > On 2020-06-11 13:01, Samuel Sieb wrote: > > On 6/11/20 4:50 AM, Bob Goodwin wrote: > > > Error: SQLite error on "/var/lib/dnf/history.sqlite": Reading a row > > > failed: database disk image is malformed > > > > Somehow your dnf

Re: No DNF updating again today -

On Fri, Jun 12, 2020 at 8:27 AM Bob Goodwin wrote: > Dnf update produces the same error message this morning as it did for > the previous two days. Did you do the database dump and restore that I mentioned yesterday? > /home/bobg/.gramps/grampsdb/5eb0b4df/sqlite.db is the only sqlite.db > file I

Re: No DNF updating again today -

On Fri, 12 Jun 2020 09:43:51 -0400 Bob Goodwin wrote: > On 2020-06-11 13:01, Samuel Sieb wrote: > > On 6/11/20 4:50 AM, Bob Goodwin wrote: > >> Error: SQLite error on "/var/lib/dnf/history.sqlite": Reading a > >> row failed: database disk image is malformed I haven't been following. Did you d

Re: No DNF updating again today -

On 2020-06-11 13:01, Samuel Sieb wrote: On 6/11/20 4:50 AM, Bob Goodwin wrote: Error: SQLite error on "/var/lib/dnf/history.sqlite": Reading a row failed: database disk image is malformed Somehow your dnf history database is corrupted.  The easy fix is to delete it or move it somewhere else

Re: No DNF updating again today -

On 6/11/20 4:50 AM, Bob Goodwin wrote: Error: SQLite error on "/var/lib/dnf/history.sqlite": Reading a row failed: database disk image is malformed Somehow your dnf history database is corrupted. The easy fix is to delete it or move it somewhere else. Otherwise you could try to find an sqli

No DNF updating again today -

It looks like my best hope is for FC33beta to arrive soon, need to check on that. Today I tried "clean all" still the same error message. The only thing that comes to mind is that I added SeaMonkey  via dnf. I would not expect a problem due to that, but maybe? It is more reliable for opening

Re: firewalld messed up after updating to F32

On 2020-05-17 07:51, Sam Varshavchik wrote: > > Thanks, this did the trick, for now. > > Additionally, somewhere along the process all my rules in FedoraServer.xml > got blown away. Fortunately, I had my firewall config backed up, and restored > it. > > Left the complete dump of the trace in Bug

Re: firewalld messed up after updating to F32

Ed Greshko writes: On 2020-05-17 07:01, Sam Varshavchik wrote: > The first thing that I noticed after updating my router to F32 is that masquerading didn't seem to work. telnet to some public port 80 appears to be blocked, traceroute dies, etc… > > When I ran firewa

Re: firewalld messed up after updating to F32

On 2020-05-17 07:01, Sam Varshavchik wrote: > The first thing that I noticed after updating my router to F32 is that > masquerading didn't seem to work. telnet to some public port 80 appears to be > blocked, traceroute dies, etc… > > When I ran firewall-config, the masquerad

Re: firewalld messed up after updating to F32

Sam Varshavchik writes: The first thing that I noticed after updating my router to F32 is that masquerading didn't seem to work. telnet to some public port 80 appears to be blocked, traceroute dies, etc… When I ran firewall-config, the masquerading checkbox was off, so I enabled it

firewalld messed up after updating to F32

The first thing that I noticed after updating my router to F32 is that masquerading didn't seem to work. telnet to some public port 80 appears to be blocked, traceroute dies, etc… When I ran firewall-config, the masquerading checkbox was off, so I enabled it, but it made no diffe

Re: Grub.cfg not updating

On 7/12/19 17:11, Robert McBroom via users wrote: On 12/6/19 10:03 PM, Stephen Morris wrote: On 7/12/19 10:22, Robert McBroom via users wrote: On 12/6/19 5:41 PM, Samuel Sieb wrote: On 12/6/19 1:52 PM, Robert McBroom via users wrote: On 12/6/19 2:06 AM, Anthony F McInerney wrote: On Thu, 5

Re: Grub.cfg not updating

install to make sure it's up to date. Updated with the update to f31. It's possible, but I don't think that updating the package updates the parts embedded on the hard drive. There should be some way to check the version from the boot menu to see if the version there match

Re: Grub.cfg not updating

On 12/6/19 10:03 PM, Stephen Morris wrote: On 7/12/19 10:22, Robert McBroom via users wrote: On 12/6/19 5:41 PM, Samuel Sieb wrote: On 12/6/19 1:52 PM, Robert McBroom via users wrote: On 12/6/19 2:06 AM, Anthony F McInerney wrote: On Thu, 5 Dec 2019 at 19:04, Samuel Sieb

Re: Grub.cfg not updating

On 7/12/19 10:22, Robert McBroom via users wrote: On 12/6/19 5:41 PM, Samuel Sieb wrote: On 12/6/19 1:52 PM, Robert McBroom via users wrote: On 12/6/19 2:06 AM, Anthony F McInerney wrote: On Thu, 5 Dec 2019 at 19:04, Samuel Sieb > wrote:     On 12/5/19 8:02 AM, Robe

Re: Grub.cfg not updating

On 12/6/19 5:41 PM, Samuel Sieb wrote: On 12/6/19 1:52 PM, Robert McBroom via users wrote: On 12/6/19 2:06 AM, Anthony F McInerney wrote: On Thu, 5 Dec 2019 at 19:04, Samuel Sieb > wrote:     On 12/5/19 8:02 AM, Robert McBroom via users wrote:     > Updated from Fedo

Re: Grub.cfg not updating

On 12/6/19 1:52 PM, Robert McBroom via users wrote: On 12/6/19 2:06 AM, Anthony F McInerney wrote: On Thu, 5 Dec 2019 at 19:04, Samuel Sieb > wrote: On 12/5/19 8:02 AM, Robert McBroom via users wrote: > Updated from Fedora 29 to 31 on a legacy system. Kernel u

Re: Grub.cfg not updating

On 12/6/19 2:06 AM, Anthony F McInerney wrote: On Thu, 5 Dec 2019 at 19:04, Samuel Sieb > wrote: On 12/5/19 8:02 AM, Robert McBroom via users wrote: > Updated from Fedora 29 to 31 on a legacy system. Kernel updates no > longer update grub.cfg to the new ker

  1   2   3   4   >