Unable to eject SDcard -getting remounted immediately

[Bartłomiej Żogała]

THe problem is on Dell XPS13 9310 and built-in microSD card reader(without adapter). When I plug the card it's visiible in file manager, with little 'eject' icon. I can read/write to it. After finishing and using eject button. THe card it's still present in gnome along with 'eject' button. But when clicking eject it says 'No object for D-bus interface' and both the device and partition blockdevices are still present.
I can't also eject from command line:
nusch@xps13:~$ LANG="en" eject -v /dev/mmcblk0
eject: device name is `/dev/mmcblk0'
eject: /dev/mmcblk0: not mounted
eject: /dev/mmcblk0: is whole-disk device
eject: /dev/mmcblk0: trying to eject using CD-ROM eject command
eject: CD-ROM eject command failed
eject: /dev/mmcblk0: trying to eject using SCSI commands
eject: not an sg device, or old sg driver
eject: SCSI eject failed
eject: /dev/mmcblk0: trying to eject using floppy eject command
eject: floppy eject command failed
eject: /dev/mmcblk0: trying to eject using tape offline command
eject: tape offline command failed
eject: unable to eject

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83
Uname: Linux 5.10.0-1057-oem x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu71.2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 28 13:31:39 2022
DisplayManager: gdm3
InstallationDate: Installed on 2015-05-08 (2608 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to impish on 2022-02-21 (126 days ago)

[Daniel van Vugt (vanvugt)]

Thanks for the bug report.

Please try disabling Ubuntu Dock in the Extensions app, and tell us if that prevents the bug.

Also, since Ubuntu 21.10 reaches end-of-life in 15 days would you be able to try Ubuntu 22.04?
https://wiki.ubuntu.com/Releases

[Daniel van Vugt (vanvugt)]

Maybe also try:

gsettings set org.gnome.desktop.media-handling automount false
gsettings set org.gnome.desktop.media-handling automount-open false

If that fixes the issue then it doesn't mean automount is to blame though, as it might be a quirk of the card reader (or kernel) whereby the device reports insertion after ejection.

[Bartłomiej Żogała (nusch)]

Upgraded to 22.04, still an issue, also neither of above gsettings makes a change . Regatrding disabling dock, can you give more details ? I've tried to
settings-> Appearance -> Dock -> COnfigure Dock Behaviour and unticked Show Volumes and Devices- doesn't make any change also

[Bartłomiej Żogała (nusch)]

Managed to disable dock via Extensions - doesn't change anything also

[Bartłomiej Żogała (nusch)]

Is ther any reason that impish was removed if the bug is valid both for jammy and impish ? Also do you need any more debug info to properly triage this and change "New" status to something meaninfgul after 6 months ?

[Bartłomiej Żogała (nusch)]

I've just tried to eject/enter the card when running *udisksctl monitor* . The output attached. What seems strange to me is that one of the symlinks (to/from ? ) device is stated as /dev/android1 . Not sure what specific logic causes this and if there was any previous naming convention agreed but on my device /dev/android1 links to /dev/video - the built-in camera . Could that be the root issue - that camera and memory card developers had the same idea of using android1 symlink ? I'm not sure where to furthe debug this - how kernel, udev and udisks play alltogether

[Daniel van Vugt (vanvugt)]

'impish' is no longer supported so its tag gets removed and replaced with a more current tag 'jammy' so that the bug does not get automatically closed for being too old when we do housekeeping later.

[Bartłomiej Żogała (nusch)]

Ok thank you, can you guide how to debug this further on jammy?

pon., 30 sty 2023, 07:25 użytkownik Daniel van Vugt <
<email address hidden>> napisał:

> 'impish' is no longer supported so its tag gets removed and replaced
> with a more current tag 'jammy' so that the bug does not get
> automatically closed for being too old when we do housekeeping later.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1980080
>
> Title:
> Unable to eject SDcard -getting remounted immediately
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1980080/+subscriptions
>
>

[Bartłomiej Żogała (nusch)]

Also wondering - my lspci output shows line:
72:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01)

I'm wondering about the 'unassigned class' - might it be related to this issue. As most other devices besides NVMe disk starts from 00:, where NVMe starts from 01: Might this 72: mean that SD card reader has priority over NVMe disk ?

[Bartłomiej Żogała (nusch)]

I've spotted that if wheter I eject from GUI or manualy by:
`eject /dev/mmcblk0` the group of /dev/mmcblk0 changes from **disk** to **plugdev** . Is this desired ?
Found this old Gentoo Forums post which might be related https://forums.gentoo.org/viewtopic-p-4212031.html but IMHO it's importand not only to make some quick udev workaround but understand what actually happens to not break things in other place