users July 2020

users@lists.fedoraproject.org

110 participants
112 discussions

Network Manager Wait Online service fails to start
by Robert G (Doc) Savage 13 Jul '20

13 Jul '20

I've started playing with DashBoard on F32. When I saw this error under Services, I wondered if it might be a factor in a WiFi problem. Has anyone else run into this? If so, how did you resolve it? --Doc Savage Fairview Heights, IL Network Manager Wait OnlineStatusFailed to startAutomatically starts Path/usr/lib/systemd/system/NetworkManager-wait-online.serviceRequiressystem.sliceNetworkManager.servicesysinit.targetWanted Bynetwork-online.targetConflictsshutdown.targetBeforenetwork-online.targetshutdown.targetAftersystem.slicebasic.targetNetworkManager.servicesystemd-journald.socketsysinit.targetService LogsJuly 12, 2020 8:32 PM Failed to start Network Manager Wait Online.systemd 8:32 PM NetworkManager-wait-online.service: Failed with result 'exit-code'.systemd 8:32 PM NetworkManager-wait-online.service: Main process exited, code=exited, status=1/FAILUREsystemd 8:31 PM Starting Network Manager Wait Online...systemd

2 1

Kernel hang-up without any stack trace
by Eshin Kunishima 13 Jul '20

13 Jul '20

Hello, I've met kernel hang-up without any stack trace from kernel 5.7.6 in the update testing repository. I did not find any usable messages in dmesg and journalctl(It said that its data was corruption after rebooting). Is there any method of collecting debug information in this situation? Environment: * Fedora 32 x86_64 * Kernel * 5.7.6-200.fc32 @updates-testing? * 5.7.7-200.fc32 @updates-testing * 5.7.8-200.fc32 @updates-testing * 5.7.8-200.fc32 (debug build) * External modules * nvidia 440.100-1.fc32 from rpmfusion * zfs 6f1db

2 1

newbie Bluetooth questions
by David 13 Jul '20

13 Jul '20

I have never used Bluetooth device in Linux, until today. Device ( a speaker ) paired, but would not connect. ( Disclaimer: I have a 6 year old ASUS motherboard ) Here are some terminal displays: [me@localhost ~]$ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor> Active: active (running) since Wed 2020-07-08 08:53:29 CDT; 4h 28min ago Docs: man:bluetoothd(8) Main PID: 756 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18759) Memory: 2.7M CPU: 192ms CGroup: /system.slice/bluetooth.service └─756 /usr/libexec/bluetooth/bluetoothd Jul 08 08:53:28 localhost.localdomain systemd[1]: Starting Bluetooth service... Jul 08 08:53:29 localhost.localdomain bluetoothd[756]: Bluetooth daemon 5.54 Jul 08 08:53:29 localhost.localdomain systemd[1]: Started Bluetooth service. Jul 08 08:53:29 localhost.localdomain bluetoothd[756]: Starting SDP server Jul 08 08:53:29 localhost.localdomain bluetoothd[756]: Bluetooth management int> Jul 08 08:53:29 localhost.localdomain bluetoothd[756]: *Failed to set mode*: Bloc> Jul 08 08:53:39 localhost.localdomain bluetoothd[756]: *Failed to set mode*: Bloc> Jul 08 13:06:01 localhost.localdomain bluetoothd[756]: Endpoint registered: sen> Jul 08 13:06:01 localhost.localdomain bluetoothd[756]: Endpoint registered: sen> [me@localhost ~]$ bluetoothctl Agent registered [bluetooth]# show Controller E0:B9:A5:F3:04:9C (public) Name: localhost.localdomain Alias: localhost.localdomain Class: 0x001c0104 Powered: yes Discoverable: yes DiscoverableTimeout: 0x00000000 Pairable: yes UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Headset AG (00001112-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: OBEX File Transfer (00001106-0000-1000-8000-00805f9b34fb) UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb) UUID: IrMC Sync (00001104-0000-1000-8000-00805f9b34fb) UUID: Message Access Server (00001132-0000-1000-8000-00805f9b34fb) UUID: OBEX Object Push (00001105-0000-1000-8000-00805f9b34fb) UUID: Phonebook Access Server (0000112f-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0536 Discovering: yes Advertising Features: ActiveInstances: 0x00 SupportedInstances: 0x05 SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name [CHG] Device 7C:B4:7F:21:F0:D1 RSSI: -61 [CHG] Device 7C:B4:7F:21:F0:D1 RSSI: -63 [CHG] Device 7C:B4:7F:21:F0:D1 RSSI: -70 David Locklear

4 16

unmount automatically mounted USB devices by systemd-udevd
by Angelo Moreschini 13 Jul '20

13 Jul '20

Hi, I made a script that (using rsync <linux utility>) run a backup of some (particular) data of my computer. I use an external USB-HD to store data of the backup and, of course, I need to mount this HD-device before. A problem come because systemd-udevd automatically mount plugged USB devices when they are connected to computer. I my “simple” mind, I fund that this automatically mounted point is” */run/media/$USER/partition_label (...this says Gparted…).* In this way, before that I manually mount the partition in order to use the rsync command I do: *umount /run/media/$USER/partition_label. * This in OK! (this is working) ! But this is only a my empiric solution to the problem, and looking for <”linux how to manually unmounting the automatically mounted usb device by system-udevd”> I didn't find nothing *exactly* appropriate for my problem. I know that are different solutions (using udev rules) to manage the automatic montage of devices, but since I already have a good script that work, I only would like find an “official instruction” for the problem to manually unmout automatically mounted USB devices by systemd-udev. Can I have some help ? thank you Angelo lists.fedoraproject.org

2 2

tty
by Patrick Dupre 11 Jul '20

11 Jul '20

Hello, When I make ctl/alt F3 to open a tty connection, I can login, but, then I get /home/user: change directory failed: permission denied cd /home/user works fine /home/user as the following permission drwx Thanks =========================================================================== 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 ===========================================================================

3 2

Can't boot VM with a passthrough DVD
by Konstantin Svist 10 Jul '20

10 Jul '20

I've set up a win10 virtual machine in VMM QEMU/KVM and trying to pass through a DVD. The virtual disk setting in the VM suggests /dev/sr0, but whenever I select that, the machine refuses to boot with the following error: Error starting domain: internal error: child reported (status=125): unable to open /dev/sr0: Read-only file system Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 66, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/object/domain.py", line 1279, in startup self._backend.create() File "/usr/lib64/python3.7/site-packages/libvirt.py", line 1136, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirt.libvirtError: internal error: child reported (status=125): unable to open /dev/sr0: Read-only file system I've tried changing the disk bus (SATA/SCSI), and flipping "Shareable" toggle, neither one helps. Storage format is set to "raw" (text), not sure what else it should be.. Any help?

4 13

Configure static IP address in F32 container
by Michael Eager 10 Jul '20

10 Jul '20

I'm having a difficult time configuring the IP address of an interface in a Fedora 32 in a LXD container. The configuration for eth0 in /etc/sysconfig/network-scripts/: # cat ifcfg-eth0 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=no IPV6_DEFROUTE=no IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=eth0 DEVICE=eth0 ONBOOT=yes IPADDR=192.168.20.43 PREFIX=24 GATEWAY=192.168.20.1 IPV6_DISABLED=yes DNS1=192.168.20.1 DNS2=75.75.75.75 DNS3=8.8.8.8 HWADDR=00:16:3e:d1:ea:86 When I start the container, eth0 gets two IP addresses. One is the IP specified in the ifcfg-eth0 file. The other is a DHCP address. I'm assuming that NetworkManager is getting the DHCP address. I tried adding NMCONTROLLED=no to the ifcfg, but I get the same double IP assignment. I've tried removing the ifcfg-eth0 file and configuring the interface using nmcli as described here: https://linuxconfig.org/how-to-configure-static-ip-address-on-fedora-31 That doesn't work. When the container restarts, a new eth0 is created with a different UUID. Any suggestions would be appreciated. -- Michael Eager

4 3

Re: Kernel Headers problem trying to run Virtual Box
by Ed Greshko 10 Jul '20

10 Jul '20

On 2020-07-10 18:51, Mark Roberts wrote: > Thanks Ed, > > The versions that I have installed (from the rpm command you mentioned are) : > > kernel-devel-5.7.7-200.fc32.x86_64 > kernel-5.7.7-200.fc32.x86_64 > kernel-5.6.19-300.fc32.x86_64 > kernel-modules-5.6.6-300.fc32.x86_64 > kernel-5.6.6-300.fc32.x86_64 > kernel-core-5.6.19-300.fc32.x86_64 > kernel-core-5.6.6-300.fc32.x86_64 > kernel-modules-extra-5.6.19-300.fc32.x86_64 > kernel-modules-extra-5.7.7-200.fc32.x86_64 > kernel-headers-5.7.7-200.fc32.x86_64 > kernel-modules-5.6.19-300.fc32.x86_64 > kernel-core-5.7.7-200.fc32.x86_64 > kernel-modules-5.7.7-200.fc32.x86_64 > kernel-modules-extra-5.6.6-300.fc32.x86_64 > > At the risk of asking a stupid question - How do I boot the kernel at 5.7.7 ? > Well, first of all, the install of a new kernel should have resulted in subsequent boots using the latest installed. I think you may be running Fedora Workstation which now currently defaults to not showing the menu. If that is the case, you can hit the escape key at the boot which will bring up the menu and allow you to select kernel-5.7.7-200. -- The key to getting good answers is to ask good questions.

1 1

Kernel Headers problem trying to run Virtual Box
by Mark Roberts 10 Jul '20

10 Jul '20

Hi all, I have a Fedora 32 laptop with kernel : 5.6.19-300.fc32.x86_64 This seems to be the latest available. To use VirtualBox I need to configure it and that requires that I install kernel headers. The current version I have installed is : kernel-devel-5.7.7-200.fc32.x86_64 I can't find the kernel headers to match my OS level and I can't see an upgrade mechanism to get the kernel up to 5.7.7-200. Any ideas how to resolve this ? Mark Mark Roberts Senior Solution Architect Red Hat <https://www.redhat.com/> mroberts(a)redhat.com <marrober(a)redhat.com> M: 07887-850270 <https://www.redhat.com/>

2 1

Baobab Gnome Disk Analyzer: how to I remove paths?
by ToddAndMargo 09 Jul '20

09 Jul '20

Hi All, Baobab, Gnome Disk Analyzer I like the feature where you can add a path to analyze. Now how to I get rid of it when I am finished? Many thanks, -T

2 9

← Newer
1
...
5
6
7
8
9
10
11
12
Older →