users August 2024

users@lists.fedoraproject.org

64 participants
56 discussions

color profiles for screens/monitors
by lejeczek 17 Nov '24

17 Nov '24

Hi guys How do we load & tweak color profiles in Fedora (without using external sensor-devices) ? My Lenovo Thinkbook built-in screen has different (and not adjustable in BIOS) color temperature what my external DELL shows - they are quite different thus annoying. many thanks, L.

5 7

[FC8] ssh and CAC card???
by Todd Denniston 17 Sep '24

17 Sep '24

From what I understood, the change to openssh listed in: rpm -q --changelog openssh |less as: "* Wed Jun 20 2007 Tomas Mraz <tmraz(a)redhat.com> - 4.5p1-7 - experimental NSS keys support - correctly setup context when empty level requested (#234951) " was supposed to allow the Common Access Card (CAC) to work with the shipped Fedora 8 ssh. As per NSS usual, everything is undocumented, i.e., `ssh-add --help` does not help at all, and `man ssh-add` points to `ssh-add -s reader` # ssh-add -s 0 Enter passphrase for smartcard: SSH_AGENT_FAILURE Could not add card: 0 # ssh-add -s 1 Enter passphrase for smartcard: SSH_AGENT_FAILURE Could not add card: 1 So does anyone know how to use the possible functionality, or are we reduced to reading the source? -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter

4 8

Fedora 40: the last three kernels fail
by Walter H. 08 Sep '24

08 Sep '24

These three kernels kernel-6.10.4-200.fc40.x86_64 kernel-6.10.5-200.fc40.x86_64 kernel-6.10.6-200.fc40.x86_64 won't start my VM properly, ends in a black screen, where I can see mouse moventments, and that was it ... no login, nothing; kernel-6.10.3-200.fc40.x86_64 works fine using LXDM Thanks Walter

6 22

Apache fails to resume after hibernation
by Patrick O'Callaghan 07 Sep '24

07 Sep '24

I've noticed recently that Apache often (or perhaps always) doesn't respond after a system hibernate/resume cycle. After restarting it ('apachectl restart') all is well. I could script an automatic restart after resuming, but I wondered if this is a well-known problem with a simpler solution. poc

4 11

cups messages in boot logs.
by home user 05 Sep '24

05 Sep '24

good afternoon, (f39 standalone workstation, last patched Thursday, August 29) The next group of boot log messages of possible concern is related to cups. I hope that we don't need context lines for this. Here are the messages (with line numbers): - - - - - - 1634 Aug 30 08:11:11 coyote cupsd[1258]: Unknown directive BrowseOrder on line 6 of /etc/cups/cupsd.conf. 1635 Aug 30 08:11:11 coyote cupsd[1258]: Unknown directive BrowseAllow on line 7 of /etc/cups/cupsd.conf. 1636 Aug 30 08:11:11 coyote cupsd[1258]: Unknown directive BrowseRemoteProtocols on line 8 of /etc/cups/cupsd.conf. 1637 Aug 30 08:11:11 coyote cupsd[1258]: Unknown directive BrowseAddress on line 9 of /etc/cups/cupsd.conf. 1638 Aug 30 08:11:11 coyote cupsd[1258]: Unknown browse protocol "CUPS" ignored. 1639 Aug 30 08:11:11 coyote cupsd[1258]: Unknown directive JobPrivateAccess on line 97 of /etc/cups/cupsd.conf. 1640 Aug 30 08:11:11 coyote cupsd[1258]: Unknown directive JobPrivateValues on line 98 of /etc/cups/cupsd.conf. 1641 Aug 30 08:11:11 coyote cupsd[1258]: Unknown directive SubscriptionPrivateAccess on line 99 of /etc/cups/cupsd.conf. 1642 Aug 30 08:11:11 coyote cupsd[1258]: Unknown directive SubscriptionPrivateValues on line 100 of /etc/cups/cupsd.conf. 1643 Aug 30 08:11:12 coyote cupsd[1258]: Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 - - - - - - My printer is an HP Color Laser Jet Pro MFP M180nw. 1. (line 1643) What (if anything) should I do about this, or will future weekly patching or semi-annual upgrades take care of this? 2. Am I correct in assuming that the messages in lines 1634-1642 can be ignored? If no, what should I do about them? If it's relevant, I have something called "HPLIP Graphical Tools" on my workstation.

7 15

QXL drivers for Fedora Guest?
by ToddAndMargo 02 Sep '24

02 Sep '24

Hi All, On my Fedora 40 XFCe/MATE qemu-kvm guest virtual machine configures for QXL video. How do I install the guest QXL drivers? Yours in confusion, -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2 13

ACPI in boot log.
by home user 31 Aug '24

31 Aug '24

Good afternoon, (f39 standalone workstation last patched Thursday, August 29) My boot log (from journalctl -b > jlog.txt) contains the messages below. Note that for context, I'm including the last 5 lines before the errors and the first 5 lines after the errors. I left in short sequences of intervening lines; those might also provide context. I also added line numbers. - - - - - - 727 Aug 30 02:10:31 coyote kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci 728 Aug 30 02:10:31 coyote kernel: usb 3-1: new high-speed USB device number 2 using ehci-pci 729 Aug 30 02:10:31 coyote kernel: ata7: SATA link down (SStatus 0 SControl 300) 730 Aug 30 02:10:31 coyote kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) 731 Aug 30 02:10:31 coyote kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 732 Aug 30 02:10:31 coyote kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20240322/psargs-330) 733 Aug 30 02:10:31 coyote kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20240322/psparse-529) 734 Aug 30 02:10:31 coyote kernel: ata1.00: ATA-9: ST2000DM006-2DM164, CC26, max UDMA/133 735 Aug 30 02:10:31 coyote kernel: ata1.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 32), AA 736 Aug 30 02:10:31 coyote kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20240322/psargs-330) 737 Aug 30 02:10:31 coyote kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20240322/psparse-529) 738 Aug 30 02:10:31 coyote kernel: ata1.00: configured for UDMA/133 739 Aug 30 02:10:31 coyote kernel: scsi 0:0:0:0: Direct-Access ATA ST2000DM006-2DM1 CC26 PQ: 0 ANSI: 5 740 Aug 30 02:10:31 coyote kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20240322/psargs-330) 741 Aug 30 02:10:31 coyote kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 742 Aug 30 02:10:31 coyote kernel: sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB) 743 Aug 30 02:10:31 coyote kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks 744 Aug 30 02:10:31 coyote kernel: sd 0:0:0:0: [sda] Write Protect is off 745 Aug 30 02:10:31 coyote kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 746 Aug 30 02:10:31 coyote kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA 747 Aug 30 02:10:31 coyote kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes 748 Aug 30 02:10:31 coyote kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20240322/psparse-529) 749 Aug 30 02:10:31 coyote kernel: ata5.00: ATAPI: HL-DT-ST BD-RE BH14NS40, 1.00, max UDMA/100 750 Aug 30 02:10:31 coyote kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300) 751 Aug 30 02:10:31 coyote kernel: ata9: SATA link down (SStatus 0 SControl 300) 752 Aug 30 02:10:31 coyote kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20240322/psargs-330) 753 Aug 30 02:10:31 coyote kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20240322/psparse-529) 754 Aug 30 02:10:31 coyote kernel: ata5.00: configured for UDMA/100 755 Aug 30 02:10:31 coyote kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20240322/psargs-330) 756 Aug 30 02:10:31 coyote kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20240322/psparse-529) 757 Aug 30 02:10:31 coyote kernel: ata3.00: ATAPI: PIONEER BD-RW BDR-208M, 1.10, max UDMA/100 758 Aug 30 02:10:31 coyote kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20240322/psargs-330) 759 Aug 30 02:10:31 coyote kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT2._GTF due to previous error (AE_NOT_FOUND) (20240322/psparse-529) 760 Aug 30 02:10:31 coyote kernel: ata3.00: configured for UDMA/100 761 Aug 30 02:10:31 coyote kernel: scsi 2:0:0:0: CD-ROM PIONEER BD-RW BDR-208M 1.10 PQ: 0 ANSI: 5 762 Aug 30 02:10:31 coyote kernel: PM: Magic number: 4:730:170 763 Aug 30 02:10:31 coyote kernel: acpi device:33: hash matches 764 Aug 30 02:10:31 coyote kernel: RAS: Correctable Errors collector initialized. [... snip ...] 1181 Aug 30 08:10:44 coyote audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" host name=? addr=? terminal=? res=success' 1182 Aug 30 08:10:44 coyote systemd[1]: Stopped systemd-vconsole-setup.service - Virtual Console Setup. 1183 Aug 30 08:10:44 coyote systemd[1]: Stopping systemd-vconsole-setup.service - Virtual Console Setup... 1184 Aug 30 08:10:44 coyote systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup... 1185 Aug 30 08:10:44 coyote kernel: EDAC ie31200: No ECC support 1186 Aug 30 08:10:44 coyote kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20240322/utaddress-204) 1187 Aug 30 08:10:44 coyote kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver? 1188 Aug 30 08:10:44 coyote kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20240322/utaddress-204 ) 1189 Aug 30 08:10:44 coyote kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20240322/utaddress-204) 1190 Aug 30 08:10:44 coyote kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver? 1191 Aug 30 08:10:44 coyote kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20240322/utaddress-204 ) 1192 Aug 30 08:10:44 coyote kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20240322/utaddress-204) 1193 Aug 30 08:10:44 coyote kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver? 1194 Aug 30 08:10:44 coyote kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\_SB.PCI0.LPCB.GPBX) (20240322/utaddress-204 ) 1195 Aug 30 08:10:44 coyote kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20240322/utaddress-204) 1196 Aug 30 08:10:44 coyote kernel: ACPI: OSL: Resource conflict; ACPI support missing from driver? 1197 Aug 30 08:10:44 coyote kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich 1198 Aug 30 08:10:44 coyote kernel: asus_wmi: ASUS WMI generic driver loaded 1199 Aug 30 08:10:44 coyote kernel: asus_wmi: Initialization: 0x0 1200 Aug 30 08:10:44 coyote kernel: asus_wmi: BIOS WMI version: 0.9 1201 Aug 30 08:10:44 coyote kernel: asus_wmi: SFUN value: 0x0 - - - - - - There are many lines of concern, having something to do with "ACPI". Are these false alarms that I can ignore, or ticking time bombs that need attention soon, or a problem for which I've been lucky to not yet see symptoms (other than the log entries), or a major immediate problem? There are numerous other lines containing "ACPI", but those do not look like errors or warnings. I left those out. I don't really know what "ACPI" is... Annoying Confusing Puzzling Information? :) Actually, I don't know what this really is or what (if anything) I should do about it.

4 10

Dual boot failure after Windows update?
by Matthew Saltzman 31 Aug '24

31 Aug '24

Microsoft's August security update included a patch to prevent vulnerable GRUB2 (susceptible to bypassing UEFI secure boot) installations from booting. https://www.omgubuntu.co.uk/2024/08/windows-update-breaking-linux-dualboot-… The update was supposed to not install on already-configured dual boot systems, but that apparently failed, so lots of dual-boot systems had their Linux boot blocked after the update. I wondered if up-to-date Fedora users were affected by this issue. Would like to know before I apply Windows updates whether I will need to deal with it. TIA for any information, experiences. -- Matthew Saltzman School of Mathematical and Statistical Sciences Clemson University mjs AT clemson DOT edu

4 4

warning in log during boot.
by home user 30 Aug '24

30 Aug '24

Good morning, (f39 workstation last patched Thursday, August 22) My boot logs (from journalctl -b > log20240826.txt) contain the warning below. Note that for context, I'm including the last 5 lines before the warning and the first 5 lines after the warning. I also added line numbers. - - - - - - 1021 Aug 26 08:01:58 coyote systemd[1]: RTC configured in localtime, applying delta of -360 minutes to system time. 1022 Aug 26 08:01:58 coyote systemd[1]: Relabeled /dev, /dev/shm, /run, /sys/fs/cgroup in 78.112ms. 1023 Aug 26 08:01:58 coyote systemd[1]: systemd 254.16-1.fc39 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) 1024 Aug 26 08:01:58 coyote systemd[1]: Detected architecture x86-64. 1025 Aug 26 08:01:58 coyote systemd[1]: bpf-lsm: LSM BPF program attached /1026 Aug 26 08:01:58 coyote systemd-sysv-generator[595]: SysV service '/etc/rc.d/init.d/network' lacks a native systemd unit file. ~ Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it safe, robust and future-proof. ! This compatibility logic is deprecated, expect removal soon. !/ 1027 Aug 26 08:01:58 coyote systemd[1]: initrd-switch-root.service: Deactivated successfully. 1028 Aug 26 08:01:58 coyote systemd[1]: Stopped initrd-switch-root.service - Switch Root. 1029 Aug 26 08:01:58 coyote systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1. 1030 Aug 26 08:01:58 coyote systemd[1]: Created slice system-akmods\x2dkeygen.slice - Slice /system/akmods-keygen. 1031 Aug 26 08:01:58 coyote systemd[1]: Created slice system-getty.slice - Slice /system/getty. - - - - - - Line 1026 is the line of concern. Is this a false alarm that I can ignore, or a ticking time bomb (a warning that needs attention soon), a problem for which I've been lucky to not yet see symptoms (other than the log entry), or a major immediate problem? The warning suggests updating some package. I do a "dnf upgrade" weekly. Why did the update not already automatically happen?

6 13

Bind mounting hogs.
by R. Clayton 30 Aug '24

30 Aug '24

I'm having space pressure under /: Fedora 40 won't install because it runs out of space. I'm thinking I can solve this by moving some hogs from / into /home and bind mounting them back into / like so: /home/storage/cache /var/cache none bind /home/storage/flatpak /var/lib/flatpak none bind in fstab. Does this seem like a sensible approach? I'm running 39 under this scheme to see if it works in general. Will there be any surprises when I try to update or upgrade under this scheme?

4 8

[Heroes Of Fedora] A token of gratitude for all the hard work!
by Sumantro Mukherjee 29 Aug '24

29 Aug '24

Hello Fedorables, I wanted to take a moment to express my deepest gratitude to each one of you for your invaluable contributions to the Fedora 39 and 40 release cycles. Your dedication and hard work have played a crucial role in making these releases a success. You are truly amazing, and the Fedora QA team greatly values the time and effort you invest. Your contributions make a real difference, and we couldn't do it without you. I apologize for the delay in writing up the HoF, but please know that my appreciation for your efforts is unwavering. I have taken the liberty to add a few graphs and all FAS IDs of folks (even if they made a single contribution) Thank you once again for everything you do. [0] https://communityblog.fedoraproject.org/heroes-of-fedora-fedora-40-contribu… [1] https://communityblog.fedoraproject.org/heroes-of-fedora-fedora-39-contribu… -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED <https://redhat.com/trusted>

1 0

Reboot timeout
by Patrick O'Callaghan 28 Aug '24

28 Aug '24

When I reboot the system, there's a delay of around a minute before anything happens. This is a single-user desktop and I really don't need to stare at a spinner for so long. Is there a setting somewhere that lets me change this? I'm aware of 'reboot -f' but I assume that would normally be too drastic. poc

14 35

Fresh install Fedora 40.
by Ger van Dijck 28 Aug '24

28 Aug '24

Hi All, I had a total crash on my PC and had to restore Windows 10 Professionel by using Veeam Recorvery. This was succesfull , but the bootloader was gone and Fedora 40 also . I did install a 1 Terra SSD drive . I burned a netinstall DVD Fedora 40 and tried to install Fedora 40 : Normally this is no problem ,but I am not able to create the correct disk partitioning . See following disk layout. sda1 partition ntfs 348.71 Mb system reserved. sda2 partition ntfs 195.35 Gb Windows 10 Professionel (C:\). sda 3 partition 251.02 Gb. sda 5 partition ntfs 251.02 Gb Ger Pro (D:\) free space 484.79 Gb. Fedora 40 should be installed (fresh) on the free space partition , but one way or another I do not manage. Any help would be usefull. Regards, Ger van Dijck. -- Gemaakt met Opera's e-mailprogramma: http://www.opera.com/mail/

3 2

smartd configuration problem
by Robert McBroom 28 Aug '24

28 Aug '24

Boot process f40 system stops for a long time with a problem with smartd. Seems to access the system drives and note that they are SMART capable. The following entries are in the journal smartd[977]: Warning via /usr/libexec/smartmontools/smartdnotify to root produced>> smartd[977]: No configuration file found at (null) or /etc/esmtprc After multiple entries smartd[977]: No configuration file found at (null) or /etc/esmtp The files referenced are not in /etc. Don't see such files on a f39 system What is the system looking to find and where can it be found.

5 7

can't ssh into fedora lxc-container
by Mike Wright 26 Aug '24

26 Aug '24

Hi gurus, I've installed f40 as an lxc container named FED. Default image comes without an ssh server so I "dnf install openssh-server -y" followed by "systemctl start sshd". It fails. journalctl -xeu sshd shows this: "FED (sshd)[636]: sshd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS" Inspection of the sshd.service file shows these as part of the [Service] section: EnvironmentFile=-/etc/sysconfig/sshd ExecStart=/usr/sbin/sshd -D $OPTIONS Apparently /etc/sysconfig/sshd is supposed to contain at least one named variable ( name appears to be unimportant ). Searches showed the options name to be SSHD_OPTS, journalctl says it is looking for OPTIONS, either work if declared correctly. OPTIONS= fails because OPTIONS is null OPTIONS='' works because it is defined but empty. My question is: since the sshd.service file expects -D $OPTIONS shouldn't /etc/sysconfig/sshd define the OPTIONS variable ahead of time? If the user wants to pass values via $OPTIONS they can do so of their own accord but the service should at least start without modification to sysconfig/sshd ( IMHO ). Does this call for bugzilla? Thanks, Mike Wright

1 1

Waking from suspend
by Patrick O'Callaghan 26 Aug '24

26 Aug '24

Having failed to get hibernation working (see recent posts about Secure Boot getting in the way), I tried to fall back to suspending the system overnight. That works of course. What doesn't work is waking it up automatically. If the RTC can wake the system from hibernation, why can't it wake it from suspension? I don't want to have to be in front of the system to wake it up. poc

7 18

Can't ssh into fedora container (lxc): redux
by Mike Wright 25 Aug '24

25 Aug '24

Hi all, Now that sshd is working as a service I tried to ssh in and got bounced out. Trying again with ssh -v FED ( container's name ) yields: debug1: Server accepts key: /home/mike/... journalctl -xeu sshd shows: FED unix_chkpwd[881]: could not obtain user info (mike) FED sshd[735]: fatal: Access denied for user mike by PAM account configuration [preauth] ( mike exists and has a password ) I've never run into this before. If I remember correctly this didn't happen with f38. I skipped f39. I've since destroyed f38 and can't recreate it to verify ( did it term out and is no longer in the repository? ) Some searches have said a user must attempt to login a first time before they are "setup" in the system ( is that the [preauth] ? ). Since the containers are headless that isn't possible. I tried attaching to the container ( as root ) and using sudo to become mike but that asks for a password which also fails and I get the same journalctl errors "fatal: Access denied..." Does anybody know of another way to validate new accounts? Thanks, Mike Wright

2 1

Strange laptop behavior #2
by Paolo Galtieri 25 Aug '24

25 Aug '24

Folks, I previously sent a message regarding my laptop powering off unexpectedly. Here is an update. Power came back on, but I cannot login to my laptop. When I try to login to the mate gui it replies with power failure and authentication failure. If I enter ctrl-alt-F1, login as root I can login. If I then enter su - pgaltieri I can login as me. If I then enter su - pgaltieri it prompts for password and when I enter my passwd I can login just fine. This problem occurs on both my systems there were shutdown due to the power outage. What do I have to do to be able to log in? This is happening with F39 and F40. Paolo

5 7

KVM image fails to resume after f38->40 upgrade
by Eyal Lebedinsky 25 Aug '24

25 Aug '24

Following an upgrade of the host (38->40) I could not start the vm. The VM was running f40 for a while just fine. It was "virsh save"d a few days ago. $ sudo virsh save e4 /data1/VMs/libvirt/images/e4.saved Normally I actually stop it but forgot to do it this time. $ sudo virsh restore '/data1/VMs/libvirt/images/e4.saved' -rw-r--r-- 1 qemu qemu 512110190592 Jul 8 18:36 /data1/VMs/libvirt/images/e4.raw -rw------- 1 root root 8472278573 Jul 8 18:37 /data1/VMs/libvirt/images/e4.saved error: Failed to restore domain from /data1/VMs/libvirt/images/e4.saved error: operation failed: guest CPU doesn't match specification: extra features: vmx-ins-outs,vmx-true-ctls,vmx-store-lma,vmx-activity-hlt,vmx-vmwrite-vmexit-fields,vmx-apicv-xapic,vmx-ept,vmx-desc-exit,vmx-rdtscp-exit,vmx-vpid,vmx-wbinvd-exit,vmx-unrestricted-guest,vmx-rdrand-exit,vmx-invpcid-exit,vmx-vmfunc,vmx-shadow-vmcs,vmx-rdseed-exit,vmx-pml,vmx-ept-execonly,vmx-page-walk-4,vmx-ept-2mb,vmx-ept-1gb,vmx-invept,vmx-eptad,vmx-invept-single-context,vmx-invept-all-context,vmx-invvpid,vmx-invvpid-single-addr,vmx-invvpid-all-context,vmx-intr-exit,vmx-nmi-exit,vmx-vnmi,vmx-preemption-timer,vmx-vintr-pending,vmx-tsc-offset,vmx-hlt-exit,vmx-invlpg-exit,vmx-mwait-exit,vmx-rdpmc-exit,vmx-rdtsc-exit,vmx-cr3-load-noexit,vmx-cr3-store-noexit,vmx-cr8-load-exit,vmx-cr8-store-exit,vmx-flexpriority,vmx-vnmi-pending,vmx-movdr-exit,vmx-io-exit,vmx-io-bitmap,vmx-mtf,vmx-msr-bitmap,vmx-monitor-exit,vmx-pause-exit,vmx-secondary-ctls,vmx-exit-nosave-debugctl,vmx-exit-load-perf-global-ctrl,vmx-exit-ack-intr,vmx-exit-save-pat,vmx-exit-load-pat,vmx-exit-save-efer,vmx-exit-load-efer,vmx-exit-save-preemption-timer,vmx-entry-noload-debugctl,vmx-entry-ia32e-mode,vmx-entry-load-perf-global-ctrl,vmx-entry-load-pat,vmx-entry-load-efer,vmx-eptp-switching Then, trying to resume from the UI gets the message: ===== Error unpausing domain: Requested operation is not valid: domain is not running Error unpausing domain: Requested operation is not valid: domain is not running Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/virt-manager/virtManager/object/domain.py", line 1437, in resume self._backend.resume() File "/usr/lib64/python3.12/site-packages/libvirt.py", line 2425, in resume raise libvirtError('virDomainResume() failed') libvirt.libvirtError: Requested operation is not valid: domain is not running ===== Looking at the VM details I see: CPU model Skylake-Client-IBRS $ virsh --version 10.1.0 $ qemu-x86_64 --version qemu-x86_64 version 8.2.2 (qemu-8.2.2-1.fc40) Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers What is the correct way to resume this image? -- Eyal at Home (fedora(a)eyal.emu.id.au)

5 13

Re: Managing guest VMs on Fedora KVM host
by C. Linus Hicks 24 Aug '24

24 Aug '24

> Hi, > > I have some Linux VMs that are running out of space. Is there a tool I can > use to manage their .IMG or .QCOW files? > > In particular, I have a build farm with some Linux machines using LVM > filesystems, and I need to resize their PV’s and LV’s, grow the ext4 or xfs > filesystems, etc. inside those .IMG and .QCOW files. > > In some cases the partition I want to grow is sandwiched between others. > > What’s available? > > I saw a Redhat Access blog that mentioned virt-filesystems, but it doesn’t > seem to be built for my OS. You can use qemu-img to resize the img and qcow files. Then you can resize existing partitions or if you don't want to mess with that, resize the PV and then extend your LVs into that space. It's been a while since I've done that, but it's pretty straightforward.

1 0

Managing guest VMs on Fedora KVM host
by Philip Prindeville 24 Aug '24

24 Aug '24

Hi, I have some Linux VMs that are running out of space. Is there a tool I can use to manage their .IMG or .QCOW files? In particular, I have a build farm with some Linux machines using LVM filesystems, and I need to resize their PV’s and LV’s, grow the ext4 or xfs filesystems, etc. inside those .IMG and .QCOW files. In some cases the partition I want to grow is sandwiched between others. What’s available? I saw a Redhat Access blog that mentioned virt-filesystems, but it doesn’t seem to be built for my OS. Thanks, -Philip

3 2

OT: UEFI settings for DDR5 RAM
by Patrick O'Callaghan 24 Aug '24

24 Aug '24

Apologies in advance if this is too OT. I recently installed a new system based on an MSI B650-P motherboard with an AMD Ryzen 7600 and Corsair DDR5 RAM. The RAM specs show a recommended frequency of 5200 MHz, but the UEFI screen shows it running at 4800MHz (even though it also notes the correct spec). Here's a screenshot link: https://drive.google.com/file/d/1Z21GpYtO9jgNA5RDVh6qz2EShbVCRWCw/view?usp=… The MSI docs are atrocious and I can't see any way of changing the DRAM frequency. Not a big deal really but if anyone has any ideas I'd appreciate the feedback. poc

9 20

Secondary SSH
by Dave Close 24 Aug '24

24 Aug '24

I have several local machines that, while working, I frequently use ssh to do something on a different machine. While on that second machine, I may even use ssh to do something on a third machine. All of this works exactly as it should. If I use JuiceSSH on my Android phone to contact one of my local machines, that also works well. But if, while connected, I try to start an ssh session to a different local machine, it simply times out. The last message seen with "ssh -vvv" is, "debug3: ssh_get_authentication_socket_path:". Up to that point, the output of "ssh -vvv" is identical when running successfully between two local machines without using JuiceSSH. If instead of trying to start an ssh session immediately upon connecting with JuiceSSH, I first use sudo to become root on the local machine and then try to ssh to another local machine, that works perfectly (provided, of course, that the second machine permits root ssh login). The second ssh session also works if I simply run "sudo su {me} -c ssh" so becoming root isn't the key. Summary: JuiceSSH -> user@machine1 -> user@machine2 :: FAILS JuiceSSH -> user@machine1 -> sudo on machine1 -> user@machine2 :: WORKS I've examined the output of the set command for all of these situations and can't find any variables that are different that seem relevant. (Of course, $PPID and similar variables are different.) Can anyone suggest what could be the issue? Or what other tests might be helpful? -- Dave Close, Compata, Irvine CA +1 714 434 7359 dave(a)compata.com dhclose(a)alumni.caltech.edu "Life resembles a novel more often than novels resemble life." -- George Sand

3 6

Unexpected laptop behavior
by Paolo Galtieri 24 Aug '24

24 Aug '24

I normally run my laptop on AC power. I also have it plugged into a UPS. Today the power went out. The power applet on the mate desktop reported I had 7298 hours of laptop run time and 5 minutes of UPS. The laptop then powered itself off. Can someone tell me what I might have have misconfigured? Paolo

3 2

Hibernation vs Secure Boot
by Patrick O'Callaghan 23 Aug '24

23 Aug '24

I keep getting this in the journal: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 and a glance at the man page reveals that hibernation and secure boot don't play nice unless the swap image filesystem is encrypted. My immediate reaction is to disable Secure Boot, but I'd like to know if there's an easy workaround, bearing in mind that my system is set to hibernate overnight and wake up automatically in the morning, without me having to type in a password. poc

2 3