users October 2020

users@lists.fedoraproject.org

106 participants
126 discussions

Re: What was that?
by Tom Killian 02 Oct '20

02 Oct '20

> However, neither the keyboard or mouse were functioning. > I unplugged the wireless dongles for both of them and > plugged them back in, and now the mouse works, but the > keyboard still doesn't work. I've been seeing stuff like this in the syslog from recent kernels: Sep 30 08:59:34 dorotea kernel: usb 1-3: new full-speed USB device number 3 using xhci_hcd Sep 30 08:59:34 dorotea kernel: usb 1-3: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.09 Sep 30 08:59:34 dorotea kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 30 08:59:34 dorotea kernel: usb 1-3: Product: USB Receiver Sep 30 08:59:34 dorotea kernel: usb 1-3: Manufacturer: Logitech Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C52B.0001/input/input18 Sep 30 08:59:34 dorotea kernel: hid-generic 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-3/input0 Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0002/input/input19 Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0002/input/input20 Sep 30 08:59:34 dorotea kernel: input: Logitech USB Receiver System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.1/0003:046D:C52B.0002/input/input21 Sep 30 08:59:34 dorotea kernel: hid-generic 0003:046D:C52B.0002: input,hiddev96,hidraw1: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-3/input1 Sep 30 08:59:34 dorotea kernel: hid-generic 0003:046D:C52B.0003: hiddev97,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2 Sep 30 08:59:34 dorotea kernel: usb 1-3: USB disconnect, device number 3 Sep 30 08:59:34 dorotea mtp-probe[1544]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3" Sep 30 08:59:39 dorotea kernel: usb 1-3: new full-speed USB device number 4 using xhci_hcd Sep 30 08:59:39 dorotea kernel: usb 1-3: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.09 Sep 30 08:59:39 dorotea kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 30 08:59:39 dorotea kernel: usb 1-3: Product: USB Receiver Sep 30 08:59:39 dorotea kernel: usb 1-3: Manufacturer: Logitech The device is recognized, then something called mtp-probe comes along and blows it out of the water. The cycle repeats until either mtp-probe gives up and lets the device work, or the device itself gives up: Sep 30 09:00:10 dorotea kernel: usb 1-3: Device not responding to setup address. A workaround (found on the interwebs) is to add a udev rule in, say, /etc/udev/rules.d/99-mtp-no-probe.rules: ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c52b", ENV{MTP_NO_PROBE}="1" Now there are messages like this: Oct 2 10:18:09 dorotea mtp-probe[973]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5" Oct 2 10:18:09 dorotea mtp-probe[973]: bus: 1, device: 3 was not an MTP device But so far nothing bad has happened.

1 0

Any Emacs Users?
by Lasse Kliemann 01 Oct '20

01 Oct '20

Greetings, recently, I tried to switch from Debian to Fedora for the nth time. Once again, I was stopped dead in my tracks since my Emacs initialization stopped working because of a missing 'use-package'. I could try and rewrite my initialization to not use 'use-package'. However, since already something so basic is missing, I expect the next roadblock to be just around the corner. Questions: a) Is 'use-package' available for Fedora from a trustworthy source? (I avoid Emacs' own package management, since the last time I checked, it was a security nightmare.) b) Is Emacs not so popular with Fedora users generally? Can such a statement be made? Any Fedora+Emacs enthusiasts who would like to share their setup? Thanks -- Kind Regards / MfG Dr. Lasse Kliemann Westring 269, 24116 Kiel, Germany E-Mail: lasse(a)lassekliemann.de Telegram / Wire: @lassekliemann Phone: +49 162 66 88 468

6 5

(root) FAILED (loading cron table)
by Paolo Galtieri 01 Oct '20

01 Oct '20

Folks, since August 13 my backups have failed to run due the following errors: Oct 1 11:10:01 terrapin CROND[110219]: (root) CMD (/usr/local/bro/bin/zeekctl cron) Oct 1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security context (/etc/crontab) Oct 1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table) Oct 1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security context (/etc/cron.d/0hourly) Oct 1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table) Oct 1 11:12:01 terrapin crond[1565]: ((null)) No SELinux security context (/etc/cron.d/sbackup) Oct 1 11:12:01 terrapin crond[1565]: (root) FAILED (loading cron table) ls -lZ /etc/cron.d/sbackup -rw-r--r--. 1 root root unconfined_u:object_r:system_cron_spool_t:s0 76 Oct 1 11:11 /etc/cron.d/sbackup ls -lZ /etc/cron.d/0hourly -rw-r--r--. 1 root root system_u:object_r:system_cron_spool_t:s0 128 Jul 24 2019 /etc/cron.d/0hourly ls -lZ /etc/crontab -rw-r--r--. 1 root root system_u:object_r:system_cron_spool_t:s0 451 Jul 24 2019 /etc/crontab ls -lZ /usr/sbin/sbackupd -rwxr-xr-x. 1 root root system_u:object_r:usr_t:s0 21024 Apr 29 08:53 /usr/sbin/sbackupd* I ran: sudo sesearch -A -s unconfined_t -t user_cron_spool_t -c file allow application_domain_type user_cron_spool_t:file { append getattr ioctl lock read write }; allow crontab_domain user_cron_spool_t:file { append create getattr ioctl link lock open read rename setattr unlink write }; allow domain file_type:file map; [ domain_can_mmap_files ]:True allow files_unconfined_type file_type:file execmod; [ selinuxuser_execmod ]:True allow files_unconfined_type file_type:file { append audit_access create execute execute_no_trans getattr ioctl link lock map mounton open quotaon read relabelfrom relabelto rename setattr swapon unlink write }; allow unconfined_t user_cron_spool_t:file entrypoint; [ cron_userdomain_transition ]:True allow unconfined_t user_cron_spool_t:file { getattr ioctl read write }; This made no difference, my backups still don't run. The last backup ran Aug 13. What do I need to change to get my backups to start running automatically again? Paolo

2 2

RPM for python-module-memory_profiler
by Alex 01 Oct '20

01 Oct '20

Hi, I'm looking for an RPM for python-module-memory_profiler for fedora32: https://pypi.org/project/memory-profiler/ Perhaps someone knows of a source RPM for another distro that might work? Or a repo that is maintaining it? Why wouldn't it be included with fedora by default? Thanks, Alex

2 2

htts://retrace.fedoraproject.org : URL does not exist.
by Ger van Dijck 01 Oct '20

01 Oct '20

Hi, Wich URL does replace this URL ? Kind regards, Ger van Dijck.

2 1

What was that?
by Tom Horsley 01 Oct '20

01 Oct '20

Just did a dnf update which (among other things) got the new kernel 5.8.12-200.fc32.x86_64. Rebooted after installing everything (and letting akmods finish building and installing). Got a totally black screen with a mouse cursor in the middle that wouldn't move. After staring at it for a bit, I started trying to login via ssh from my phone, but about half way through typing my password, the black screen suddenly showed the sddm login screen. However, neither the keyboard or mouse were functioning. I unplugged the wireless dongles for both of them and plugged them back in, and now the mouse works, but the keyboard still doesn't work. I used the mouse and the onscreen button to completely shutdown the system, gave it a few seconds to cool off, then hit the power button to boot again, and everything worked perfectly fine on the power up boot. What was that? Can a reboot leave USB in some weird state that the new kernel doesn't recognize and only a complete power cycle works? What was it doing during the five minutes or so it was showing a blank screen on the first boot (was graphics also in a weird state from the old to new kernel transition?) Hopefully it will remain happy now.

1 0