Automounting encrypted flash drives in Gnome+xmonad

[sktsee]

On Sat, 21 Mar 2015 12:18:51 -0700, Caleb wrote:

> On Sat, Mar 21, 2015 at 11:55 AM, Caleb <enlightened.despot at gmail.com>
> wrote:
> 
>> On Sat, Mar 21, 2015 at 11:04 AM, sktsee <sktseer at gmail.com> wrote:
>>
>>> On Sat, 21 Mar 2015 10:39:24 -0700, Caleb wrote:
>>>
>>> > HI sktsee,
>>> >
>>> > Thanks for the reply! I tried "nautilus -n" and got the following
>>> > results:
>>> >
>>> > caleb at storm:~$ nautilus -n
>>> >
>>> > ** (nautilus:6264): WARNING **: Couldn't connect to accessibility
>>> > bus: Failed to connect to socket /tmp/dbus-qgjeqdNTwQ: Connection
>>> > refused caleb at storm:~$ ps auxw | grep nautilus caleb     5047  0.0 
>>> > 1.0 1656904 82036 ?       Sl   09:59   0:01 nautilus -n caleb    
>>> > 6270  0.0  0.0 11744   920 pts/6    S+   10:35   0:00 grep nautilus
>>> > caleb at storm:~$
>>> >
>>> > I'm assuming the warning about the accessibility bus can be safely
>>> > ignored.
>>> > The USB drive is still not automounted, however. Any other ideas?
>>> >
>>> >
>>> Yeah, usually WARNING messages are ok to ignore.
>>>
>>> I'm thinking that some GNOME services aren't running that provides the
>>> dbus intercommunications to talk to udisks to automount/unmount
>>> automatically. Should be able to confirm this by logging into a GNOME
>>> +Metacity session and then in a terminal type "xmonad --replace". If
>>> automounting your USB drive still works after that, then it'll be a
>>> matter of starting the right services when you login to a xmonad
>>> session.
>>>
>>> --
>>> sktsee
>>>
>>>
>> Yep, using xmonad --replace in a GNOME+Metacity session automounts the
>> drive just fine. Any ideas on how to track down the service that I
>> should be starting? I'm looking at the X session definitions in
>> /usr/share/xsessions, and so far the only difference seems to be the
>> argument to gnome-session.
>>
>>
> Success! I edited /usr/share/gnome-session/sessions/xmonad.session to
> look exactly like
> /usr/share/gnome-session/sessions/gnome-flashback.session except for the
> title and using xmonad instead of metacity, and the drive now
> automounts. I thought it wasn't working at first because it didn't
> happen right away, but after waiting for a second, the magic occurred.
> I'll probably try to pair down the list of required components, but it
> looks like it's either the gnome-flashback-services, nautilus-classic,
> or the unity-settings-daemon that's providing the magic.

Excellent. Nautilus should the program that talks to udisks in the 
background, but it I think it requires gnome-setting-daemon and xmonad to 
be launched by gnome-session to get the dbus stuff working correctly. One 
thing you may want to look at is Arch Linux's xmonad wiki page (https://
wiki.archlinux.org/index.php/Xmonad#GNOME_3_and_xmonad) where they have 
some configs that look like it may do a better job of getting xmonad to 
work nicely with GNOME3 components than what Ubuntu provides. Also, you 
may want to edit /etc/xdg/autostart/nautilus-autostart.desktop and 
comment out the line, "OnlyShowIn=GNOME;Unity;". This will allow Nautilus 
to start in the background when you choose to login to a session other 
than GNOME or Unity. 

-- 
sktsee