users June 2019

users@lists.fedoraproject.org

122 participants
137 discussions

Why Must I Do "dnf clean all" Before Updating Will Proceed?
by Garry Williams 07 Jun '19

07 Jun '19

On most occasions I have to clean files before I am allowed to update a Fedora 30 system: garry@ifr$ sudo dnf upgrade [sudo] password for garry: Fedora 30 - x86_64 - Updates 63 kB/s | 18 kB Fedora 30 - x86_64 - Updates 226 kB/s | 659 kB Failed to synchronize cache for repo 'updates' Error: Failed to synchronize cache for repo 'updates' garry@ifr$ sudo dnf clean all 68 files removed garry@ifr$ sudo dnf upgrade Fedora 30 openh264 (From Cisco) - x86_64 11 kB/s | 5.1 kB Fedora 30 - x86_64 - Updates 2.3 MB/s | 12 MB Fedora 30 - x86_64 1.0 MB/s | 70 MB google-chrome 37 kB/s | 3.4 kB Copr repo for qt5-qtbase-print-dialog-advanced o 91 kB/s | 100 kB RPM Fusion for Fedora 30 - Free - Updates 128 kB/s | 130 kB RPM Fusion for Fedora 30 - Free 570 kB/s | 735 kB RPM Fusion for Fedora 30 - Nonfree - Updates 54 kB/s | 34 kB RPM Fusion for Fedora 30 - Nonfree 449 kB/s | 227 kB Visual Studio Code 363 kB/s | 2.1 MB Dependencies resolved. ================================================================== Does anyone know what is special about this system that it requires clean all before it will update? I have two other systems that never experience the same problem. -- Garry Williams

9 12

qemu
by Patrick Dupre 06 Jun '19

06 Jun '19

Hello, It is say: You can test your stick using QEMU. qemu -hda /dev/sdX -m 1024 -vga std I installed qemu (dnf install qemu). Then qemu -hda /dev/sdc -m 1024 -vga std bash: qemu: command not found... What I am doing wrong? Thank. =========================================================================== Patrick DUPRÉ | | email: pdupre(a)gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 ===========================================================================

5 7

How do I regenerate the grub files for a UEFI system ?
by linux guy 06 Jun '19

06 Jun '19

How do I regenerate the grub files for a UEFI system to boot from ? Thanks

4 8

WiFi now disabled by radio killswitch
by Paolo Galtieri 06 Jun '19

06 Jun '19

Folks, on both June 2 and June 4 I have seen the following message in the logs: Jun 4 13:35:53 terrapin NetworkManager[1529]: <info> [1559680553.5293] manager: rfkill: WiFi now disabled by radio killswitch Until I shutdown my system and reboot I cannot connect to my WiFi network. Has anyone else seen this and can tell why I'm getting it? The first time this message appears is on June 2. Paolo

3 2

5.1 kernel and 32 bit executables?
by Tom Horsley 06 Jun '19

06 Jun '19

I have some very, very old (ancient, in fact) 32 bit statically linked executables run as part of a testbed. With the new 5.1.6-300.fc30.x86_64 kernel installed this morning, they are all failing because the programs are confused by something in the initial code before they even get to the main program. Anyone know if there is some major new difference in i386 support in the new kernel? (When I get a chance I'll boot the old kernel and make sure it still works and this isn't something different than I suspect).

2 3

Cloning of existing fedora install failing at switch root. Does systemd keep system state?
by stan 06 Jun '19

06 Jun '19

Hi, I'm trying to clone an existing Fedora install, just a / partition and a /boot partition, both ext4. I use rsync, # rsync -C -x -u -a -v -A -X /mnt/old/ /mnt/new to clone both partitions from a running Fedora. I then clean up the /etc/fstab and /boot/grub2/grub.cfg by changing the UUIDs of the / and boot partitions. Formerly, that would be enough. I would run mkconfig to find the new installs from an existing Fedora, and boot into them from the grub menu of that existing install. That failed at switch root. Research found that the initramfs is now hostonly, so will not boot on a different root. I generated a new initramfs using dracut with --no-hostonly on the existing / old install, and copied it to the new /boot. Then altered the new grub.cfg to use that as the initramfs, ran mkconfig in the existing / old install to pick up the change, and rebooted. Still not working, though it now fails because systemd kills itself after switch root. And hangs because it can't find /bin/bash. As near as I can tell, everything is there. /usr/sbin/init links to /usr/lib/systemd/systemd, and the initramfs has those links in it, so why is switch root failing? The only thing I can come up with is that systemd somehow keeps track of the system it was installed on, and is failing to find something from the old system because it isn't mounted. Can anyone offer any insight?

5 17

28 --> 30
by ToddAndMargo 06 Jun '19

06 Jun '19

Hi All, I updated two virtually identical Fedora 28 servers to Fedora 30 yesterday. The first one had mechanical drives and the second had SSD drives. Motherboard, memory, processor were identical. The second one when perfectly. The first one, after issuing "dnf system-upgrade reboot" did its thing up to the transaction checks. I got bored and walked away. a minute later it was all booted back up, but was still in 28. I googled the issue and could not really find anything. So I reissued "dnf system-upgrade reboot" and this time it completed the upgrade. Go figure ... The first one with the mechanical drives and took 2 hours and 38 minutes. The second one with the SSD drives and took 36 minutes. -T

1 0

F30 libvirt dnsmasq glitch
by Peter Boy 06 Jun '19

06 Jun '19

I installed KVM/libvirt on a new F30 installation. Surprisingly, 2 instances of dnsmasq are launched: [root@base ~]# ps -ef | grep dnsmasq dnsmasq 1531 1 0 11:33 ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper root 1533 1531 0 11:33 ? 00:00:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper root 2450 2391 0 11:39 pts/2 00:00:00 grep --color=auto dnsmasq The second instance is not connected to any port. [root@base ~]# netstat -tulpn | grep dnsmasq tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 1531/dnsmasq udp 0 0 192.168.122.1:53 0.0.0.0:* 1531/dnsmasq udp 0 0 0.0.0.0:67 0.0.0.0:* 1531/dnsmasq And I can kill the second instance without any harm I noticed yet. Is that second instance intended behaviour for some reason? Or is it used for a function I didn’t notice yet? Can someone reproduce that behaviour? Is it a bug of my installation? Thanks Peter

1 0

f29 to f30 and grub config only memtest present
by Gianluca Cecchi 05 Jun '19

05 Jun '19

Hello, on a pc where I had both Windows 7 and Fedora 29, with boot loader configured in linux and grub2, I have run the update to Fedora 30 using the usual procedure described here, and already completed on another pc (but without the dual boot...): https://fedoramagazine.org/upgrading-fedora-29-to-fedora-30/ after the commad sudo dnf system-upgrade reboot I saw the laptop rebooting, installing all the about 9k packages, than verifying them and as soon as it had verified the last one, I saw again reboot (is it expected?), but then in grub options I only see memtest windows 7 windows 7 recovery environment So I think something went bad in updating grub2 config... Any hint on how to recover grub, eventually booting from a usb stick in any way? Already happened to anyone else with f29 to f30? I followed on the same laptop the same procedure without problems from f26 (or f27) to f29 until this problem. Thanks, Gianluca

2 5

a stop job.... systemd again and again....
by François Patte 05 Jun '19

05 Jun '19

Bonjour, "a stop job is running for rc.local compatibility no limit" This a new fantasy of systemd on my system when I shut it down and there is "no limit": after half a hour, the computer stops with this message: "forcibly powering off: job timed out". This is boring! Why this? I made no update, no change in my configuration which worked correctly... What is this job? We cannot know... *A job* that's all we can know! Looking at the journal (journalctl -u rc-local) shows nothing wrong. How to stop this weird behavior? systemd was supposed to increase the speed, in fact since systemd replaced the previous system boot takes more time (30s instead of 10s if no "start job is running" occurs...) and I did not see any change in the speed of the computer. Thank you. -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)6 7892 5822 http://www.math-info.univ-paris5.fr/~patte

3 2

Jump to page: