this post was submitted on 03 Sep 2024
23 points (96.0% liked)

Linux

5174 readers
481 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 1 year ago
MODERATORS
 

H1_SD is the name of a MicroSD card I'm connecting, it does connect a second later, but it's annoying to keep dismissing this error every time. I am also getting it with regular SD cards and USB Drives regardless on which USB Port I've connected it to, and which format it's been partitioned too. NTFS, exfat, fat all respond similarly.

EDIT Welp, I was able to brute force a "fix". There appeared to be an issue with the Nemo configuration between 21 and 22. Not sure what the issue was specifically, but deleting the users ~/.config/nemo and a reboot fixed it for me.

top 4 comments
sorted by: hot top controversial new old
[–] aniki@discuss.tchncs.de 5 points 2 months ago* (last edited 2 months ago) (1 children)

GNOME? Is auto mount causing Nautilus to bug out? What's lsof say?

Something is causing a lock.

[–] the16bitgamer@programming.dev 1 points 2 months ago (1 children)

That was my guess too, and if Nautilus has the auto mount disabled the error goes away. But I'd like for USB drives to be auto mounted. And lsof just gives a wall of indecipherable text. What would I be looking for?

[–] aniki@discuss.tchncs.de 3 points 2 months ago

grep the mount point and track down the pid that using that file. should be pretty easy to see which application is doing it.

[–] mvirts@lemmy.world 1 points 2 months ago

Maybe watch dmesg when you plug in the drive?

Or look at the logs later. Journalctl -k -f should also show more logs than dmesg when you plug it it which may be informative.