https://bugs.kde.org/show_bug.cgi?id=486594

            Bug ID: 486594
           Summary: "Disks & Devices" reports AOSP device in initial
                    charge reporting state has accessible storage, but it
                    doesn't.
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: unassigned-b...@kde.org
          Reporter: 4wy78...@rokejulianlockhart.addy.io
  Target Milestone: ---
             Flags: performance-

Created attachment 169197
  --> https://bugs.kde.org/attachment.cgi?id=169197&action=edit
Depiction of the problem.

SUMMARY
The "Disks & Devices" plasmoid reports that an AOSP device in its initial
charge-reporting state has accessible storage, but it doesn't.

STEPS TO REPRODUCE
1.  Shutdown the device (using `adb shell reboot -p` per
https://android.stackexchange.com/revisions/47994/2#:~:text=Try-,adb%20shell%20reboot%20-p,-to%20shutdown%20the).
2.  Boot into the state whereby it solely displays its charge (as
https://android.stackexchange.com/revisions/257032/1#:~:text=Most%20importantly%2C%20I'd,device%20commences%20charging
describes).
3.  Attempt to access the device's storage via the plasmoid.

OBSERVED RESULT
An error dialogue window appears.

EXPECTED RESULT
The plasmoid shouldn't present the device has possessing accessible storage.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7600X 6-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: AMD Radeon RX 5700
Manufacturer: ASRock
Product Name: X670E Taichi

ADDITIONAL INFORMATION
https://discuss.kde.org/t/where-to-report-bug-for-disks-devices-plasmoid/15057/1?u=rokejulianlockhart#:~:text=i%20ask%20because%20i%20want%20to%20report%20aosp%20devices%20being%20identified%20as%20accessible%20after%20booting%20from%20an%20unpowered%20state%20(when%20their%20bootloader%20displays%20charging%20information%2C%20but%20the%20os%20is%20not%20initialized).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to