[kde] [Bug 509867] New: partitionmanager hangs while scanning disks after password request
Xwang
bugzilla_noreply at kde.org
Wed Sep 24 13:59:40 BST 2025
https://bugs.kde.org/show_bug.cgi?id=509867
Bug ID: 509867
Summary: partitionmanager hangs while scanning disks after
password request
Classification: I don't know
Product: kde
Version First unspecified
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: xwaang1976 at mailo.com
Target Milestone: ---
SUMMARY
partitionmanager hangs while scanning disks after password request
STEPS TO REPRODUCE
1. Start partitionmanager
2. Insert the password
OBSERVED RESULT
partitionmnager remains in "scanning device" at 0% forever, this is what is
written in the console if I start from it. I have to kill the process to close
it:
LC_ALL=C partitionmanager
Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not
UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
Loaded backend plugin: "pmsfdiskbackendplugin"
"Using backend plugin: pmsfdiskbackendplugin (1)"
"Scanning devices..."
"Device found: KBG50ZNS512G NVMe KIOXIA 512GB"
getting temp failed for "/dev/nvme0n1" : No such file or directory
getting powered on time failed for "/dev/nvme0n1" : No such file or directory
getting power cycles failed for "/dev/nvme0n1" : No such file or directory
EXPECTED RESULT
scan should be completed quickly and the program can be used
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.8-arch3-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × 12th Gen Intel® Core™ i5-1240U
Memory: 16 GiB of RAM (15.2 GiB usable)
Graphics Processor: Mesa Intel® Iris® Xe Graphics
Manufacturer: Dell Inc.
Product Name: Latitude 9330
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list