Bug#836355: closed by Simon McVittie <smcv at debian.org> (Re: Bug#836355: libglib2.0-0: makes all entries of fstab show up as desktop items)
kilobyte at angband.pl
Fri Jun 7 14:56:34 BST 2019
Control: reopen -1
Control: found -1 2.58.3-2
On Fri, Jun 07, 2019 at 07:21:03AM +0000, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the libglib2.0-0 package:
> #836355: libglib2.0-0: makes all entries of fstab show up as desktop items
> It has been closed by Simon McVittie <smcv at debian.org>.
> On Fri, 07 Jun 2019 at 02:04:48 +0000, scott092707 at aol.com wrote:
> > Well, I changed my user-dirs.dirs back to the original state, and did the bind mount
> > from my data partition to my /home/scott/... user directories. All works fine.
> It sounds like there is no observable bug in Debian, then; marking this
> as closed.
> If you find a related bug on a Debian system, please report it as a
> separate bug number with details of how to reproduce the bug, using
> the reportbug(1) tool on the Debian system to gather the necessary
> information about version numbers etc.
> If you find a related bug on a Peppermint system that you cannot reproduce
> on Debian, please contact Peppermint's support channels instead.
While Scott is on Peppermint, the original submitter (me) and probably
others who chimed in are on real vanilla Debian. The bug reproduces (as on
attached screenshot) on fully up-to-date unstable, on a box installed just
yesterday from d-i daily image, on a Debian conference, by a DD, with two
other DDs debugging bootloader problems, with not a single package not in
Besides the expected "Home" and "File System" I get two extra entries:
* "Filesystem root" (/, redundant with "File System")
* "boot" (/boot)
both of which are on a non-removable disk.
New installs don't have /proc in their fstabs, but old do -- and I just
added such an entry to mine, and indeed it did show up.
This box's fstab at the time of screenshot is:
# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/mmcblk2p2 during installation
UUID=a7cd0bc6-7f6f-44bb-9379-21e561e5afaa / btrfs noatime 0 0
# /boot was on /dev/mmcblk2p1 during installation
UUID=c523e382-26a4-4ab9-8efe-a65e4eef6918 /boot ext4 noatime 0 2
# swap was on /dev/mmcblk2p5 during installation
UUID=1d9d31be-dc9a-47ae-a9a1-ec3f99bff94d none swap sw 0 0
proc /proc proc defaults
(all lines but the last were generated by d-i)
This box's internal disk is eMMC, the one in original report had regular SATA.
> > I tried GDebi-ing my current debian GLib2 libraries into Peppermint 10 system,
> > to test this theory, but each one of the three packages pointed to one of the
> > others and cited incompatibilities.
> Note that Debian does not support packages installed from other
> Debian-based distributions (if you do this, it is at your own risk,
You just closed a bug as "not for Debian" for a single commenter using a
derivative -- most of which don't even modify core packages such as glib --
without even asking the original reporter nor two other folks who also
confirmed. Alas, the BTS still has the unfortunate flaw of not sending new
mails to the submitter unless explicitly subscribed, thus you'd need CCs
when asking if the bug still reproduces. Unless the reporter subscribed
(like I just did), then they'll get two or more copies...
⣾⠁⢠⠒⠀⣿⡁ Sometimes you benefit from delegating stuff. For example,
⢿⡄⠘⠷⠚⠋⠀ this way I get to be a vegetarian.
More information about the pkg-gnome-maintainers