users May 2024

users@lists.fedoraproject.org

71 participants
75 discussions

/boot too small
by Patrick Dupre 04 Jun '24

04 Jun '24

Hello, During an update, I get Error Summary ------------- Disk Requirements: At least 7MB more space needed on the /boot filesystem. How can I fix it without currently resizing /boot? Thank drwx------. 5 root root 4096 May 14 08:36 grub2 lrwxrwxrwx. 1 root root 45 Mar 7 13:24 symvers-6.7.7-100.fc38.x86_64.xz -> /lib /modules/6.7.7-100.fc38.x86_64/symvers.xz -rw-------. 1 root root 81850041 Mar 7 13:24 initramfs-6.7.7-100.fc38.x86_64.img -rw-r--r--. 1 root root 269378 Mar 1 01:00 config-6.7.7-100.fc38.x86_64 -rw-r--r--. 1 root root 8851783 Mar 1 01:00 System.map-6.7.7-100.fc38.x86_64 -rwxr-xr-x. 1 root root 14794568 Mar 1 01:00 vmlinuz-6.7.7-100.fc38.x86_64 lrwxrwxrwx. 1 root root 45 Feb 13 17:38 symvers-6.7.4-100.fc38.x86_64.xz -> /lib /modules/6.7.4-100.fc38.x86_64/symvers.xz -rw-------. 1 root root 81905180 Feb 13 17:37 initramfs-6.7.4-100.fc38.x86_64.img -rw-r--r--. 1 root root 269327 Feb 5 01:00 config-6.7.4-100.fc38.x86_64 -rw-r--r--. 1 root root 8850577 Feb 5 01:00 System.map-6.7.4-100.fc38.x86_64 -rwxr-xr-x. 1 root root 14806856 Feb 5 01:00 vmlinuz-6.7.4-100.fc38.x86_64 lrwxrwxrwx. 1 root root 46 Jan 25 13:39 symvers-6.6.13-100.fc38.x86_64.xz -> /li b/modules/6.6.13-100.fc38.x86_64/symvers.xz -rw-------. 1 root root 42503616 Jan 25 13:39 initramfs-6.6.13-100.fc38.x86_64.img -rw-r--r--. 1 root root 266375 Jan 20 01:00 config-6.6.13-100.fc38.x86_64 -rw-------. 1 root root 8786049 Jan 20 01:00 System.map-6.6.13-100.fc38.x86_64 -rwxr-xr-x. 1 root root 14676712 Jan 20 01:00 vmlinuz-6.6.13-100.fc38.x86_64 -rw-r--r--. 1 root root 147744 Jan 7 01:00 memtest86+x64.bin drwx------. 4 root root 4096 Jun 20 2023 efi drwxr-xr-x. 2 root root 4096 Jun 20 2023 extlinux -rw-------. 1 root root 103940590 Jul 21 2022 initramfs-0-rescue-c60d54440c4d444a9eb5a084a65edf40.img -rwxr-xr-x. 1 root root 11802352 Jul 21 2022 vmlinuz-0-rescue-c60d54440c4d444a9eb5a084a65edf40 drwxr-xr-x. 3 root root 4096 Jul 21 2022 loader drwx------. 2 root root 16384 Jul 21 2022 lost+found =========================================================================== Patrick DUPRÉ | | email: pdupre(a)gmx.com ===========================================================================

11 17

Please stop hijacking /etc/resolv.conf
by Sam Varshavchik 04 Jun '24

04 Jun '24

I updated from F39 to F40. I used to have: /etc/resolv.conf -> /run/NetworkManager/no-stub-resolv.conf Everything got messed up because the update hijacked this symlink again: lrwxrwxrwx. 1 root root 39 May 29 09:44 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf I was confident that F39 did not have systemd-resolved installed, it must've been pulled into the update. I repeated the experiment on two other F39 systems today. I confirmed that neither one of them had systemd-resolved installed. F40 pulled it in, and the package's scriptlet clobbered /etc/resolv.conf It would be real nice if someone finally STOPed this repeated hijacking of /etc/resolv.conf, and breaking network connectivity, is this too much to ask? Although this was fairly simple to fix, this kind of behavior does not improve systemd's existing reputation.

9 23

Can Fedora REPLACE Android on Smart Phones?
by Philip Rhoades 31 May '24

31 May '24

People, I have messed around with Android ROMs in the past - mostly for fun - now I would like Fedora running on my old Pixel2XL, which is currently running the last available Lineage ROM available for it. I have been experimenting with proot and chroot - but these things just create Fedora containers - has anyone installed Fedora as the host OS on phones other than Pine64|Pinephone|Pine64 PinePhone Pro|Pine64 Pinetab (1 and 2)|Purism Librem 5|Oneplus 6 ? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil(a)pricom.com.au

2 1

SELinux is preventing key.dns_resolve from setattr access on the key labeled kernel_t.
by Go Canes 30 May '24

30 May '24

I have been getting the following SElinux alert: SELinux is preventing key.dns_resolve from setattr access on the key labeled kernel_t. Is it safe to create a rule to ignore this? Known issue?

1 0

vdagent drag and drop question
by ToddAndMargo 30 May '24

30 May '24

Hi All, Host: Fedora 39 $ rpm -qa spice\* spice-server-0.15.1-3.fc39.x86_64 spice-glib-0.42-3.fc39.x86_64 spice-gtk3-0.42-3.fc39.x86_64 spice-vdagent-0.22.1-6.fc39.x86_64 VM: Windows 11 23H2 Virtio-win-driver-installer 0.1.240 Virtio-win-guest-tools 0.1.240 I can drag and drop a file from my Linux host to a qemu-kvm Windows 11 virtual machine but I can not do it in reverse What am I doing wrong, this time? -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 1

2 installations on the same PC - Add partition in Ftab
by soles.g 29 May '24

29 May '24

Hello: I need help with two topics: a) install two Fedora40. Therefore I have two EFI and that creates 'problems' Is there anything I can do so the PC doesn't get 'confused'...? b) I would like to mount a partition from Ftab... ├─sda7 ext4 1.0 from fedora_37 8ff104f3-ee9g-41be-9b2e-2b97d88f17cb 83.3G 51% /run/media/soles_40/from fedora_37 /dev/sda7: LABEL="from fedora_37" UUID="8ff104f3-ee9g-41be-9b2e-2b97d88f17cb" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="2ef79c09-c5a1-5943-0722-10f22g41633e" When I mount it... the mount command tells me: /dev/sda7 on /run/media/soles_40/from fedora_37 type ext4 (rw,nosuid,nodev,relatime,seclabel,errors=remount-ro,uhelper=udisks2) Do I write that in Ftab...? I write in Spanish and 'san' Google translates. Thank you... Claudia Ah! and I know VERY little about computers... ;-)

8 19

size of fedora 40 live
by Patrick Dupre 29 May '24

29 May '24

Hello, Could somebody tell the size of the iso image of fedora 40 workstation live? I need to known before download. Thanks =========================================================================== Patrick DUPRÉ | | email: pdupre(a)gmx.com ===========================================================================

4 3

Trying to get drupal running
by Ryan Bach 29 May '24

29 May '24

This is what I have but it isn't working: <VirtualHost *:80> ServerAdmin admin(a)example.net ServerName drupal.example.net DocumentRoot /home/ryan/drupal <Directory /home/ryan/drupal> Allowoverride all </Directory> </VirtualHost>

4 3

Kernel 6.9 Test Week is underway
by Sumantro Mukherjee 29 May '24

29 May '24

Hey Folks, We are currently running the Kernel 6.9 Test Week[0] and this is an awesome opportunity to come and contribute to Fedora! If you are interested and have some spare time, feel free to join us and submit reports here[1] [0] http://fedoraproject.org/wiki/Test_Day:2024-05-26_Kernel_6.9_Test_Week [1] https://testdays.fedoraproject.org/events/187 -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0

MS Bitlocker Blue Screen on Reboot
by Tim Evans 28 May '24

28 May '24

Woke up yesterday to terminal messages about /var/log being read-only; all graphical apps (Thunderbird, Chrome) had crashed. So, I decided to reboot. Background first: this is a new (3-months-old) PC. It came with two disks, an NVME with Windows 11 pre-installed and an empty second HDD. I DID NOT boot the system in Windows when it arrived. Instead, I popped in a Fedora 39 Live thumbdrive, hit the BIOS hot key, and booted from the thumbdrive, then installed F39. Again, the system has never, ever, booted into Windows. Which means I have no Bitlocker recovery key, nor any means to access it. Contacting Microsoft won't do any good, since the system was never registered. (I will have to try Dell.) F39 install was successful, and I've been using the system ever since. Normal grub bootup, offering Fedora kernels, rescue boot, and Windows. So, getting back to yesterday, I went to reboot the system, and it came up with the blue MS Bitlocker screen, asking for the Bitlocker Recovery key. Have never seen this before. Then, I noted the "skip this drive" button on the Bitlocker screen, which brought up a second screen, with an alternative devices button. Clicking this reveals a "Fedora" button. Clicking it brings up the normal grub boot screen and away we go into Fedora. Repeating the reboot gets the same results. I have to click through the Bitlocker screens to get to a Fedora boot. Not a big, big deal, but this prevents any sort of unattended reboot from being possible. Suggestions for restoring the normal boot process, please? Thanks.

6 8