-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Michael Biebl <[email protected]> wrote in [email protected]: > I don't see any source related changes which would make spacefm actually > add support for udisks2. > > spacefm still uses the /org/freedesktop/UDisks D-Bus interface (i.e. > udisks1), so I'm going to reopen this bug report as I don't think this > bug is properly fixed.
Hi, I'm the author of SpaceFM. Just to clarify this for you, SpaceFM has never used the dbus interface to any version of udisks (and it has no dependency on or use of dbus at all). You may think that because you searched the source for "/org/freedesktop/UDisks", but that part of the source is not compiled or is used for parsing device properties and was never used to communicate with dbus. Any dbus info you see in a terminal is coming from GTK components sometimes opening dbus interfaces by default. SpaceFM always performs mounting using command-line interface tools only, using whatever mount tool the user chooses. If none is chosen it will look for and use (in this order of preference) udevil, pmount, udisks2, or udisks1. So udisks1 is still supported, but udisks2 is used in preference to it if installed. I recommend udevil, but the package-recommends are up to the packager. There are many users using SpaceFM with udisks2 on Debian for over a year, no problem reports. Relevant function code for 0.9.4 is at https://github.com/IgnorantGuru/spacefm/blob/25a2a94bccc5d44770a2a1e227e9127fa761d6d2/src/vfs/vfs-volume-nohal.c#L3232 User's Manual: http://ignorantguru.github.io/spacefm/spacefm-manual-en.html#devices-settings-mcmd IgnorantGuru <[email protected]> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iF4EAREIAAYFAlT1z98ACgkQJ6WsWgGTdiH4tQEAsWeIoukJUQIVhlie1cmnlgUJ sPKNaKxsAnJN8TaKJy8BAKRgjFYLNB4oejmEyEGE0Vb4vldd0KO2bYKyLXqLBSQV =BRpr -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
