This sounds a lot like bug 404185, except that we don't do the "safely remove device" any more with the eject button (which is what would cause this effect). Can you please open system -> admin -> disk utility and play with the unmount/eject/safe eject buttons and check which of those remove the entire reader? (expected: eject doesn't, safe removal does)
Also, please do
- fresh boot, no card inside
- open Terminal, do "devkit-disks --monitor-details > /tmp/dkd.log"
- insert card, let it automount
- eject in nautilus
- Press Control-C in that terminal.
- Attach /tmp/dkd.log here.
This sounds a lot like bug 404185, except that we don't do the "safely remove device" any more with the eject button (which is what would cause this effect). Can you please open system -> admin -> disk utility and play with the unmount/eject/safe eject buttons and check which of those remove the entire reader? (expected: eject doesn't, safe removal does)
Also, please do
- fresh boot, no card inside
- open Terminal, do "devkit-disks --monitor-details > /tmp/dkd.log"
- insert card, let it automount
- eject in nautilus
- Press Control-C in that terminal.
- Attach /tmp/dkd.log here.
Thanks!