||General / Others
||wmudmount is a filesystem mounter that uses udisks to handle notification of new filesystems and mounting of the filesystems as a non-root user. It also includes a mode to display the mounted filesystems with the least free space percentage (similar to wmfsm).
Reply to a blog post
The author of wmvolman seems to take issue with the design of my dockapp on his blog <http://thousandsofhate.blogspot.com/2010/03/facepalmjpg.html>. Since it won't let me post a comment there, I'll just reply here.
He is apparently reasoning from faulty premises. He complains that the dockapp uses libgnome-keyring, libnotify, and gtk+ and states "Why would someone use WindowMaker inside GNOME (and it WILL be 'inside GNOME' just after libnotify and libgnome-keyring starts all GNOME services like gconf and gvfs) with dockapps enabled?".
Libgnome-keyring is there so I don't have to mess around with mlock when handling the LUKS passwords; the non-gnome-keyring-memory portions (i.e. the associated daemon) are completely optional. I also note that they're working on a generic dbus service so libgnome-keyring can be used to access the KDE wallet or other similar services. But hey, I can easily enough make even the library optional at the expense of requiring the --allow-insecure-memory command line option.
Libnotify is there because I wanted notifications. But the Gnome notification daemon is far from the only one providing the org.freedesktop.Notifications DBus service; I see at least 4 others just in a quick "apt-cache search notification-daemon". But hey, I can easily make that library optional too.
I don't know where he got gvfs from, I just uninstalled it on my machine and wmudmount continued to work fine; neither the gnome-keyring daemon nor the Gnome notification-daemon seem to require gvfs either. And while removing gconf does take out the gnome-keyring daemon and the Gnome notification-daemon, as I noted above neither of those is at all necessary for wmudmount.
Since I already had glib in there for dbus-glib and I needed something to do the various dialogs and popup menus, and gtk supports the freedesktop.org themed icons that udisks returns and has a text entry widget that can easily be made to use the memory allocated by gnome-keyring-memory, I decided to just go with that instead of messing with xlib or pulling in some other toolkit.
BTW, there aren't even any widgets in the dockapp window, everything is drawn on the window just as in a traditional xlib dockapp; there are widgets in the other dialogs, of course. Signals and callbacks are unavoidable unless I would decide to go completely low-level and omit dbus-glib entirely. And there aren't any blackjacks or hookers at all. And I note that the libdockapp he uses in wmvolman has callbacks too...
I'm not sure what the file size comparison is supposed to prove, since wmvolman seems to do almost nothing of course it will be smaller.
All in all, I find nothing there to support the claim that "it WILL be 'inside GNOME'".
wmaker inside gnome
fwiw, I think running windowmaker as the window manager for gnome provides the best linux desktop experience. The only reason more people don't do it is because its non-trivial to swap the windowmanager in gnome (it requires editing one gconf key).
no udisks for karmic
I can't find a udisks install package for ubuntu karmic, and running wmudmount gives an error:
"DeviceKit-Disks version 007 is not supported"
not sure if its too old or too new. :(
Re: no udisks for karmic
It's too old. DeviceKit-Disks 009 is supported, if you can find a way to upgrade to that. Or you could try editing the version detection code in udisks.c at about line 943 to pretend 007 is 009 and see if anything blows up.
FYI, after 009 they renamed devicekit-disks to udisks and started using "1.0.0" style versions.
I tried wmudmount with Fluxbox-1.1.1 and today's git version.
The wmudmount app doesn't dock to the Fluxbox slit and remains on the top left corner of the desktop.
Reply to a reply to a blog post
Hey, man. I meant no offence and I really like your wmweather+ and wmsystemtray applets. But using all this GNOME crap in wmaker... I don't know, I think it's a bit "bloated".
I have the same problem as tassukahlain: wmudmount ignores the dock settings, and instead remains in the top left corner of the desktop. Shame.
Re: Fluxbox and Openbox
The problem with both is that they only consider an app to be a dockapp if the window has its initial state set to WithdrawnState. Unfortunately, gtk has no way to set the initial state to WithdrawnState, and even if you dig in to the underlying X windows it resets the initial state hint before mapping the window.
So it's not that wmudmount is somehow "ignoring" the dock settings, its that the window manager isn't recognizing wmudmount as a dockapp in the first place and so isn't swallowing the icon window in the first place.
Re: Fluxbox and Openbox
See also https://bugzilla.gnome.org/show_bug.cgi?id=139322
I.e. no solution? :(
i.e. I need to put in a hack, fortunately I was able to come up with one.
Fluxbox works now
Thanks anomie for the great app.
1.6 works now with fluxbox.
this app is extremely useful.