No match for grup package - during dnf upgrade process??

[Michael D. Setzer II via users]

Am upgrading a machine from Fedora 37 to Fedora 38.
Saw this as part of process.
Is there a process to clean this up?
Did they drop this groups, or renamed them??

Thanks.

No match for group package "python3-dnf-plugin-system-upgrade"
No match for group package "google-noto-sans-telugu-ui-vf-fonts"
No match for group package "google-noto-looped-lao-ui-vf-fonts"
No match for group package "google-noto-sans-kannada-ui-vf-fonts"
No match for group package "google-noto-sans-display-vf-fonts"
No match for group package "sil-scheherazade-fonts"
No match for group package "drehatlas-warender-bibliothek-fonts"
No match for group package "google-noto-sans-tai-viet-vf-fonts"
No match for group package "evince-nautilus"
No match for group package "google-noto-sans-lao-ui-vf-fonts"
No match for group package "google-noto-sans-khmer-ui-vf-fonts"
No match for group package 
"google-noto-serif-tamil-slanted-vf-fonts"
No match for group package "tlomt-junction-fonts"
No match for group package "google-noto-looped-lao-vf-fonts"
No match for group package "polarsys-b612-sans-fonts"
No match for group package 
"google-noto-sans-zanabazar-square-vf-fonts"
No match for group package "reiserfs-utils"
No match for group package "google-noto-sans-runic-vf-fonts"
No match for group package "ubuntu-title-fonts"
No match for group package "google-noto-sans-arabic-ui-vf-fonts"
No match for group package "yanone-tagesschrift-fonts"
No match for group package 
"google-noto-sans-hebrew-new-vf-fonts"
No match for group package "google-noto-looped-thai-ui-vf-fonts"
No match for group package "vlgothic-p-fonts"
No match for group package "gimp-heif-plugin"
No match for group package 
"google-noto-sans-myanmar-ui-vf-fonts"
No match for group package 
"google-noto-serif-nyiakeng-puachue-hmong-vf-fonts"
No match for group package "vlgothic-fonts"
No match for group package "google-noto-kufi-arabic-vf-fonts"
No match for group package "google-noto-sans-thai-ui-vf-fonts"
No match for group package "google-noto-serif-display-vf-fonts"
No match for group package 
"google-noto-sans-hebrew-droid-vf-fonts"
No match for group package "google-noto-sans-oriya-ui-vf-fonts"
No match for group package "kanjistrokeorders-fonts"
No match for group package 
"google-noto-sans-gurmukhi-ui-vf-fonts"
No match for group package "google-noto-sans-tamil-ui-vf-fonts"
No match for group package 
"google-noto-sans-malayalam-ui-vf-fonts"
No match for group package "culmus-shofar-fonts"
No match for group package 
"google-noto-sans-tamil-supplement-vf-fonts"
No match for group package "drehatlas-xaporho-fonts"
No match for group package "cups-bjnp"
No match for group package "google-noto-looped-thai-vf-fonts"
No match for group package "ipa-ex-mincho-fonts"
No match for group package "hanazono-fonts"
No match for group package "google-noto-serif-dogra-vf-fonts"
No match for group package "google-noto-sans-bengali-ui-vf-fonts"
No match for group package "gstreamer1-libav"
No match for group package "vollkorn-fonts"
No match for group package "google-noto-sans-sinhala-ui-vf-fonts"
No match for group package "ipa-ex-gothic-fonts"
No match for group package "authselect-compat"



++
 Michael D. Setzer II - Computer Science Instructor (Retired) 
 mailto:mi...@guam.net
 mailto:msetze...@gmail.com
 Guam - Where America's Day Begins
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
++


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: unwanted login

[Joe Zeff]

On 08/30/2023 03:55 PM, Richard wrote:

   Automatically Logout Inactive Users From Linux System
   


That only closes inactive terminal sessions, not a GUI.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: unwanted login

[Tim via users]

Tim:
>> I 'spose we should confirm, do you mean the screen saver is kicking in
>> and you have to unlock it.  Or are you getting logged out?


Beartooth
>   I'm actually getting logged out; I have to give my username (id 
> est, confirm the default) and type my password every time.

>> Some xscreensavers were known to crash the display.

>   I've never seen that happen.

Well, the behaviour you've described is exactly the kind of thing that
happened when they crashed.  Then X would restart and you'd have to log
in again.

It was usually just one or two of them that did it, and if people had
xscreensavers set to pick one at random, rather than always use the
same one, they'd get a surprise crash every now and then.

Screen savers that have locked the screen just ask you to re-enter your
password, the username field is unchangeable from your own name.

I'd say, on the problem machine, try just picking a blank screen
option, no other ones, and see if you still get the log outs.


>   My practice after installing every new release has been to tell 
> dnf first to remove mate-screensaver and then to install xscreensaver. The 
> latter is still working fine on the other two machines in front of me.

Same hardware?  Same installs?


>   I've just reversed that: told dnf to install mate-screensaver and 
> remove xscreensaver. I found out immediately that the former doesn't let 
> me manage my screen in any of the ways I want. 
> 
>   Would it help to reboot? Could there be a problem with my KVM 
> switch??

A reboot may help if you've done various installs, etc.  This doesn't
sound like a KVM issue.

I'm yet to try 38, but I am using mate on Fedora and CentOS, and its
screen savers.  The options have always been an adjustable time delay
for how long before considering the computer idle, an option to
activate the screen saver then, an option to lock the screen then. 
And, of course, which screen saver you'd like to use.  Then, there's a
button bringing up power management, with time delay options for
putting the whole computer to sleep when inactive, time delay options
for putting the display to sleep when inactive, and dimming the display
by a selectable amount when idle.

Mostly the same options as any screen saver, I don't recall
xscreensaver having other options, just more choices about what the
screensavers look like.  Though since I just blank the screen, I don't
need anything fancy.

-- 
 
uname -rsvp
Linux 3.10.0-1160.95.1.el7.x86_64 #1 SMP Mon Jul 24 13:59:37 UTC 2023 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: TPM Error on Warm Boot From F38

[Stephen Morris]

On 30/8/23 23:12, stan via users wrote:

On Wed, 30 Aug 2023 09:32:22 +1000
Stephen Morris  wrote:
  

The bios is set to boot off my ssd drive, which is the first drive
plugged into the motherboard, which is the device that Fedora sees as
hd2.

I did a system update yesterday, which upgraded the kernel to 6.4.12
and also updated grub, and then updated the grub menus via
grub2-mkconfig as I always do, and that has not made any difference
to the issue. I have grub configured to build sub-menus for all the
kernel entries as well as showing the latest kernel in the main menu,
so that I have all the Fedora kernels and Ubuntu kernels in
sub-menus. What I have now found is that if I open up a sub-menu,
that is when the tpm error occurs, and since the grub update it is
now producing an extra error telling me to load a kernel first (what
I don't understand is that message seems to be coming from an I386
sub-folder but my environment is 64 bit, or does that mean that
somehow or other grub has reverted to 32 bit?).
I've also mentioned in another thread, that if when I get the tpm
errors I edit the grub menu entry and change all occurrences of hd2
to hd0, even though it continues to display the tpm errors it
successfully boots into F38. It seems as though at the moment it
boots normally if I select a main menu entry to boot from, but only
if the tpm error hasn't already occurred. If the tpm error has
occurred none of the menu entries will boot, which includes the
Chainloader entry for Windows.

Having started my machine from a cold start, when the grub menu's
were displayed, I went to the grub command line and issued the LS
command to list all devices, that showed my boot device as hd0
(hd0,gpt1 - hd0,gpt9), and then when I exited from the command line,
and selected the menu entry for the latest Fedora kernel, which
specified to boot from hd2,gpt7 (this is the fedora UEFI partition),
it successfully booted into Fedora.
How is this possible when the grub command line is indicating that
grub is seeing the devices differently? What I might add to this is
that the way the grub command line is showing the devices is the way
I would expect them to be shown given the way the devices are
physically connected to the motherboard.

I understand what you are asking, and it is certainly a conundrum, but
I have no insight to offer.  Maybe open a bugzilla against grub2.  I
don't think it is the problem, but the people who maintain grub2
probably have a good understanding of this part of the boot process, and
might be able to point to the real culprit.

Thanks Stan, I'll do that.

regards,
Steve


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue





OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: unwanted login

[Richard]

> Date: Wednesday, August 30, 2023 15:36:54 +
> From: Beartooth 
>
>> On Mon, 2023-08-28 at 19:09 +, Beartooth wrote:
>>> One of my F38 machines has taken to demanding that I login over
>>> and over. I want not to have to login at all. (I'm the sole user,
>>> and at home.) Fwiw, I'm running xscreensaver under Mate. Where
>>> and how do I reconfigure?
> 
>   I'm actually getting logged out; I have to give my username (id 
> est, confirm the default) and type my password every time.
> 
> 
>   My practice after installing every new release has been to tell 
> dnf first to remove mate-screensaver and then to install
> xscreensaver. The  latter is still working fine on the other two
> machines in front of me.
> 
>   I've just reversed that: told dnf to install mate-screensaver and 
> remove xscreensaver. I found out immediately that the former
> doesn't let  me manage my screen in any of the ways I want. 
> 
>   Would it help to reboot? Could there be a problem with my KVM 
> switch??

Your initial message seemed to imply that you thought this was
related to Mate, hence my screensaver config reply.

Given your additional information, this may be related to:

  Automatically Logout Inactive Users From Linux System
  

  Why Unix automatically logs you out
  


To deal with this I have (as shown in the second reference) a "set
autologout=off" line in my .cshrc.

Not certain why this behavior would have changed for you - unless you
are logging in differently or your shell startup script changed.


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: unwanted login

[Samuel Sieb]

On 2023-08-30 08:36, Beartooth wrote:

On Wed, 30 Aug 2023 13:20:50 +0930, Tim via users wrote:


On Mon, 2023-08-28 at 19:09 +, Beartooth wrote:

One of my F38 machines has taken to demanding that I login over and
over. I want not to have to login at all. (I'm the sole user, and at
home.) Fwiw, I'm running xscreensaver under Mate. Where and how do I
reconfigure?


I 'spose we should confirm, do you mean the screen saver is kicking in
and you have to unlock it.  Or are you getting logged out?


I'm actually getting logged out; I have to give my username (id
est, confirm the default) and type my password every time.


Are you getting logged out or is it switching to the chooser?
After you login, are applications still open or are you starting from 
what would be a normal initial login state?

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: unwanted login

[Beartooth]

On Wed, 30 Aug 2023 13:20:50 +0930, Tim via users wrote:

> On Mon, 2023-08-28 at 19:09 +, Beartooth wrote:
>> One of my F38 machines has taken to demanding that I login over and
>> over. I want not to have to login at all. (I'm the sole user, and at
>> home.) Fwiw, I'm running xscreensaver under Mate. Where and how do I
>> reconfigure?
> 
> I 'spose we should confirm, do you mean the screen saver is kicking in
> and you have to unlock it.  Or are you getting logged out?

I'm actually getting logged out; I have to give my username (id 
est, confirm the default) and type my password every time.

> Some xscreensavers were known to crash the display.

I've never seen that happen.

My practice after installing every new release has been to tell 
dnf first to remove mate-screensaver and then to install xscreensaver. The 
latter is still working fine on the other two machines in front of me.

I've just reversed that: told dnf to install mate-screensaver and 
remove xscreensaver. I found out immediately that the former doesn't let 
me manage my screen in any of the ways I want. 

Would it help to reboot? Could there be a problem with my KVM 
switch??
-- 
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: TPM Error on Warm Boot From F38

[stan via users]

On Wed, 30 Aug 2023 09:32:22 +1000
Stephen Morris  wrote:
 
> The bios is set to boot off my ssd drive, which is the first drive 
> plugged into the motherboard, which is the device that Fedora sees as
> hd2.
> 
> I did a system update yesterday, which upgraded the kernel to 6.4.12
> and also updated grub, and then updated the grub menus via
> grub2-mkconfig as I always do, and that has not made any difference
> to the issue. I have grub configured to build sub-menus for all the
> kernel entries as well as showing the latest kernel in the main menu,
> so that I have all the Fedora kernels and Ubuntu kernels in
> sub-menus. What I have now found is that if I open up a sub-menu,
> that is when the tpm error occurs, and since the grub update it is
> now producing an extra error telling me to load a kernel first (what
> I don't understand is that message seems to be coming from an I386
> sub-folder but my environment is 64 bit, or does that mean that
> somehow or other grub has reverted to 32 bit?).
> I've also mentioned in another thread, that if when I get the tpm
> errors I edit the grub menu entry and change all occurrences of hd2
> to hd0, even though it continues to display the tpm errors it
> successfully boots into F38. It seems as though at the moment it
> boots normally if I select a main menu entry to boot from, but only
> if the tpm error hasn't already occurred. If the tpm error has
> occurred none of the menu entries will boot, which includes the
> Chainloader entry for Windows.
> 
> Having started my machine from a cold start, when the grub menu's
> were displayed, I went to the grub command line and issued the LS
> command to list all devices, that showed my boot device as hd0
> (hd0,gpt1 - hd0,gpt9), and then when I exited from the command line,
> and selected the menu entry for the latest Fedora kernel, which
> specified to boot from hd2,gpt7 (this is the fedora UEFI partition),
> it successfully booted into Fedora.
> How is this possible when the grub command line is indicating that
> grub is seeing the devices differently? What I might add to this is
> that the way the grub command line is showing the devices is the way
> I would expect them to be shown given the way the devices are
> physically connected to the motherboard.

I understand what you are asking, and it is certainly a conundrum, but
I have no insight to offer.  Maybe open a bugzilla against grub2.  I
don't think it is the problem, but the people who maintain grub2
probably have a good understanding of this part of the boot process, and
might be able to point to the real culprit.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Last kernel update leads to emergency mode

[stan via users]

On Wed, 30 Aug 2023 00:38:08 +0100
Paul Smith  wrote:

> Maybe the following is relevant:
> 
> 
> # dracut --force --kver 6.4.12-200.fc38.x86_64 --verbose
> dracut: Executing: /usr/bin/dracut --force --kver
> 6.4.12-200.fc38.x86_64 --verbose
> dracut: dracut module 'busybox' will not be installed, because command
> 'busybox' could not be found!
> dracut: dracut module 'connman' will not be installed, because command
> 'connmand' could not be found!
> dracut: dracut module 'connman' will not be installed, because command
> 'connmanctl' could not be found!
> dracut: dracut module 'connman' will not be installed, because command
> 'connmand-wait-online' could not be found!
I see the connman errors when I build the initramfs, but it works fine.
> dracut: dracut module 'network-wicked' will not be installed, because
> command 'wicked' could not be found!
> dracut: dracut module 'biosdevname' will not be installed, because
> command 'biosdevname' could not be found!
> dracut: dracut module 'busybox' will not be installed, because command
> 'busybox' could not be found!
> dracut: dracut module 'connman' will not be installed, because command
> 'connmand' could not be found!
> dracut: dracut module 'connman' will not be installed, because command
> 'connmanctl' could not be found!
> dracut: dracut module 'connman' will not be installed, because command
> 'connmand-wait-online' could not be found!
> dracut: dracut module 'network-wicked' will not be installed, because
> command 'wicked' could not be found!
I think these can be taken as warnings rather than errors, unless you
are using busybox or network-wicked in the suspended version.
> dracut: *** Including module: bash ***
> dracut: *** Including module: systemd ***
> dracut: *** Including module: systemd-initrd ***
> dracut: *** Including module: systemd-sysusers ***
> dracut: *** Including module: nss-softokn ***
> dracut: *** Including module: dbus-broker ***
> dracut: *** Including module: rngd ***
> dracut: *** Including module: dbus ***
> dracut: *** Including module: i18n ***
> dracut: *** Including module: network-manager ***
> dracut: *** Including module: network ***
> dracut: *** Including module: ifcfg ***
> dracut: *** Including module: drm ***
> dracut: *** Including module: plymouth ***
> dracut: *** Including module: dm ***
> dracut: Skipping udev rule: 64-device-mapper.rules
> dracut: Skipping udev rule: 60-persistent-storage-dm.rules
> dracut: Skipping udev rule: 55-dm.rules
> dracut: *** Including module: kernel-modules ***
> dracut: *** Including module: kernel-modules-extra ***
> dracut: *** Including module: kernel-network-modules ***
> dracut: *** Including module: lvm ***
> dracut: Skipping udev rule: 64-device-mapper.rules
> dracut: Skipping udev rule: 56-lvm.rules
> dracut: Skipping udev rule: 60-persistent-storage-lvm.rules
> dracut: *** Including module: resume ***
> dracut: *** Including module: rootfs-block ***
> dracut: *** Including module: terminfo ***
> dracut: *** Including module: udev-rules ***
> dracut: Skipping udev rule: 40-redhat.rules
> dracut: Skipping udev rule: 50-firmware.rules
> dracut: Skipping udev rule: 50-udev.rules
> dracut: Skipping udev rule: 91-permissions.rules
> dracut: Skipping udev rule: 80-drivers-modprobe.rules
> dracut: Skipping udev rule: 70-persistent-net.rules
> dracut: *** Including module: dracut-systemd ***
> dracut: *** Including module: usrmount ***
> dracut: *** Including module: base ***
> dracut: *** Including module: fs-lib ***
> dracut: *** Including module: memstrack ***
> dracut: *** Including module: shutdown ***
> dracut: *** Including modules done ***
> dracut: *** Installing kernel module dependencies ***
> dracut: *** Installing kernel module dependencies done ***
> dracut: *** Resolving executable dependencies ***
> dracut: *** Resolving executable dependencies done ***
> dracut: *** Hardlinking files ***
> dracut: Mode: real
> dracut: Method:   sha256
> dracut: Files:2153
> dracut: Linked:   81 files
> dracut: Compared: 0 xattrs
> dracut: Compared: 974 files
> dracut: Saved:563.14 KiB
> dracut: Duration: 0.057574 seconds
> dracut: *** Hardlinking files done ***
> dracut: *** Generating early-microcode cpio image ***
> dracut: *** Constructing AuthenticAMD.bin ***
> dracut: *** Store current command line parameters ***
> dracut: *** Stripping files ***
> dracut: *** Stripping files done ***
> dracut: *** Creating image file
> '/boot/initramfs-6.4.12-200.fc38.x86_64.img' *** dracut: Using
> auto-determined compression method 'pigz' dracut: *** Creating
> initramfs image file '/boot/initramfs-6.4.12-200.fc38.x86_64.img'
> done *** #

This all looks fine.  The journalctl log you posted showed that the
initramfs was working properly, and was able to start systemd to do the
actual boot. It only failed at verifying that t

Re: How do I install the rescue kernel for fc38?

[Jeffrey Walton]

On Wed, Aug 30, 2023 at 12:44 AM Eyal Lebedinsky  wrote:
>
> On 29/08/2023 21.14, ToddAndMargo via users wrote:
> >
> > Fedora 38
> >
> > My rescue kernel is FC30.
> >
> > How do I install the FC38 rescue kernel?
> >
> > # dnf whatprovides kernel\* | grep -i rescue
> > 
> >
> > And my search engine is not helping.
>
> I see (but never used)
> $ man -k rescue
> ...
> grub2-mkrescue (1)   - make a GRUB rescue image
>
> provided by
> grub2-tools-extra

Or 
https://www.gnu.org/software/grub/manual/grub/html_node/Invoking-grub_002dmkrescue.html

Jeff
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: How do I install the rescue kernel for fc38?

[ToddAndMargo via users]

On 8/29/23 20:55, Tim via users wrote:

Geoffrey Leach:

Put the FC 38 on a thumb drive and boot from there. Lots of useful
stuff.


ToddAndMargo:

That went over my head.

:'(



I think they're suggesting that if you wanted to rescue a system, it
may be beneficial to boot from something else, such as a live install
of Fedora on a USB memory stick.  Sometimes it's an exercise in
frustration trying to fix a system by booting from it.




Well that makes sense.  I thought he meant
to use a Live USB (I have several) to create
a rescue boot kernel for the system.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: How do I install the rescue kernel for fc38?

[Stephen Morris]

On 30/8/23 09:51, ToddAndMargo via users wrote:

On 8/29/23 10:41, Michael D. Setzer II via users wrote:
I've found that removing the rescue files from /boot and then doing a 
dnf reinstall kernel-core will do

it.

Did just run it to make sure, paste has wrapping, but hopefully one 
can follow.


# cd /boot
# ls -l*rescue*
-rw---. 1 root root 118033857 Jun  5 01:53
initramfs-0-rescue-189711f94e78436d9618b891a8fce70e.img
-rwxr-xr-x. 1 root root  14332776 Jun  5 01:51
vmlinuz-0-rescue-189711f94e78436d9618b891a8fce70e

# rm*rescue*
rm: remove regular file 
'initramfs-0-rescue-189711f94e78436d9618b891a8fce70e.img'? y
rm: remove regular file 
'vmlinuz-0-rescue-189711f94e78436d9618b891a8fce70e'? y


# dnf reinstall kernel-core
Last metadata expiration check: 0:27:24 ago on Wed 30 Aug 2023 
03:05:33 AM ChST.

Dependencies resolved.
===

  Package  Architecture 
Version   Repository    Size

===

Reinstalling:
  kernel-core  x86_64 
6.4.12-100.fc37   updates   15 M


Transaction Summary
===


Total download size: 15 M
Installed size: 65 M
Is this ok [y/N]: y
Downloading Packages:
kernel-core-6.4.12-100.fc37.x86_64.rpm 3.4 MB/s |  15 MB 00:04
--- 


Total 2.7 MB/s |  15 MB 00:05
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
   Preparing : 1/1
   Reinstalling : kernel-core-6.4.12-100.fc37.x86_64 1/2
   Running scriptlet: kernel-core-6.4.12-100.fc37.x86_64 1/2
   Running scriptlet: kernel-core-6.4.12-100.fc37.x86_64 2/2
   Cleanup  : kernel-core-6.4.12-100.fc37.x86_64 2/2
   Running scriptlet: kernel-core-6.4.12-100.fc37.x86_64 2/2
   Verifying    : kernel-core-6.4.12-100.fc37.x86_64 1/2
   Verifying    : kernel-core-6.4.12-100.fc37.x86_64 2/2

Reinstalled:
   kernel-core-6.4.12-100.fc37.x86_64

Complete!

Takes some time to run, but afterwards.
# ls -l*rescue*
-rw---. 1 root root 123671666 Aug 30 03:35
initramfs-0-rescue-189711f94e78436d9618b891a8fce70e.img
-rwxr-xr-x. 1 root root  14384360 Aug 30 03:34
vmlinuz-0-rescue-189711f94e78436d9618b891a8fce70e



Hi Michael,

Worked perfectly.  Excellent directions!

https://imgur.com/lgwFazr.png
If you install the following statement into /etc/default/grub, and 
remake the grub menus either with grubby (maybe) or definitely with 
grub2-mkconfig, the menu build process it add a rescue entry into the 
grub menus for all kernels you have installed.


GRUB_DISABLE_RECOVERY="false"

regards,
Steve



-T
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue





OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue