Description of problem: The USB-Ports doesn't recognize any connected device after booting. When it is already connected while booting, then it works without any problems. Version-Release number of selected component (if applicable): How reproducible: Easy Steps to Reproduce: 1. Boot 2. Connect any USB device to the computer/laptop. Actual results: Disk or device doesn't appear. Expected results: Disk or device does appear. Additional info: My Environment: Lenovo Thinkpad X395 (20NL000HMZ) BIOS: Rev. 1.24 OS: Fedora 35 DE: Gnome WM: Mutter Kernel: 5.15.7-200.fc35.x86_64 USB Controller: Realtek Semiconductor Co., Ltd. RTL811x EHCI host controller (rev 0e) (took from lspic | grep USB)
Sounds more like a kernel issue. Is this a new issue? Can you test different kernel versions to see whether that might help?
This sounds like you may have usbguard active and are missing a gui plugin to show notifications to ask for permission to allow new devices to connect. I believe Fedora workstation uses usbguard by default now, but I've been unable to find any docs on this.
Hmm, good point. If usbguard is installed (and it is not by default), then GNOME will only permit USB devices that are plugged in while a user is logged in and the screen is unlocked. Which could explain the observation that the reporter is seeing. That said, we do *not* install it by default! @gc95 do you have usbguard installed?
Hello Together @j.w.r.degoede.nl I looked at my packages, there was no usbguard package installed. @bberg I tried different kernels, always the same situation. But I encountered something interesting: The USB ports seems like they are inactive when the laptop doesn't been plugged in via power adapter. I monitored dmesg (dmesg -w) and saw that it recognized immediately the USB devices connected to it. Sounds like a power save option, right?
> j.w.r.degoede.nl Wow, that is a very old email address of mine, I had totally forgotten that I was already using bugzilla at that time (1996 ish) I'm surprised bugzilla still somehow has that, but it won't work anymore. > I looked at my packages, there was no usbguard package installed. Ok, then that is not the cause of this.
> Wow, that is a very old email address of mine, I had totally forgotten that I was already using bugzilla at that time (1996 ish) I'm surprised bugzilla still somehow has that, but it won't work anymore. That's really nice, I'm glad I dug up an old email corpse – sorry for the disturbing xD. > I looked at my packages, there was no usbguard package installed. Yeah, I think it depends on some energy- or power saving setting. Sadly, didn't have time for troubleshooting more. Would give feedback when I know more.
In today's Prioritized Bugs meeting, we agreed to reject this as a Prioritized Bug. It does not appear to be widespread and the maintainers are actively involved. https://meetbot.fedoraproject.org/fedora-meeting-1/2022-01-12/fedora_prioritized_bugs_and_issues.2022-01-12-16.00.log.html#l-160
> But I encountered something interesting: > The USB ports seems like they are inactive when the laptop doesn't been plugged in via power adapter. That is normal for the "charge" port on thinkpads (the one with a battery symbol next to it). The firmware will keep the USB port powered (but otherwise inactive) so that you can use it as a charger. You can even change the BIOS setting to keep the port powered while suspended (and not plugged into the AC). But, it *might* be an interesting data point, if that particular USB device is getting confused by being powered without having a proper USB hub on the other side and doesn't reset properly then.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.