Two processes attempt to mount blank optical discs

[mc4man]

Here the error popup appears to come from gvfs, one element would be gvfsd-burn though something calls it I suppose, see screen
This would be the alt. message when /usr/lib/gvfs/gvfsd-burn is made unavailable
(sudo mv /usr/lib/gvfs/gvfsd-burn /usr/lib/gvfs/gvfsd-burn.bak

[kansasnoob]

Here the error popup appears to come from gvfs, one element would be gvfsd-burn though something calls it I suppose, see screen
This would be the alt. message when /usr/lib/gvfs/gvfsd-burn is made unavailable
(sudo mv /usr/lib/gvfs/gvfsd-burn /usr/lib/gvfs/gvfsd-burn.bak

So I've been assuming that Nautilus (or Caja) is trying to mount the blank media after gvfs, but from the appearance of that maybe the file manager is mounting the media before gvfs?????

[kansasnoob]

Any idea where gvfs logs would be?

[VMC]

Any idea where gvfs logs would be?

No idea, but "burn.mount" is AutoMount=true, found under "/usr/share/gvfs/mounts/". What would happen if made false?

[VMC]

I don't have my dvd handy ( i use usb), but when the message appears, is it show up here "/run/user/$uid/gvfs/" ?

[mc4man]

No idea, but "burn.mount" is AutoMount=true, found under "/usr/share/gvfs/mounts/". What would happen if made false?

That would get rid of the 'error' popup (needs a new session to take affect.
blank media isn't negativity affected by the automount option for gnome, an autorun option is always possible (ask, do nothing, do something) so can't see any reason (yet) while that file shouldn't be set to false

(- in the case of optical media with something on it I think Gnome screwed this up a while back, likely part of their ongoing 'simplification'

[kansasnoob]

No idea, but "burn.mount" is AutoMount=true, found under "/usr/share/gvfs/mounts/". What would happen if made false?

I see what you mean:

lance@lance-desktop:~$ cat /usr/share/gvfs/mounts/burn.mount
[Mount]
Type=burn
Exec=/usr/lib/gvfs/gvfsd-burn
AutoMount=true

I'll give it a whirl and see what happens.

[kansasnoob]

Reboot required after changing that but it seems to work:

lance@lance-desktop:~$ cat /usr/share/gvfs/mounts/burn.mount
[Mount]
Type=burn
Exec=/usr/lib/gvfs/gvfsd-burn
AutoMount=false

That said I want to test this for a few days to be sure there are no other ill effects associated with that change.

[QDR06VV9]

No idea, but "burn.mount" is AutoMount=true, found under "/usr/share/gvfs/mounts/". What would happen if made false?

Reboot required after changing that but it seems to work:



That said I want to test this for a few days to be sure there are no other ill effects associated with that change.

Nice! Great Detective work guys.

[kansasnoob]

I decided to check Precise which was not effected and the same file is set to "true" so the actual "bug" is probably somewhere in some executable file, but if this workaround causes no problems it's certainly simple enough

I'm going to apply this workaround to my in-house "stable" Trusty installs which get used a lot for a variety of things and make sure there are no ill effects before I recommend it as a workaround to others though.