search

getsolus / packages

Solus Package Monorepo & Issue Tracker
62 stars 78 forks source link

Impossible to safely eject FAT usb key #674

Open FTouzain opened 11 months ago

FTouzain commented 11 months ago

Summary

After using a 128 MB FAT16 usb key. I cannot eject it (nothing using it).

Here is the message I obtain in a pop up window (you can see the volume still mounted on the left of the picture). I do not face this problem on ubuntu 20.04 LTS or windows 10 with the same device. 2023-10-26_bug_solus_eject_FAT16_usb_key

The second picture shows Gparted and the characteristics of the usb key: 2023-10-26_gparted_characteristics_FAT16_usb_key

Steps to reproduce

1- plug and use FAT16 device

2- try to eject

Expected result

Normal ejection of the FAT16 usb key

Actual result

fail message, obligation of unsafe unplug

Environment

Repo

Shannon (stable)

Desktop Environment

Budgie

System details

budgie 10.8.1 Solus 4.4 Harmony Linux 6.5.7-259.current

Other comments

No response

ReillyBrogan commented 11 months ago

I'd like to see your system journal after such a failure. sudo journalctl -b0 > bad-eject.log and then upload it to Github Gists. If possible would you mind switching your system locale to English, then reboot and reproduce the failure? Unfortunately your system logs are localized as well and I'm not able to understand French. If I pass your logs through a translator they're going to change just enough that I won't be able to accurately google messages of interest.

FTouzain commented 10 months ago

Switching to English does not seem to change window display. The logs are already in English.

Note: when clicking the first time on "EJect", there is not pop up window with error message, but it does not eject (disappear and appear again). When clicking the second time, I have the pop up window with the error message: "Impossible to eject FAB_TOUZAIN. Error ejecting /dev/sde: Command line: 'eject '/dev/sde'' exited with non-zero exit status 1: eject: impossible to eject." (I translated the very last sentence because still in French)

Here is the output asked from the time I plugged and ejected the USB key FAB_TOUZAIN

oct. 31 12:20:01 fragile budgie-panel[1842]: budgie_abomination_app_group_get_windows: assertion 'self != NULL' failed
oct. 31 12:20:01 fragile separate_shot[5049]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:03 fragile separate_shot[5054]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:04 fragile kernel: usb 1-6.1: USB disconnect, device number 7
oct. 31 12:20:09 fragile separate_shot[5123]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:09 fragile separate_shot[5125]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:15 fragile separate_shot[5134]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:16 fragile kernel: usb 1-6.1: new high-speed USB device number 8 using xhci_hcd
oct. 31 12:20:16 fragile kernel: usb 1-6.1: New USB device found, idVendor=0781, idProduct=7100, bcdDevice= 1.04
oct. 31 12:20:16 fragile kernel: usb 1-6.1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
oct. 31 12:20:16 fragile kernel: usb 1-6.1: Product: Cruzer Mini 
oct. 31 12:20:16 fragile kernel: usb 1-6.1: Manufacturer: SanDisk Corporation 
oct. 31 12:20:16 fragile kernel: usb 1-6.1: SerialNumber: 000357895
oct. 31 12:20:16 fragile kernel: usb-storage 1-6.1:1.0: USB Mass Storage device detected
oct. 31 12:20:16 fragile kernel: scsi host38: usb-storage 1-6.1:1.0
oct. 31 12:20:16 fragile mtp-probe[5144]: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.1"
oct. 31 12:20:16 fragile mtp-probe[5144]: bus: 1, device: 8 was not an MTP device
oct. 31 12:20:16 fragile mtp-probe[5156]: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.1"
oct. 31 12:20:16 fragile mtp-probe[5156]: bus: 1, device: 8 was not an MTP device
oct. 31 12:20:17 fragile kernel: scsi 38:0:0:0: Direct-Access     Generic  STORAGE DEVICE   1.04 PQ: 0 ANSI: 0
oct. 31 12:20:17 fragile kernel: sd 38:0:0:0: [sde] 256000 512-byte logical blocks: (131 MB/125 MiB)
oct. 31 12:20:17 fragile kernel: sd 38:0:0:0: [sde] Write Protect is off
oct. 31 12:20:17 fragile kernel: sd 38:0:0:0: [sde] No Caching mode page found
oct. 31 12:20:17 fragile kernel: sd 38:0:0:0: [sde] Assuming drive cache: write through
oct. 31 12:20:17 fragile kernel: usb 1-6.1: reset high-speed USB device number 8 using xhci_hcd
oct. 31 12:20:18 fragile kernel: usb 1-6.1: reset high-speed USB device number 8 using xhci_hcd
oct. 31 12:20:18 fragile kernel: usb 1-6.1: reset high-speed USB device number 8 using xhci_hcd
oct. 31 12:20:19 fragile kernel: usb 1-6.1: reset high-speed USB device number 8 using xhci_hcd
oct. 31 12:20:19 fragile kernel: usb 1-6.1: reset high-speed USB device number 8 using xhci_hcd
oct. 31 12:20:19 fragile kernel:  sde: sde1
oct. 31 12:20:19 fragile kernel: sd 38:0:0:0: [sde] Attached SCSI removable disk
oct. 31 12:20:21 fragile separate_shot[5176]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:21 fragile separate_shot[5178]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:23 fragile separate_shot[5187]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:23 fragile kernel: FAT-fs (sde1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
oct. 31 12:20:23 fragile udisksd[1013]: Mounted /dev/sde1 at /run/media/touzain/FAB_TOUZAIN on behalf of uid 1000
oct. 31 12:20:27 fragile separate_shot[5213]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:29 fragile tracker-miner-f[2063]: tracker_indexing_tree_remove: assertion 'TRACKER_IS_INDEXING_TREE (tree)' failed
oct. 31 12:20:29 fragile systemd[1]: run-media-touzain-FAB_TOUZAIN.mount: Deactivated successfully.
oct. 31 12:20:29 fragile udisksd[1013]: Cleaning up mount point /run/media/touzain/FAB_TOUZAIN (device 8:65 is not mounted)
oct. 31 12:20:29 fragile udisksd[1013]: Unmounted /dev/sde1 on behalf of uid 1000
oct. 31 12:20:29 fragile budgie-panel[1842]: Failed to measure available space: Erreur d’obtention des informations du système de fichiers pour /run/media/touzain/FAB_TOUZAIN : Aucun fichier ou dossier de ce type
oct. 31 12:20:29 fragile kernel: usb 1-6.1: reset high-speed USB device number 8 using xhci_hcd
oct. 31 12:20:29 fragile kernel: usb 1-6.1: reset high-speed USB device number 8 using xhci_hcd
oct. 31 12:20:30 fragile kernel:  sde: sde1
oct. 31 12:20:33 fragile separate_shot[5250]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:33 fragile separate_shot[5248]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:39 fragile separate_shot[5259]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:41 fragile org.buddiesofbudgie.BudgieWm.desktop[1818]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800444
oct. 31 12:20:41 fragile separate_shot[5267]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:41 fragile kernel: usb 1-6.1: reset high-speed USB device number 8 using xhci_hcd
oct. 31 12:20:42 fragile kernel: usb 1-6.1: reset high-speed USB device number 8 using xhci_hcd
oct. 31 12:20:42 fragile kernel:  sde: sde1
oct. 31 12:20:42 fragile separate_shot[5280]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:45 fragile separate_shot[5295]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:45 fragile separate_shot[5297]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:47 fragile separate_shot[5306]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:47 fragile separate_shot[5312]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:49 fragile separate_shot[5317]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:51 fragile separate_shot[5323]: Theme parsing error: gtk-contained-dark.css:2871:228: Missing closing bracket for :not()
oct. 31 12:20:55 fragile sudo[5328]:  touzain : TTY=pts/0 ; PWD=/home/touzain/Téléchargements ; USER=root ; COMMAND=/usr/bin/journalctl -b0
oct. 31 12:20:55 fragile sudo[5328]: pam_unix(sudo:session): session opened for user root by (uid=1000)

Thank you. Maybe it is easier to handle txt file, I join it. bad-eject.log

ReillyBrogan commented 10 months ago

So reading through that issue it looks like udisks is unmounting the file system just fine. The only error is from tracker-miners, which may have been trying to index the filesystem at the time you ejected it. Tracker-miners received an update as part of the GNOME stack, are you sure this is still an issue?

FTouzain commented 10 months ago

Yes, because still reproducible. At the first try of ejection, the USB key disappear a brief moment and reappears. At the second try, I get the pop up window with the error I reported (restart and updates several times since I reported this bug). If this is tracker-miners, do I have a way to "repair it" or make it works fine, please? (why does this error systematically appear?).

ReillyBrogan commented 9 months ago

Can you check if this is still an issue after the upcoming sync? And also, do you happen to have mtools installed?

FTouzain commented 9 months ago

I have checked: it is still an issue. mtools is already installed.

ReillyBrogan commented 8 months ago

OK, could you test this again after the next sync? We've made a number of improvements since the last time you've tested, and this might be fixed now. I have a hunch that this might be another instance of the GIO crash that I fixed last month.

FTouzain commented 8 months ago

Sorry, still the problem with:

but I am not sure there are still many devices using FAT16