On Tuesday 10 September 2019 18.03:27 Michele Calgaro via trinity-users wrote: > As an additional thought, it is possible that perhaps TDEHW is notified by > udev of the existence of the new device before UDisks2 has created the > related object path. Therefore an immediate attempt to automount the device > would result in the error displayed in the original screenshot (object path > /org/freedesktop/UDisks2/block_devices/sdg1 not existing). Sound plausible to me, as these disks do mount at a later stage > This would also be consistent with the fact that a later attempt to mount > the device (even from Konqueror) works fine. I assume you have chosen to > automount the device when inserted in the tde control center, right? Humm... not really. I have "chosen" nothing (at least knowing I did). I may have said yes to mounting them the first time I got a popup window asking for it (which would explain why I get that window as root but not as user). In storage media I have "Enable medium application autostart after mount" checked. "Mount automaticaly", "Read only" and "Quiet" are unchecked, "UTF-8" and "Mount as user" are checked, "Synchronous", "Access time updates" and "Flushed IO" show a minus, which I imagine means undefined. > Cheers > Michele Thierry --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
