Arch Linux User Repository

Porting to UDisks2 Use the gobject introspection approach for UDisks and Gtk

Added 'python-gobject' as dependency (I forgot it)

This version should be the final step before migrating to UDisks2. The 'traydevice' utility is replaced with 'traydvm', a simplified, re-written from scratch utility to show device icons in system tray, with a right-click menu. 'traydvm' is a python3 script which uses gobject-introspection for GIO, GLib and Gtk3. It has no configuration file and a predefined simple popup menu with only 'Mount', 'Unmount' and 'Eject' actions. Many improvements could be added to it in future releases. The two scripts 'udisksvm' and 'traydvm' are now written in the same more actual way, using more up to date tools.

As another step towards refreshing the script, I rewrote it in python 3. It still uses UDisks 1. I chose not to use python-dbus anymore but the UDisks DBus API with the GDBus part of the GIO module of GLib, via GObject-Introspection. It's a more up to date way to get Python code onto D-Bus (see http://dbus.freedesktop.org/doc/dbus-python/ the 'Problems and alternatives' part). To migrate to UDisks 2, the 'traydevice' utility has to be converted to this same way of using the D-Bus interface, and from pygtk to pygobject in python 3. Apart from that the changelog of this release is better shown with the 'udisksvm --help' output: usage: udisksvm [-h] [-v] [-n] [-d] [traydconf] A GUI UDisks wrapper positional arguments: traydconf configuration file for traydevice (default: /usr/share/udisksvm/udisksvm.xml) optional arguments: -h, --help show this help message and exit -v, --version show program's version number and exit -n, --noauto do not automount -d, --debug show internal infos The '-n, --noauto' option should permit to use the script to only start traydevice, ie to show a systray icon, without interfering with a file manager automounting feature enabled. There is still much left to accomplish to go ahead with this script and accompanying traydevice utility.

@jum1960: I will soon migrate the script to udisks2. Presently I have not udisks2 running on my computer, so I cannot say for sure if there is a conflict; but I read that the two versions could be installed and ran concurently, though that could be not safe in every cases. But that issue should be resolved when I finished migrating to udisks2.

Changelog for 1.9 release : Added some errors management Added redirection to /dev/null at traydevice command lines

Does udisks conflict udisks2? https://bbs.archlinux.org/viewtopic.php?id=142985

@Cpunitd: You can launch udisksvm in a console without the redirection to /dev/null to see the output and the errors on the screen. (take care to have only one udisksvm running). Do that without anything else automounting devices. Post the result here or in the forum thread.

Changelog for 1.8 release : Rewriting of the script in Python2. It now uses the dbus interface to UDisks, instead of the 'udisks' command (but the 'udisks' command is still used by traydevice). All the dependencies are provided with the traydevice package installation. For now it has the same functionalities as before. See the forum thread for more explanations.

Not sure how to troubleshoot this issue, but it's been a bother for close to a month now... it's officially to the point where I am unable to properly function with my computer anymore. At first, I would get icons when drives were connected, but they refused to mount (I would work around this by opening PCmanfm as root and clicking the drives so they mounted (doing so as non-root would give a permissions error). I was able to live with this... then, it got to the point where it traydevice doesn't always show a drive when it's connected. Then PCManfm now mounts (as root) drives that are accessible as root only. So I started mounting the partitions via the commandline. How do I figure out how to get this setup working the way it's supposed to (where I connect a device and it automounts on it's own)?