On Wed, 26 Apr 2017 at 12:09:02 +0100, Ben Green wrote: > Quoting Simon McVittie <s...@debian.org>: > > I speculate that in Ben's case, dbus-daemon might be selecting a file > > manager that is broken in some way, such that it silently fails to > > start up. Running "dbus-monitor --session" while reproducing this bug > > might provide evidence for or against this. > > > > Well there's no shortage of output from that
Huh. There is indeed no shortage of output, but it all seems to be gvfs: none of it is an attempt to send messages to Nautilus. I was expecting to see a message trying to start Nautilus (or more precisely org.freedesktop.FileManager1) and perhaps an error reply. Perhaps it would be more informative if you dbus-monitor'd the first attempt to reproduce this bug after a reboot? Or if not that, then sorry, I've run out of ideas. S