Summary: | Plasma Crashed when unmounting usb with 2 partitions | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | news.group |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | plasma-bugs, qydwhotmail |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.23.5 | ||
Target Milestone: | 1.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
news.group
2022-01-20 22:56:39 UTC
The usb drive that causes Plasma to crash was formatted by Ventoy, specifically using GPT partition style. In this format both partitions are mounted and Plasma crashes when both partitions are unmounted. I have reformatted the drive using Ventoy, but this time with a MBR partition style. In this format only one partition is mounted and no issues when it is unmounted. I have added fdisk output for both the GPT & MBR partition styles, in case this is helpful. Disk /dev/sdd: 112.64 GiB, 120945901568 bytes, 236222464 sectors Disk model: Transcend 128GB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 479AE6A6-4773-B477-23F1-A882B0936453 Device Start End Sectors Size Type /dev/sdd1 2048 236154879 236152832 112.6G Microsoft basic data /dev/sdd2 236156888 236222423 65536 32M Microsoft basic data Disk /dev/sdd: 112.64 GiB, 120945901568 bytes, 236222464 sectors Disk model: Transcend 128GB Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x79089258 Device Boot Start End Sectors Size Id Type /dev/sdd1 * 2048 236156927 236154880 112.6G 7 HPFS/NTFS/exFAT /dev/sdd2 236156928 236222463 65536 32M ef EFI (FAT-12/16/32) It's fixed in 5.24. Please test again after updating Plasma and reopen if the bug still persists. *** This bug has been marked as a duplicate of bug 427945 *** |