users May 2019

users@lists.fedoraproject.org

130 participants
125 discussions

Fedora 30, BootLoaderSpec and generating entries under /boot/loader/entries
by Kevin Wilson 28 May '19

28 May '19

Hi all, I had installed Fedora 30, on a dual boot machine which has a second partition with Fedora 28. Fedora 30 comes by default with a new boot loader spec. I found under /boot/loader/entries/ the following: ls /boot/loader/entries/ ec1b8b7719964c8b9a1d8db430c63fd6-0-rescue.conf ec1b8b7719964c8b9a1d8db430c63fd6-5.0.9-301.fc30.x86_64.conf0 I want to be able to boot by default into Fedora 28. Is there a way by some utility to generate entries under /boot/loader/entries/ for the Fedora 28 and choose Fedora 28 as the default ? Or should I disable the boot loader spec in order to boot to Fedora 28 on this machine ? Regards, Kevin

3 3

is grubby a dumb software?
by François Patte 27 May '19

27 May '19

Bonjour, For a long time now grubby has replaced grub2-mkconfig to update the grub.cfg file. From this time, I have to correct the kernel update manualy with grub2-mkconfig because every time grubby chooses a wrong partition as the / partition. The choosen partition is not mounted, it is empty, with no boot flag.... Why grubby chooses this partition? It is so stupide that I am wondering what is the way followed by grubby to to this? Thank you for any light. -- 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

7 9

F28, openvpn, NetworkManager
by Jack Craig 27 May '19

27 May '19

hi all, anyone got openvpn doing proper route management with vpn start/stop? my take appears to suggest NM to be the problem, but short on proof. anyone? tia, jackc...

3 11

DHCP fails on wired Ethernet after F29-F30 upgrade
by Robert G. (Doc) Savage 27 May '19

27 May '19

I've been running F30 on my Lenovo P72 laptop since upgrading to the beta. I had all sorts of SELinux problems until I reset the contexts. Now there's one last problem I haven't been able to fix and that's the wired Ethernet port. Whenever I connect to it, the NetworkManager applet loops and loops without ever getting a DHCP address. It worked fine in F29, and so does the WiFi port with DHCP in F30. systemd baffles me, and the lack of /var/log/messages doesn't give me much to look thru. I've run 'journalctl -u NetworkManager' to see what happens when I plug in the RJ-45 connector, then disconnect it: May 25 02:18:33 tiger.protogeek.org NetworkManager[1217]: <info> [1558768713.6461] device (enp0s31f6): carrier: link connected May 25 02:18:33 tiger.protogeek.org NetworkManager[1217]: <info> [1558768713.6464] device (enp0s31f6): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') May 25 02:18:33 tiger.protogeek.org NetworkManager[1217]: <info> [1558768713.6478] device (enp0s31f6): Activation: starting connection 'Ethernet' (8b81adbf-22bf-3f18-ba5e-85f78dc4fa17) May 25 02:18:33 tiger.protogeek.org NetworkManager[1217]: <info> [1558768713.6480] device (enp0s31f6): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') May 25 02:18:33 tiger.protogeek.org NetworkManager[1217]: <info> [1558768713.6484] device (enp0s31f6): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 25 02:18:33 tiger.protogeek.org NetworkManager[1217]: <info> [1558768713.6845] device (enp0s31f6): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') May 25 02:18:33 tiger.protogeek.org NetworkManager[1217]: <info> [1558768713.6848] dhcp4 (enp0s31f6): activation: beginning transaction (timeout in 45 seconds) May 25 02:18:33 tiger.protogeek.org NetworkManager[1217]: <info> [1558768713.6863] dhcp4 (enp0s31f6): dhclient started with pid 21697 May 25 02:18:33 tiger.protogeek.org dhclient[21697]: DHCPDISCOVER on enp0s31f6 to 255.255.255.255 port 67 interval 4 (xid=0x94236275) May 25 02:18:37 tiger.protogeek.org dhclient[21697]: DHCPDISCOVER on enp0s31f6 to 255.255.255.255 port 67 interval 4 (xid=0x94236275) May 25 02:18:41 tiger.protogeek.org dhclient[21697]: DHCPDISCOVER on enp0s31f6 to 255.255.255.255 port 67 interval 11 (xid=0x94236275) May 25 02:18:48 tiger.protogeek.org NetworkManager[1217]: <info> [1558768728.5573] device (enp0s31f6): state change: ip-config -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed') May 25 02:18:48 tiger.protogeek.org NetworkManager[1217]: <info> [1558768728.5740] dhcp4 (enp0s31f6): canceled DHCP transaction, DHCP client pid 21697 May 25 02:18:48 tiger.protogeek.org NetworkManager[1217]: <info> [1558768728.5740] dhcp4 (enp0s31f6): state changed unknown -> done The wired Ethernet never comes up, but as soon as I unplug it the WiFi port's DHCP connection resumes perfectly. Can anyone suggest the next step? --Doc Savage

4 6

OT - Antivirus clean up USB
by Javier Perez 26 May '19

26 May '19

Hi. This is Off Topic. Is there a reliable usb or dvd distribution with tools to clean up viruses, root kits, whatever from a Hard drive? I got a quite slow windows 10 laptop from a nephew for clean up (I do not know what kind of viruses/malware might be lurking in there). Rather than hooking it to my home network I would prefer to first start it from a cleaning usb/dvd and at least catch and erase them off line instead of giving them the opportunity to try and conquer my linux realm :) Thanks -- ------------------------------ /\_/\ |O O| pepebuho(a)gmail.com ~~~~ Javier Perez ~~~~ While the night runs ~~~~ toward the day... m m Pepebuho watches from his high perch.

10 15

Kernel 5.0.17 Vega failing on boot.
by Leander Hutton 25 May '19

25 May '19

Hello, I have an AMD Ryzen with a Vega 56 graphics card running Fedora 30 and the 5.0.17 update the graphics output seems to just die after grub. Rolled back to the previous kernel (5.0.16) in grub and it comes up just fine. No errors or logs ... just sits there at the ASRock logo on screen after selecting the kernel. From what I can tell it is actually installed. Tried runlevel 1 and 3 as well and it does the same thing. The kernel works fine on my laptop but that's an Intel machine. Standard grub command line arguments except amddgpu.gpu_recovery=1 for the Vega card. I did also try it with that removed and still no go. I can SSH into it just fine but the screen is just sitting there with the BIOS manufacturer's logo, nothing telling in dmesg or /var/log/messages and it doesn't set off abrt. I'm running a pretty standard Fedora system with only some codecs and non-free software from rpmfusion. The only other thing I changed recently was adding the ROCm for OpenCL image support on my Radeon card. I removed those after I noticed this issue and reran dracut to no avail, reinstalled the kernel and all related packages as well. Nothing. Anyway, looks like I really loused something up. Luckily the older kernel still works fine. Any other ideas out there? Maybe the ROCm packages left something behind (removed with dnf remove)? Thanks! Leander

2 2

Possible nvidia driver
by rodmccown＠aircanopy.net 25 May '19

25 May '19

Updated Fedora 30 system with all latest, and latest kernel. Gnome doesn't start, but consoles seem to be ok and it does boot to multiuser....I think. When I reboot down into the previous kernel, 5.0.13-300.fc30.x86_64, everything works fine. > Wondering if there is a problem with the newer kernel and my nvidia card, GeForce GT 640. Haven't had time to really look yet, but wondering if anyone else has run across this? > Thanks. > Kindly do NOT hijack threads. Your message is completely unrelated to the one you are replying to, and changing the Subject line does not make it OK because the various list-related headers remain the same. Create a new message from scratch if you want people to reply. poc Also, Thanks Patrick O'Callaghan for so kindly informing me of how to ask for help on this user list. Last time I asked for help I was 2 versions behind on the OS and I got roasted because the OS version was too old. Maybe I should try Ubuntu.

3 3

fixrefox 67 - support for CSS media query prefers-color-scheme not working
by Barry Scott 25 May '19

25 May '19

I have firefox 67 install on f30 and its not honouring the prefers-color-scheme CCS media query. I use KDE in dark mode. This works for Firefox 67 on macOS. Is this expected to be working? Should I create bug report for this? Barry

3 2

OSM??
by Beartooth 24 May '19

24 May '19

Can dnf get me OSM? I tried osm, OSM, and openstreetmap. I don't doubt there's some sort of .iso on their own site, but with a program so vast ... -- Beartooth Staffwright, Not Quite Clueless Power User Remember I know little (precious little!) of where up is.

5 8

Vagrant vbguest on Fedora 30
by Paul-Erik Törrönen 24 May '19

24 May '19

Seems like there's a conflict between rubygem libs in Vagrant: $ vagrant plugin install vagrant-vbguest Installing the 'vagrant-vbguest' plugin. This can take a few minutes... /usr/share/gems/gems/psych-3.1.0/lib/psych.rb:237: warning: already initialized constant Psych::LIBYAML_VERSION /usr/share/ruby/psych.rb:237: warning: previous definition of LIBYAML_VERSION was here /usr/share/gems/gems/psych-3.1.0/lib/psych.rb:239: warning: already initialized constant Psych::NOT_GIVEN /usr/share/ruby/psych.rb:239: warning: previous definition of NOT_GIVEN was here Bundler, the underlying system Vagrant uses to install plugins, reported an error. The error is shown below. These errors are usually caused by misconfigured plugin installations or transient network issues. The error from Bundler is: conflicting dependencies fog-core (~> 1.43.0) and fog-core (= 2.1.2) Activated fog-core-2.1.2 which does not match conflicting dependency (~> 1.43.0) Conflicting dependency chains: fog-core (= 2.1.2), 2.1.2 activated versus: vagrant-libvirt (> 0), 0.0.41 activated, depends on fog-core (~> 1.43.0) I attempted to rebuild the vagrant/vagrant-libvirt package with definitions for a newer (2.1.2) fog-core but this did not seem to fix it. Installed packages: $ rpm -qa | grep vagrant vagrant-2.2.4-1.fc30.noarch vagrant-libvirt-0.0.45-1.fc30.noarch $ rpm -qa | grep fog-core rubygem-fog-core-2.1.2-2.fc30.noarch Any clues on how to get vagrant working again? TIA, Poltsi

1 1

← Newer
1
2
3
4
5
6
7
...
13
Older →