New question #708174 on Ubuntu-Certification:
https://answers.launchpad.net/ubuntu-certification/+question/708174

Tested with :

Ubuntu Version: 1:44.0-1ubuntu2
Nautilus Version: 1:44.0-1ubuntu2

Desktop environment: Gnome
Associated hardware: RTS525A PCI Express Card Reader

Reproducable: always
Steps to reproduce:

1.  Insert SD-micro card in SD-card slot.
2. Open Nautilus
3. Right-Click on mounted SD-Card Volume(s). Only option to unmount SD-Card 
displayed on menu is Eject, no Unmount option
4. When clicking on Eject in contextual menu opened by Right-Click or clicking 
on the Eject icon right to the SD-Card Volume name, user gets no feedback, 
until executing step 4 a second time whereupon an Error Dialogue appears: 
--------------------------
Unable to Eject <SD Card Volume name>
Volume
No object for D-Bus Interface
--------------------------

Expected behaviour on clicking Eject either in contextual menu or icon to the 
right of Volume Name in Nautilus:
1.  System checks if any changes have not been written to SD-Card Volume, if so 
asks user to wait until processing has been complete
2.  If no changes are to in the qeue to be written, umount the SD-Card volume, 
update Nautilus interface by removing Eject icon and give message to User that 
SD-card can be removed safely.
- Nautilus should show Unmount option instead of Eject or better still process 
Eject command as a simple umount without trying to shut off power to parent 
device (The Card Reader).

Real behaviour:
1. No feedback when Eject is requested  first time,  upon second time Error 
message is displayed as mentioned under step 4 under Steps to Reproduce (see 
above)

Thoughts:
-It looks like Nautilus and the underlying D-Bus rules are treating the SD-Card 
reader just like they would do with a USB-stick type SD-Card reader, even 
though the SD-Card reader is connected to the PCIe-bus and is non-removable.
A custom udev rule for  non-removable SD-Card readers that would treat the 
Eject option in the Nautilus interface as a simple umount would be the optimal 
solution imho., but I don't know if this is possible and if so, how to achieve 
this.
A udev rule would not be specific to Nautilus, so this fix should work with any 
file-manager using udev, regardless of the desktop environment.

The systemd Journal associated with the Eject attempt looks something like this:

-
(...)
okt 08 20:32:49 laptopname audit[1639]: USER_AVC pid=1639 uid=103 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_signal"  bus="system">
                                        exe="/usr/bin/dbus-daemon" sauid=103 
hostname=? addr=? terminal=?'
okt 08 20:32:49 laptopname kernel: audit: type=1107 audit(1696789969.796:150): 
pid=1639 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operati>
                                   exe="/usr/bin/dbus-daemon" sauid=103 
hostname=? addr=? terminal=?'
okt 08 20:32:49 laptopname kernel: audit: type=1107 audit(1696789969.808:151): 
pid=1639 uid=103 auid=4294967295 ses=4294967295 subj=unconfined 
msg='apparmor="DENIED" operati>
                                   exe="/usr/bin/dbus-daemon" sauid=103 
hostname=? addr=? terminal=?'
okt 08 20:32:49 laptopname audit[1639]: USER_AVC pid=1639 uid=103 
auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" 
operation="dbus_signal"  bus="system">
                                        exe="/usr/bin/dbus-daemon" sauid=103 
hostname=? addr=? terminal=?'
okt 08 20:32:49 laptopname systemd[1]: media-username-9C33\x2d6BBD.mount: 
Deactivated successfully.
okt 08 20:32:49 laptopname udisksd[1689]: Cleaning up mount point 
/media/username/9C33-6BBD (device 179:1 is not mounted)
okt 08 20:32:49 laptopname udisksd[1689]: Unmounted /dev/mmcblk0p1 on behalf of 
uid 1000
okt 08 20:32:50 laptopname kernel: mmc0: cannot verify signal voltage switch
(...)
-

The Eject action, although without feedback to the user, successfully unmounts 
the volume, but does not give feedback about this in the interface of Nautilus 
or as System message as is the case with a USB-stick type SD-Card reader.

-- 
You received this question notification because your team Canonical
Hardware Certification is an answer contact for Ubuntu-Certification.

-- 
Mailing list: https://launchpad.net/~canonical-hw-cert
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~canonical-hw-cert
More help   : https://help.launchpad.net/ListHelp

Reply via email to