The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: glib2.0 (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
** Changed in: glib
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/452049
Title:
Gnome Places contains filesystems mounted via bind
Status in
** Branch linked: lp:ubuntu/raring-proposed/glib2.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/452049
Title:
Gnome Places contains filesystems mounted via bind
Status in The G
It would be quite nice to get this fix pack ported to quantal and
precise. Given its only a two liner I assume there wont be much if any
side effects to this patch.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
It would be quite nice to get this fix pack ported to quantal and
precise. Given its only a two liner I assume there wont be much if any
side effects to this patch.
that's why a precise line was added to the bug table, I'm unsure it's
worth backporting on nonLTS (e.g quantal) though, that bug
Correct me if I am wrong, but I am assuming that the effort does not
increase if the fix is backported to two lines instead of one? This is
probably a mostly automatic procedure, or not?
And it could after all make a few people happy :)
--
You received this bug notification because you are a
This bug was fixed in the package glib2.0 - 2.35.4-0ubuntu5
---
glib2.0 (2.35.4-0ubuntu5) raring; urgency=low
* debian/patches/git_fix_gvariant_tuple_checking.patch:
- should fix a dconf-service segfault issue (lp: #1105102)
-- Sebastien Bacher seb...@ubuntu.com Fri, 25 Jan
** Also affects: glib2.0 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: glib2.0 (Ubuntu Precise)
Status: New = Triaged
** Changed in: glib2.0 (Ubuntu Precise)
Importance: Undecided = Low
--
You received this bug notification because you are a member of
** Changed in: nautilus
Status: New = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/452049
Title:
Gnome Places contains filesystems mounted via bind
Status in
The upstream bug has now a working patch for the problem. If it cannot
be backported then it should probably arrive in Gnome 3.8
--- a/gio/gunixmounts.c
+++ b/gio/gunixmounts.c
+ /* We ignore bind fstab entries, as we ignore bind mounts anyway */
+ if (hasmntopt (mntent, bind))
+
@Otus: raring is tracking the current unstable glib so that fix will
land with the next release
** Changed in: glib2.0 (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
Like Michael Weimann, I only started seeing this under 12.10. Ubuntu
12.04 was fine, although I copied my fstab over. Maybe the bug used to
be quite specific, but now applies more generally.
One difference I see from the OP is that my mounts are all root:
/media/data/folder
Since the update to Ubuntu 12.10 beta this bug affects me. Under 12.04
the behavior was as expected: bind mounted directories were not shown as
devices.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
This surprises me, because I am under 12.04 and do see this bug, its
actually present since several years.
The problem lies in the code of glib. Nautilus actually has some code in
place to differentiate between bind mounted mount points and other mount
points. But glib (gio) is not properly
14 matches
Mail list logo