Bug#726454: gnome-shell: Reads files on (gvfs-show) mountpoints after unlock
On Wed, Oct 16, 2013 at 12:19 AM, Julian Andres Klode j...@debian.org wrote: On Wed, Oct 16, 2013 at 12:13:43AM +0200, Michael Biebl wrote: Am 16.10.2013 00:05, schrieb Julian Andres Klode: Package: gnome-shell Version: 3.8.4-4 Severity: normal 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. 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. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726454: gnome-shell: Reads files on (gvfs-show) mountpoints after unlock
Am 16.10.2013 13:19, schrieb Julian Andres Klode: 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. 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 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#726454: gnome-shell: Reads files on (gvfs-show) mountpoints after unlock
On Wed, Oct 16, 2013 at 01:35:33PM +0200, Michael Biebl wrote: Am 16.10.2013 13:19, schrieb Julian Andres Klode: 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. 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 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. 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 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'] 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. It definitely quits. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Please do not top-post if possible. pgpCYy7kkfT4E.pgp Description: PGP signature
Bug#726454: gnome-shell: Reads files on (gvfs-show) mountpoints after unlock
severity 726454 minor thanks Am 16.10.2013 16:16, schrieb Julian Andres Klode: On Wed, Oct 16, 2013 at 01:35:33PM +0200, Michael Biebl wrote: It seems to somehow gets stuck on your system. As said, maybe running it in debug mode will give more info. It definitely quits. 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 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#726454: gnome-shell: Reads files on (gvfs-show) mountpoints after unlock
Package: gnome-shell Version: 3.8.4-4 Severity: normal 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. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (980, 'unstable'), (500, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.16.1-1 ii evolution-data-server3.8.5-2 ii gdm3 3.8.4-2 ii gir1.2-accountsservice-1.0 0.6.34-2 ii gir1.2-caribou-1.0 0.4.12-1 ii gir1.2-clutter-1.0 1.14.4-3 ii gir1.2-freedesktop 1.36.0-2+b1 ii gir1.2-gcr-3 3.8.2-4 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.36.0-2+b1 ii gir1.2-gmenu-3.0 3.8.0-2 ii gir1.2-gnomebluetooth-1.03.8.1-2 ii gir1.2-gnomedesktop-3.0 3.8.4-2 ii gir1.2-gtk-3.0 3.8.5-1 ii gir1.2-ibus-1.0 1.5.3-7 ii gir1.2-mutter-3.03.8.4-2 ii gir1.2-networkmanager-1.00.9.8.0-5 ii gir1.2-nmgtk-1.0 0.9.8.4-1 ii gir1.2-pango-1.0 1.32.5-5+b1 ii gir1.2-polkit-1.00.105-3+nmu1 ii gir1.2-soup-2.4 2.42.2-6 ii gir1.2-telepathyglib-0.120.22.0-1 ii gir1.2-telepathylogger-0.2 0.8.0-2 ii gir1.2-upowerglib-1.00.9.22-1 ii gjs 1.36.1-2 ii gnome-bluetooth 3.8.1-2 ii gnome-icon-theme-symbolic3.8.2.2-2 ii gnome-settings-daemon3.8.5-2 ii gnome-shell-common 3.8.4-4 ii gnome-themes-standard3.8.4-1 ii gsettings-desktop-schemas3.8.2-2 ii libatk-bridge2.0-0 2.10.0-1 ii libatk1.0-0 2.10.0-2 ii libc62.17-93 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libcamel-1.2-43 3.8.5-2 ii libcanberra-gtk3-0 0.30-2 ii libcanberra0 0.30-2 ii libclutter-1.0-0 1.14.4-3 ii libcogl-pango12 1.14.0-3 ii libcogl121.14.0-3 ii libcroco30.6.8-2 ii libdbus-1-3 1.6.16-1 ii libdbus-glib-1-2 0.100.2-1 ii libecal-1.2-15 3.8.5-2 ii libedataserver-1.2-173.8.5-2 ii libegl1-mesa [libegl1-x11] 9.1.7-1 ii libgck-1-0 3.8.2-4 ii libgcr-base-3-1 3.8.2-4 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libgirepository-1.0-11.36.0-2+b1 ii libgjs0c [libgjs0-libmozjs185-1.0] 1.36.1-2 ii libglib2.0-0 2.36.4-1 ii libgnome-menu-3-03.8.0-2 ii libgstreamer1.0-01.2.0-1 ii libgtk-3-0 3.8.5-1 ii libical0 0.48-2 ii libjson-glib-1.0-0 0.16.2-1 ii libmozjs185-1.0 1.8.5-1.0.0+dfsg-4+b1 ii libmutter0b 3.8.4-2 ii libnm-glib4 0.9.8.0-5 ii libnm-gtk0 0.9.8.4-1 ii libnm-util2 0.9.8.0-5 ii libnspr4 2:4.10-1 ii libnss3 2:3.15.1-1 ii libnss3-1d 2:3.15.1-1 ii libp11-kit0 0.18.5-3 ii libpango-1.0-0 1.32.5-5+b1 ii libpangocairo-1.0-0 1.32.5-5+b1 ii libpolkit-agent-1-0 0.105-3+nmu1 ii libpolkit-gobject-1-00.105-3+nmu1 ii libpulse-mainloop-glib0 4.0-6+b1 ii
Bug#726454: gnome-shell: Reads files on (gvfs-show) mountpoints after unlock
Am 16.10.2013 00:05, schrieb Julian Andres Klode: Package: gnome-shell Version: 3.8.4-4 Severity: normal 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. 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? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#726454: gnome-shell: Reads files on (gvfs-show) mountpoints after unlock
On Wed, Oct 16, 2013 at 12:13:43AM +0200, Michael Biebl wrote: Am 16.10.2013 00:05, schrieb Julian Andres Klode: Package: gnome-shell Version: 3.8.4-4 Severity: normal 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. 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. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Please do not top-post if possible. pgpshQckrAb1q.pgp Description: PGP signature
