[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#688271: marked as done (debian-6.0.5-i386-xfce+lxde-CD-1.iso - "no mountable filesystems" error when mounting the image)



Your message dated Sun, 3 Jul 2016 12:32:17 +0200
with message-id <20160703123217.3991716e@a68n.lokal>
and subject line done
has caused the Debian Bug report #688271,
regarding debian-6.0.5-i386-xfce+lxde-CD-1.iso - "no mountable filesystems" error when mounting the image
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 owner@bugs.debian.org
immediately.)


-- 
688271: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688271
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-6.0.5-i386-xfce+lxde-CD-1.iso
Version: 6.0.5-i386-xfce+lxde-CD-1


Hi,

I just downloaded debian-6.0.5-i386-xfce+lxde-CD-1.iso twice from the Debian servers and twice from a Cogentco mirror, using Folx2 for 2 downloads and just downloading through Chromium for the other 2 downloads. In each case I get "no mountable filesystems" when trying to mount the image to be burned. I am able to mount any other .iso images I have, so I know it's not my machine.

Thank you for your attention to this matter, I would appreciate if I could be notified with any information about the resolution, also if you need more info from me, don't hesitate to ask.

Best regards,

Alexander Hunt

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Since this is an old report referring to Debian 6, and the current stable version is 8.x,
I deliberately close the issue, most probably it has been dealt with.
If not, please retry with a current version and file a new report.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAld46bcACgkQ5+rBHyUt5wtdBwCgsaVFcQm78vFmnq6fbRCdIjgH
Qb8Ani37mMfmMMphwjXkGJW+W/yBLETw
=aZHw
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: