If I unlock my screen, the gnome-shell process reads files from my hard disk
mounted using udisks2; but the process was running all the time anyway, so
it's pointless to re-read the disk on an unlock, as nothing has changed.

This may be a bug in a library used by gnome-shell, I could not analyse
this further.

Am 16.10.2013 00:05, schrieb Julian Andres Klode:

How do you know it is gnome-shell which reads from your hard disk?
You mentioned /media/<user> something on IRC, so I assume this is only
for external drives?

Could you switch to a console and check with fuser / lsof which process
is reading from /media?

I had a loop running lsof -n | grep SecondHome (the mount point is
/media/SecondHome) in the background (started before locking the
screen). After the unlock, various files were listed there, all
opened by the gnome-shell process; and not for very long.

Just for the public record: The process doing this is
/usr/lib/gnome-shell/gnome-shell-hotplug-sniffer

It seems to recursively scan the mime types on the device, AFAICT.

Am 16.10.2013 13:19, schrieb Julian Andres Klode:

This is a D-Bus activated service.
You can kill that service and run it via
HOTPLUG_SNIFFER_DEBUG=true /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
if you want to see a more verbose output of that process

Afaics, this process is triggered by the autorun manager in gnome-shell.
(js/ui/components/autorunManager.js).

For completeness sake, could you attach the output of
$ gsettings list-recursively org.gnome.desktop.media-handling

Usually, gnome-shell-hotplug-sniffer should be activated when removable
media is plugged in, it then searches for autorun files and quits itself
after a timeout.

It seems to somehow gets stuck on your system. As said, maybe running it
in debug mode will give more info.

Michael

No need to kill it, it does not get stuck; it exists normally after running
for 1.5 seconds after the unlock. If I run it manually in debugging mode, I
see that it scans my mounted devices after unlock.

org.gnome.desktop.media-handling automount true
org.gnome.desktop.media-handling automount-open true
org.gnome.desktop.media-handling autorun-never false
org.gnome.desktop.media-handling autorun-x-content-ignore @as []
org.gnome.desktop.media-handling autorun-x-content-open-folder @as []
org.gnome.desktop.media-handling autorun-x-content-start-app ['x-content/unix-software']

It definitely quits.

severity 726454 minor
thanks

Am 16.10.2013 16:16, schrieb Julian Andres Klode:

Ah, then this was a misunderstanding on my part. In your initial email
you said that the process was running all the time and I misunderstood
that and thought you were saying that the sniffer was constantly
scanning your external drive (while you meant the gnome-shell process
itself)

With all that said, I think this is a minor issue at best and I'm
actually not sure it is a bug.
I think the issue is, that while you have your session locked, it is not
marked as being active and so doesn't process any autorun events.

When you unlock the session, it seems to do a sweep to catch up on any
events that were missed while away.

Michael