Bug#544148: gvfs* automatic processes: this time with real breakage

[Baptiste Carvello]

Le 28/02/2011 14:49, Josselin Mouette a écrit :
> Good. Since nautilus allows to specify a different action for each media
> type.
>
>    
did you test that? I was proposed several actions, but *all of them* 
mounted the drive first, including the "do nothing" action. My current 
nautilus configuration is :

~$ gconftool-2 -a /apps/nautilus/preferences|grep media
  media_autorun_x_content_start_app = 
[x-content/audio-cdda,x-content/video-dvd,x-content/audio-dvd,x-content/video-bluray,x-content/blank-dvd,x-content/video-vcd,x-content/blank-cd,x-content/video-svcd]
  media_automount_open = false
  media_autorun_x_content_ignore = 
[x-content/audio-player,x-content/software,x-content/image-picturecd,x-content/blank-bd,x-content/blank-hddvd,x-content/unix-software,x-content/win32-software,x-content/image-dcf]
  media_autorun_never = false
  media_automount = true
  media_autorun_x_content_open_folder = []
  media_autorun_x_content_ask = []

Setting media_autorun_never to true does not help.
Setting media_automount to false prevents nautilus from mounting *any* 
volumes.

> In all cases this is a different bug from #544148. So don’t hijack bugs
> and open new ones for different issues.
>
>    
The inflexibility of the gvfs implementation prevents me from easily solving (or working around) my problem. So this *is* at least partly #544148. Also, the way I finally solved it might be of interest to the reporters of this bug. Feel free to also open a bug on nautilus if you wish. Also feel free to not answer if you think it "pollutes" or "hijacks".