Your message dated Mon, 19 Jan 2015 10:52:56 +0000 with message-id <[email protected]> and subject line Re: Bug#601784: libglib2.0-0: Wrong behaviour of GVolume GVolumeMonitor related functions with mount --bind has caused the Debian Bug report #601784, regarding libglib2.0-0: Wrong behaviour of GVolume GVolumeMonitor related functions with mount --bind to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 601784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601784 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libglib2.0-0 Version: 2.24.2-1 Severity: important This bug was first reported as a nautilus bug, (https://bugs.launchpad.net/nautilus/+bug/452049) because it causes bind mounts (mount --bind x y) from '/etc/fstab' to show up in the nautilus side pane as 'XX G(M)B Filesystem' entries, and clicking on those entries results in a mount attempt which silently fails. The .xsession-errors file contains these messages: (gnome-panel:25862): GLib-GIO-CRITICAL **: g_mount_get_root: assertion `G_IS_MOUNT (mount)' failed (gnome-panel:25862): GLib-GIO-CRITICAL **: g_file_get_uri: assertion `G_IS_FILE (file)' failed ** (gnome-panel:25862): CRITICAL **: panel_show_uri: assertion `uri != NULL' failed (gnome-panel:25862): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gnome-panel:25862): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed The entries also show up in the 'Computer' browser, but attempts to open it result in a popup that says 'Unable to mount location Internal error: No mount object for mounted volume'. The root cause, as stated in the launchpad bug above and detailed in gnome bugzilla (https://bugzilla.gnome.org/show_bug.cgi?id=625552) has to do with Gvolume and GVolumeMonitor not properly dealing with bind mounts (i.e. g_volume_get_mount does not return a GMount object for bind mounts). More analysis and a some suggestions for additional checks to handle bind mounts are given in the gnome bugzilla issue. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libglib2.0-0 depends on: ii libc6 2.11.2-6+squeeze1 Embedded GNU C Library: Shared lib ii libpcre3 8.02-1.1 Perl 5 Compatible Regular Expressi ii libselinux1 2.0.96-1 SELinux runtime shared libraries ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages libglib2.0-0 recommends: ii libglib2.0-data 2.24.2-1 Common files for GLib library ii shared-mime-info 0.71-3 FreeDesktop.org shared MIME databa libglib2.0-0 suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Version: 2.36.0-1 On Fri, 29 Oct 2010 at 11:51:21 -0400, Dominique Brazziel wrote: > This bug was first reported as a nautilus bug, > (https://bugs.launchpad.net/nautilus/+bug/452049) > because it causes bind mounts (mount --bind x y) from '/etc/fstab' to show up > in the > nautilus side pane as 'XX G(M)B Filesystem' entries, and clicking > on those entries results in a mount attempt which silently fails. This appears to have been fixed upstream somewhere in the 2.35 series according to <https://bugzilla.gnome.org/show_bug.cgi?id=625552>. S
--- End Message ---
