Bug 401058 - Transcend jf v30/8GB doesn't turn off itself during unmounting process
Summary: Transcend jf v30/8GB doesn't turn off itself during unmounting process
Status: RESOLVED UPSTREAM
Alias: None
Product: frameworks-solid
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.52.0
Platform: Neon Linux
: NOR major
Target Milestone: ---
Assignee: Lukáš Tinkl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-15 08:26 UTC by proteus5
Modified: 2018-11-18 05:02 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
lshw information about the USB device (69.58 KB, image/png)
2018-11-15 08:26 UTC, proteus5
Details

Note You need to log in before you can comment on or make changes to this bug.
Description proteus5 2018-11-15 08:26:10 UTC
Created attachment 116319 [details]
lshw information about the USB device

SUMMARY


STEPS TO REPRODUCE
1. insert the usb stick into an usb port of the computer;
2. open the folder of the USB device so to mount it in the KDe Neon or other Os provided by plasma environment;
3. unmount it;
4. the led stay on;
5. udisksctl power-off -b /dev/sdX
6. the command turns off the USB device.

OBSERVED RESULT

the device doesn't turn off when unmounted;
EXPECTED RESULT
the device turns off when unmounted;

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: last
(available in About System)
KDE Plasma Version:  last
KDE Frameworks Version: last
Qt Version: last

ADDITIONAL INFORMATION
Comment 1 proteus5 2018-11-16 14:27:04 UTC
I've tested other two USb devices: after having unmounted them the red led stay on. So, I've used udisksctl power-off -b /dev/sdX command to turn off them. My opinion is that the new energy option doesn't work or that is doesn't work on my hardware.
Comment 2 proteus5 2018-11-17 08:47:20 UTC
The solution to this annoying issue is to add the SAFELY REMOVE feature in the NOTIFICATION AREA as any Microsoft's OS does. There is no other solution to fix this problem, furthermore this feature is more productive and intelligible. It's necessary to divide the unmount function both from the eject function in the optical drives, and the turning off of the USB device.
Comment 3 Stefan Brüns 2018-11-18 04:30:45 UTC
This is caused by a hardware bug.

The SCSI INQUIRY command allows to determine if the medium in a drive is ejectable or not. This bit should be set for optical drives, tape drives, card readers, ..., but *not* for flash thumb drives.

Unfortunately, many thumb drives have this bit set, while USB-SATA bridges fortunately don't. You can see this e.g. in the kernel dmesg output - "sdX: Attached SCSI [removable] disk".

But we can not ignore this - if we do, we would also remove card readers. Afterwards, the card slots would be dysfunctional until the computer is rebooted.