| Summary: | Partition manager does not show mmcblk0 device | ||
|---|---|---|---|
| Product: | [Applications] partitionmanager | Reporter: | David <kitt997> |
| Component: | general | Assignee: | Andrius Štikonas <andrius> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 23.08.4 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
David
2024-01-07 11:31:12 UTC
It uses lsblk to scan for devices (https://invent.kde.org/system/kpmcore/-/blob/master/src/plugins/sfdisk/sfdiskbackend.cpp?ref_type=heads#L74) Can you paste output of lsblk? (In reply to Andrius Štikonas from comment #1) > It uses lsblk to scan for devices > (https://invent.kde.org/system/kpmcore/-/blob/master/src/plugins/sfdisk/ > sfdiskbackend.cpp?ref_type=heads#L74) > > Can you paste output of lsblk? I figured it out randomly, it appears that my SD's read'only switch is faulty and triggers itself when not needed. And, this is the point, when the SD is read-only KDE Partition manager does not even show it. I don't know if this is by design or what, but I think this could turn out to be useful for others. |