Bug 1975017
| Summary: | USB drives does not appear in the list of connected devices | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | nucleo <alekcejk> |
| Component: | plasma-workspace | Assignee: | KDE SIG <kde-sig> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 34 | CC: | geraldo.simiao.kutz, jgrulich, kde-sig, me, rdieter, than, vitaly |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | plasma-workspace-5.22.5-2.fc34 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-09-22 16:29:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
nucleo
2021-06-22 23:57:29 UTC
The same with plasma 5.22.2.1. What I did to test this: 1. I wrote KDE live image Fedora-KDE-Live-x86_64-Rawhide-20210628.n.0.iso from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Spins/x86_64/iso/ to USB drive with ext4 filesystem (from vfat it didn't start). 2. When KDE started I connected and removed second USB drive from removable devices widget on panel. 3. Once again, I connected second USB drive, This time it was not shown in removable devices widget on panel but it was shown in removable devices list in Dolphin where it can be connected and disconnected. So this is widget bug and can be reproduced from live image. Please report upstream if possible, thanks. What component to use for upstream report? plasmashell/disks and devices Looks like bug fixed https://bugs.kde.org/show_bug.cgi?id=438874#c38 https://invent.kde.org/plasma/plasma-workspace/commit/61e2ea2323ae63c5805c87353701ba6fb722205a FEDORA-2021-3ddd095bb0 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3ddd095bb0 FEDORA-2021-ee21db8aa2 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ee21db8aa2 FEDORA-2021-3ddd095bb0 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-3ddd095bb0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-3ddd095bb0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-ee21db8aa2 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ee21db8aa2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ee21db8aa2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. tested after the update: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ee21db8aa2 seems that its working fine now. FEDORA-2021-ee21db8aa2 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-3ddd095bb0 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |