Debian Bug report logs - #775689
Do NOT use unetbootin for Debian CD images

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Steve McIntyre <steve@einval.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: Do NOT use unetbootin for Debian CD images

Date: Sun, 18 Jan 2015 18:06:18 +0000

Source: unetbootin
Severity: serious
Tags: d-i
Justification: wasting massive amounts of developer and user time

I've already added one wishlist bug for d-i to add code to detect
unetbootin usage and complain about it, but I've not got there
yet. unetbootin used to be a helpful tool for many people to create
USB-bootable installer images, but these days seems responsible for
lots of user problems and difficult-to-resolve bug reports. Using it
for Debian CD images creates USB images that do not work correctly.
It's not even needed any more - we've been making working iso-hybrid
images for years now.

Unetbootin is wasting massive amounts of developer and user time. :-(

Please add:

 * An entry in the Debian package description to say "Do not use
   unetbootin for Debian CD images, just write them raw using dd" or
   similar.

 * A runtime warning (with a similar message) if the user is
   attempting to use unetbootin for a Debian CD image.

-- System Information:
Debian Release: 7.8
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Message #10 received at 775689@bugs.debian.org (full text, mbox, reply):

From: László Böszörményi (GCS) <gcs@debian.org>

To: Steve McIntyre <steve@einval.com>, 775689@bugs.debian.org

Subject: Re: Bug#775689: Do NOT use unetbootin for Debian CD images

Date: Sun, 18 Jan 2015 19:40:11 +0100

Control: tag -1 moreinfo

Hi Steve,

On Sun, Jan 18, 2015 at 7:06 PM, Steve McIntyre <steve@einval.com> wrote:
> Source: unetbootin
> Severity: serious
> Tags: d-i
> Justification: wasting massive amounts of developer and user time
>
> I've already added one wishlist bug for d-i to add code to detect
> unetbootin usage and complain about it, but I've not got there
> yet. unetbootin used to be a helpful tool for many people to create
> USB-bootable installer images, but these days seems responsible for
> lots of user problems and difficult-to-resolve bug reports. Using it
> for Debian CD images creates USB images that do not work correctly.
> It's not even needed any more - we've been making working iso-hybrid
> images for years now.
 Can you give me pointers where those bugreports exist? Do you have
first hand experience that it's not working correctly?
I made netboot images onto my USB sticks and they worked. Especially
that it's not the same like copy the iso over the USB drive. Its
non-destructive install doesn't format the device, you may use that
for storage as well.
Also please note it's not a Debian specific tool. But it may exists in
Fedora as well for example. Those users may install a Debian boot to
their USB sticks. Adding a warning for our users won't warn other
users using UNetbootin.

Kind regards,
Laszlo/GCS

Message #17 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Thorsten Glaser <t.glaser@tarent.de>

To: László Böszörményi (GCS) <gcs@debian.org>

Cc: 775689@bugs.debian.org

Subject: Re: Bug#775689: Do NOT use unetbootin for Debian CD images

Date: Mon, 19 Jan 2015 09:45:11 +0100 (CET)

On Sun, 18 Jan 2015, László Böszörményi (GCS) wrote:

> Also please note it's not a Debian specific tool. But it may exists in

Right. I think users of Debian derivate which must not be named
use it when they don’t manage to type “sudo dd”. I suggest to
patch it upstream to recognise at the very least Debian ISOs, if
not all isohybrid and manifold-boot ISOs, and just dd them over
if found, instead of doing whatever it is otherwise doing.

“manifold-boot” is to MirBSD and Grml ISOs pretty much what was
added as “isohybrid” to ISOLINUX later. It can be detected by
the string 20 4c 6f 61 64 69 6e 67 20 00 62 61 64 20 6d 61 67
69 63 20 65 72 72 6f 72 0d 0a 00 either in sector 0, usually
around offset 0x20-0x40, or in sector 24 (ISO offset usually
around 0x3020-0x3040) with sector 0 containing a Sun disklabel
(magic bytes da be at offset 0x1FC) with an i386 bootsector
magic (bytes 55 aa at offset 0x1FE). Currently. Subject to be
expanded later ;)

bye,
//mirabilos
-- 
>> Why don't you use JavaScript? I also don't like enabling JavaScript in
> Because I use lynx as browser.
+1
	-- Octavio Alvarez, me and ⡍⠁⠗⠊⠕ (Mario Lang) on debian-devel

Message #22 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Steve McIntyre <steve@einval.com>

To: László Böszörményi (GCS) <gcs@debian.org>

Cc: 775689@bugs.debian.org

Subject: Re: Bug#775689: Do NOT use unetbootin for Debian CD images

Date: Tue, 20 Jan 2015 01:15:13 +0000

On Sun, Jan 18, 2015 at 07:40:11PM +0100, László Böszörményi (GCS) wrote:
>Control: tag -1 moreinfo
>
>Hi Steve,

Hi!

>> USB-bootable installer images, but these days seems responsible for
>> lots of user problems and difficult-to-resolve bug reports. Using it
>> for Debian CD images creates USB images that do not work correctly.
>> It's not even needed any more - we've been making working iso-hybrid
>> images for years now.
> Can you give me pointers where those bugreports exist? Do you have
>first hand experience that it's not working correctly?

Admittedly most of the reports are not in the BTS, they're mails from
people struggling to get things to work, or reporting odd behaviour. A
quick Google search on site:lists.debian.org points to the following
threads, for starters:

 * https://lists.debian.org/debian-live/2014/08/msg00052.html
 * https://lists.debian.org/debian-edu/2011/06/msg00104.html
 * https://lists.debian.org/debian-user/2014/04/msg01259.html
 * https://lists.debian.org/debian-user/2014/06/msg01064.html
 * https://lists.debian.org/debian-user/2014/02/msg01185.html

In particular, as I've been developing and improving our UEFI boot
support for Wheezy and Jessie, I've had a fair number of people report
problems to me directly when trying to use my test images, that went
away when unetbootin was taken our of the equation. This has wasted
hours of back-and-forth debug discussions in some cases. I don't see
any support for UEFI in unetbootin, and other things on the net like

 * http://askubuntu.com/questions/374931/install-ubuntu-in-uefi-mode-unable-to-boot-from-usb
 * https://wiki.archlinux.org/index.php/USB_flash_installation_media#Using_UNetbootin
 * http://ubuntuforums.org/showthread.php?t=2130039

back that up. This is a major issue on newer machines.

>Also please note it's not a Debian specific tool. But it may exists in
>Fedora as well for example. Those users may install a Debian boot to
>their USB sticks. Adding a warning for our users won't warn other
>users using UNetbootin.

I know that, but a warning for Debian users would help too. I'm also
tempted to look into how to detect unetbootin media within d-i so that
we can potentially flash up a warning to the user. I *know* it may be
a useful tool for some folks (and it used to be very helpful/necessary
for USB stuff on older releases), but it's becoming a major PITA.

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
"C++ ate my sanity" -- Jon Rabone

Message #27 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Stuart Prescott <stuart@debian.org>

To: 775689@bugs.debian.org

Subject: Re: Bug#775689: Do NOT use unetbootin for Debian CD images

Date: Tue, 20 Jan 2015 20:41:12 +1100

Hi!

>  Can you give me pointers where those bugreports exist? Do you have
> first hand experience that it's not working correctly?
> I made netboot images onto my USB sticks and they worked. 

This exchange is sadly pretty common when it comes to unetbootin and we see 
this frequently in #debian. Whenever we get a user reporting a very odd error 
from the installer, we ask them how they transferred the image to the USB 
stick and if they say "unetbootin" we just recommend they start again because 
it is well known to cause problems. Two things then always follow: (1) the 
problem is solved and the installation completes fine (2) a 3rd party will chip 
in that unetbootin always works just fine for them [sadly often also 
accompanied by (3) them telling us we don't know what we're talking about].

We have been unable to figure out what differentiates the users for whom 
unetbootin does not work from the users for whom it does work. The users who 
have chosen to use unetbootin are almost invariably not the right people to 
help debug such problems and so the impasse is perpetuated. (While unetbootin 
can also do other things like have multiple images on the one disk, that's not 
the user base we are normally seeing.)

Off the top of my head the are the sorts of errors we frequently see are 
catalogued below. I've quickly grabbed some links from upstream's bug tracker 
that may (or may not!) provide some more details. All of these errors go away 
when the exact same image is copied onto the exact same USB stick using cp as 
detailed in the install guide (or dd or cat or win32diskimager or anything 
else that just copies the image rather than trying to do whatever mangling 
unetbootin does).

* boot error messages: the prepared image is deeply unhappy and you don't even 
get as far as a boot loader. (The normal symptom reported by the user is "why 
aren't debian iso images bootable?"...)

	https://bugs.launchpad.net/unetbootin/+bug/1198731

* d-i starts but then dies weirdly, seemingly skipping the entire installation

	https://bugs.launchpad.net/unetbootin/+bug/1348956

* d-i dies very early with "No CD was detected": for some reason, the mounted 
image is not found by the installer and you don't get past the very first part 
of the installer where it tries to find the d-i components.

	https://bugs.launchpad.net/unetbootin/+bug/622075

* installing the base system fails: sometimes it can't find the .debs, 
sometimes it can't figure out how to extract them properly

	https://bugs.launchpad.net/unetbootin/+bug/1048913

* even once d-i looks to have successfully completed, it often seems to 
install grub to the wrong device and/or has sufficiently confused grub-install 
as to get the wrong device.map so that the system isn't bootable

	https://bugs.launchpad.net/unetbootin/+bug/1034975


Clearly not everyone hits these errors but enough do that it's a pain. The 
errors seem so unrelated to unetbootin that it's very hard to convince users 
to try remaking the image -- after all, once the kernel is booted and 
userspace has started, unetbootin should be irrelevant, right? If only.

> Also please note it's not a Debian specific tool. But it may exists in
> Fedora as well for example. Those users may install a Debian boot to
> their USB sticks. Adding a warning for our users won't warn other
> users using UNetbootin.

Indeed, it would be wonderful if this were actually fixed upstream (or at least 
documented upstream). In the absence of that, we at least reach a good portion 
of the user base by noting this in Debian (and its derivatives).

cheers
Stuart

-- 
Stuart Prescott    http://www.nanonanonano.net/   stuart@nanonanonano.net
Debian Developer   http://www.debian.org/         stuart@debian.org
GPG fingerprint    90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Message #34 received at 775689@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>

To: Steve McIntyre <steve@einval.com>

Cc: "László Böszörményi (GCS)" <gcs@debian.org>, Thorsten Glaser <t.glaser@tarent.de>, Stuart Prescott <stuart@debian.org>, 775689@bugs.debian.org

Subject: Re: Bug#775689: Do NOT use unetbootin for Debian CD images

Date: Tue, 17 Feb 2015 10:43:48 +0100

Hi!

I fully agree with Steve's stance. unetbootin is currently completely
broken and I don't think it should actually be shipped with Jessie.

Just as of yesterday, a colleague of mine created a bootable USB flash
drive with FreeDOS in order to flash the BIOS firmware of the new
servers we got. While the FreeDOS actually booted, he ran into random
crashes and couldn't copy the BIOS firmware and utilities onto the
flash drive from Linux so that he could later run the BIOS utility
from within FreeDOS. The files just weren't there.

When he asked me for help, my first question was "Did you use
unetbootin"? and after he acknowledged that, the first thing we did
was to rewrite the image using dd which fixed all the issues he
had.

I would even argue that we should remove unetbootin from Debian
altogether since I think it's rather a design problem and I think
it's pretty much hopeless that upstream will fix the nearly 300
bugs in their bug tracker.

After all, corrupted installation media could possibly result
in serious data loss and I don't think it's acceptable to have
such dangerously unreliable software in Debian.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Message #39 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Thorsten Glaser <t.glaser@tarent.de>

To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>

Cc: Steve McIntyre <steve@einval.com>, "László Böszörményi (GCS)" <gcs@debian.org>, Stuart Prescott <stuart@debian.org>, 775689@bugs.debian.org

Subject: Re: Bug#775689: Do NOT use unetbootin for Debian CD images

Date: Tue, 17 Feb 2015 11:11:33 +0100 (CET)

On Tue, 17 Feb 2015, John Paul Adrian Glaubitz wrote:

> I fully agree with Steve's stance. unetbootin is currently completely
> broken and I don't think it should actually be shipped with Jessie.

Shipping it with jessie is irrelevant to using it for Debian images.

> After all, corrupted installation media could possibly result
> in serious data loss and I don't think it's acceptable to have
> such dangerously unreliable software in Debian.

Completely disagree: unetbootin is the tool of choice to create
bootable images for a variety of distributions, so shipping it
with Debian is correct, for those distributions. Just that the
software should not be used for creating broken *Debian* images.
That is something to be fixed upstream, because the person using
it for such is typically *not* running Debian.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Message #44 received at 775689@bugs.debian.org (full text, mbox, reply):

From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>

To: Thorsten Glaser <t.glaser@tarent.de>

Cc: Steve McIntyre <steve@einval.com>, "László Böszörményi (GCS)" <gcs@debian.org>, Stuart Prescott <stuart@debian.org>, 775689@bugs.debian.org

Subject: Re: Bug#775689: Do NOT use unetbootin for Debian CD images

Date: Tue, 17 Feb 2015 11:19:34 +0100

On 02/17/2015 11:11 AM, Thorsten Glaser wrote:
> Completely disagree: unetbootin is the tool of choice to create
> bootable images for a variety of distributions, so shipping it
> with Debian is correct, for those distributions. Just that the
> software should not be used for creating broken *Debian* images.
> That is something to be fixed upstream, because the person using
> it for such is typically *not* running Debian.

I think you missed the part where I was talking about non-Debian
images. It clearly breaks non-Debian images as well, for example
FreeDOS. Just look at the bug tracker with almost 300 bugs:

	https://bugs.launchpad.net/unetbootin

It's completely broken and just produces headaches for both users
and developers. I don't know why something that is so broken should
be a "tool of choice". What's the point in shipping unetbootin
when half of the boot media it creates are not working properly?

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Message #49 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Thorsten Glaser <t.glaser@tarent.de>

To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>

Cc: Steve McIntyre <steve@einval.com>, "László Böszörményi (GCS)" <gcs@debian.org>, Stuart Prescott <stuart@debian.org>, 775689@bugs.debian.org

Subject: Re: Bug#775689: Do NOT use unetbootin for Debian CD images

Date: Tue, 17 Feb 2015 11:21:39 +0100 (CET)

On Tue, 17 Feb 2015, John Paul Adrian Glaubitz wrote:

> I think you missed the part where I was talking about non-Debian
> images. It clearly breaks non-Debian images as well, for example

It needs a list of images it can operate on, and refuse on all
others, then.

> FreeDOS. Just look at the bug tracker with almost 300 bugs:
> 
> 	https://bugs.launchpad.net/unetbootin
> 
> It's completely broken and just produces headaches for both users

In this case… ok it probably should not be in the release.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Message #54 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Nio Wiklund <nio.wiklund@gmail.com>

To: 775689@bugs.debian.org

Subject: mkusb

Date: Fri, 13 Mar 2015 10:34:38 +0100

From: Steve McIntyre <steve@einval.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Do NOT use unetbootin for Debian CD images
Date: Sun, 18 Jan 2015 18:06:18 +0000

Source: unetbootin
Severity: serious
Tags: d-i
Justification: wasting massive amounts of developer and user time
...
Please add:

 * An entry in the Debian package description to say "Do not use
   unetbootin for Debian CD images, just write them raw using dd" or
   similar.
_____

I would suggest wrapping safety around dd with the shell-script 'mkusb'.

Extra safety can be very important because dd is nick-named 'disk
destroyer' for a reason: It does what you *tell* it to do without
questions, even if it is not what you *want* to do (for example wipe a
drive with not yet backed up family photos).

mkusb is tested with debian Jessie (and worked reliably after some
tweaks). If you are interested, I can try to make it work without tweaks.

There is a PPA for Ubuntu, but for Debian please look at this link

https://help.ubuntu.com/community/mkusb/v9#from_phillw.net

Best regards
Nio

Message #59 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Nio Wiklund <nio.wiklund@gmail.com>

To: 775689@bugs.debian.org

Subject: tip

Date: Fri, 13 Mar 2015 11:27:59 +0100

Hi László,
_____

From: Thorsten Glaser <t.glaser@tarent.de>
To: László Böszörményi (GCS) <gcs@debian.org>
Cc: 775689@bugs.debian.org
Subject: Re: Bug#775689: Do NOT use unetbootin for Debian CD images
Date: Mon, 19 Jan 2015 09:45:11 +0100 (CET)

On Sun, 18 Jan 2015, László Böszörményi (GCS) wrote:

> Also please note it's not a Debian specific tool. But it may exists in

Right. I think users of Debian derivate which must not be named
use it when they don’t manage to type “sudo dd”. I suggest to
patch it upstream to recognise at the very least Debian ISOs, if
not all isohybrid and manifold-boot ISOs, and just dd them over
if found, instead of doing whatever it is otherwise doing.
_____

I suggested mkusb to be used now, but I also want to say that I have
used Unetbootin for years, and it is working well most of the time. It
is very good when people want persistence, and when they want to use the
pendrive for storage too (I don't, pendrives are temporary devices for
me). But sometimes there are bugs, when a new distro or version is
different in a way, that is not recognized by Unetbootin. This seems to
be the case now with Debian Jessie.

If you add a 'dd' cloning option, it would make Unetbootin even more
useful. You are welcome to borrow whatever code and concepts you want
from mkusb, it is FOSS :-)

Best regards
Nio

Message #64 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Nio Wiklund <nio.wiklund@gmail.com>

To: 775689@bugs.debian.org

Subject: mkusb-nox

Date: Sun, 15 Mar 2015 14:24:07 +0100

Den 2015-03-13 10:34, Nio Wiklund skrev:
...
> I would suggest wrapping safety around dd with the shell-script 'mkusb'.
> 
> Extra safety can be very important because dd is nick-named 'disk
> destroyer' for a reason: It does what you *tell* it to do without
> questions, even if it is not what you *want* to do (for example wipe a
> drive with not yet backed up family photos).
> 
> mkusb is tested with debian Jessie (and worked reliably after some
> tweaks). If you are interested, I can try to make it work without tweaks.
> 
> There is a PPA for Ubuntu, but for Debian please look at this link
> 
> https://help.ubuntu.com/community/mkusb/v9#from_phillw.net
> 
> Best regards
> Nio
> 

I should add that there is a command line version of mkusb

mkusb-nox

and it works without any tweaks when running as root in Debian Jessie
(tested with debian-jessie-DI-rc1-amd64-kde-CD-1.iso).

Best regards
Nio

Message #69 received at 775689@bugs.debian.org (full text, mbox, reply):

From: No-one you-know <xrs557@gmail.com>

To: 775689@bugs.debian.org

Subject: Re: Do NOT use unetbootin for Debian CD images - DD doesn't work for me

Date: Tue, 18 Aug 2015 02:03:27 -0400

[Message part 1 (text/plain, inline)]

DD doesn't work for me. It never has on linux. It creates a nonbootable
brick. As a matter of fact, no tool on the linux platform used to create
bootable usb drives based on an ISO image has ever worked for me. Strangely
enough, unetbootin, although the bootable usb it creates is buggy, actually
boots, when created on the windows platform.

go figure.

On Sun, 18 Jan 2015 18:06:18 +0000 Steve McIntyre <steve@einval.com> wrote:
> Source: unetbootin
> Severity: serious
> Tags: d-i
> Justification: wasting massive amounts of developer and user time
>
> I've already added one wishlist bug for d-i to add code to detect
> unetbootin usage and complain about it, but I've not got there
> yet. unetbootin used to be a helpful tool for many people to create
> USB-bootable installer images, but these days seems responsible for
> lots of user problems and difficult-to-resolve bug reports. Using it
> for Debian CD images creates USB images that do not work correctly.
> It's not even needed any more - we've been making working iso-hybrid
> images for years now.
>
> Unetbootin is wasting massive amounts of developer and user time. :-(
>
> Please add:
>
>  * An entry in the Debian package description to say "Do not use
>    unetbootin for Debian CD images, just write them raw using dd" or
>    similar.
>
>  * A runtime warning (with a similar message) if the user is
>    attempting to use unetbootin for a Debian CD image.
>
> -- System Information:
> Debian Release: 7.8
>   APT prefers stable
>   APT policy: (500, 'stable'), (500, 'oldstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
>

[Message part 2 (text/html, inline)]

Message #74 received at 775689@bugs.debian.org (full text, mbox, reply):

From: manyoup85@gmail.com

To: 775689@bugs.debian.org

Subject: Re: Do NOT use unetbootin for Debian CD images

Date: Sat, 21 May 2016 06:40:18 +0000 (UTC)

[Message part 1 (text/plain, inline)]

On Sun, 18 Jan 2015 18:06:18 +0000 Steve McIntyre <steve@einval.com> wrote:

> Source: unetbootin

> Severity: serious

> Tags: d-i

> Justification: wasting massive amounts of developer and user time

> 

> I've already added one wishlist bug for d-i to add code to detect

> unetbootin usage and complain about it, but I've not got there

> yet. unetbootin used to be a helpful tool for many people to create

> USB-bootable installer images, but these days seems responsible for

> lots of user problems and difficult-to-resolve bug reports. Using it

> for Debian CD images creates USB images that do not work correctly.

> It's not even needed any more - we've been making working iso-hybrid

> images for years now.

> 

> Unetbootin is wasting massive amounts of developer and user time. :-(

> 

> Please add:

> 

> * An entry in the Debian package description to say "Do not use

> unetbootin for Debian CD images, just write them raw using dd" or

> similar.

> 

> * A runtime warning (with a similar message) if the user is

> attempting to use unetbootin for a Debian CD image.

> 

> -- System Information:

> Debian Release: 7.8

> APT prefers stable

> APT policy: (500, 'stable'), (500, 'oldstable')

> Architecture: amd64 (x86_64)

> Foreign Architectures: i386

> 

> Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)

> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

> Shell: /bin/sh linked to /bin/dash

> 

>

[Message part 2 (text/html, inline)]

Message #79 received at 775689@bugs.debian.org (full text, mbox, reply):

From: manyoup85@gmail.com

To: 775689@bugs.debian.org

Date: Sat, 21 May 2016 06:40:58 +0000 (UTC)

[Message part 1 (text/plain, inline)]

ดาวน์โหลด Outlook for Android

[Message part 2 (text/html, inline)]

Message #84 received at 775689@bugs.debian.org (full text, mbox, reply):

From: manyoup85@gmail.com

To: 775689@bugs.debian.org

Subject: This app is terrific, give it a try!

Date: Sat, 21 May 2016 03:32:58 -0700 (PDT)

[Message part 1 (text/plain, inline)]

Wifi File Transfer- apps4u@android

Wifi File Transfer helps you to Explore Files/Folder Right from your  
Computer's Browser over a wifi connection.

Features.
High Performance.
Easy To User Web Interface
Fast and Simple.
Delete, rename, copy, zip or unzip files remotly using Web Interface.
No Limitations - ...

Install application via  
https://plus.google.com/appinvite/337675618254-0fe57d48-5e7d-43cd-b534-bf9a40166ab7

[Message part 2 (text/html, inline)]

Message #89 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Manyou Pending <manyoup85@gmail.com>

To: 775689@bugs.debian.org, G360HDDUOAOB2@gmail.com

Subject: Re: Bug#775689: Info received (This app is terrific, give it a try!)

Date: Sat, 21 May 2016 03:39:49 -0700

[Message part 1 (text/plain, inline)]

เมื่อ 21 พ.ค. 2016 5:36 หลังเที่ยง "Debian Bug Tracking System" <
owner@bugs.debian.org> เขียนว่า

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Laszlo Boszormenyi (GCS) <gcs@debian.org>
>
> If you wish to submit further information on this problem, please
> send it to 775689@bugs.debian.org.
>
> Please do not send mail to owner@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 775689: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775689
> Debian Bug Tracking System
> Contact owner@bugs.debian.org with problems
>

[Message part 2 (text/html, inline)]

Message #94 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Geza Kovacs <geza0kovacs@gmail.com>

To: 775689@bugs.debian.org

Subject: Re: Bug#775689: Do NOT use unetbootin for Debian CD images

Date: Sun, 22 May 2016 04:50:07 -0700

[Message part 1 (text/plain, inline)]

Hi I'm the maintainer of unetbootin, I just stumbled upon this bug report,
sorry you have been having issues. The underlying issue appears to be that
some of Debian's ISO files violate the Joilet standard - the standard does
not permit filenames exceeding 64 characters in length, as you can see at
https://en.wikipedia.org/wiki/Joliet_(file_system) . Hence any tool for
processing ISO files which follows the Joilet standard, like 7-zip (which
is used by unetbootin), will have undefined behavior when dealing with such
files (in the case of 7-zip it truncates the filenames to 64 characters).
The upstream report for 7-zip is at
https://sourceforge.net/p/sevenzip/bugs/1055/ but unetbootin is not the
only tool dealing with ISO files that relies on 7-zip (or other tools that
expect Joilet-compliant ISO files), so a solution might be to just respect
the 64-character limit for filenames in ISO files.

[Message part 2 (text/html, inline)]

Message #99 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Manyou Pending <manyoup85@gmail.com>

To: 775689@bugs.debian.org

Date: Wed, 1 Jun 2016 00:59:50 -0700

[Message part 1 (text/plain, inline)]

[Message part 2 (text/html, inline)]

Message #104 received at 775689@bugs.debian.org (full text, mbox, reply):

From: "Christies, Trish" <pchristies@museum.vic.gov.au>

To: "in@uk.ca" <in@uk.ca>, "mrs.cherry110@hotmail.com" <mrs.cherry110@hotmail.com>

Subject: Re URGENT

Date: Wed, 14 Sep 2016 15:38:32 +0000

I need your urgent assistance concerning a very important proposal, kindly contact me only at mrs.cherry110@hotmail.com

Best Regards,
Mrs Cherry Lee









































This e-mail is solely for the named addressee and may be confidential. You should only read, disclose, transmit, copy, distribute, act in reliance on or commercialise the contents if you are authorised to do so. If you are not the intended recipient of this e-mail, please notify postmaster@museum.vic.gov.au <mailto:postmaster@museum.vic.gov.au>  by email immediately, or notify the sender and then destroy any copy of this message. Views expressed in this email are those of the individual sender, except where specifically stated to be those of an officer of Museum Victoria. Museum Victoria does not represent, warrant or guarantee that the integrity of this communication has been maintained nor that it is free from errors, virus or interference.

Message #109 received at 775689@bugs.debian.org (full text, mbox, reply):

From: Gagagawo Farkas <jg45687@gmail.com>

To: undisclosed-recipients:;

Subject: Dear Wiklund

Date: Tue, 31 Jan 2017 11:06:38 +0100

[Message part 1 (text/plain, inline)]

[image: Inline image 1]

[Message part 2 (text/html, inline)]

[image.png (image/png, inline)]

Message #114 received at 775689@bugs.debian.org (full text, mbox, reply):

From: webmaster@vozmizamuzh.ru

To: 775689@bugs.debian.org

Subject: Delivery Status Notification

Date: Fri, 31 Mar 2017 06:20:20 +0300

[Message part 1 (text/plain, inline)]

Dear Customer,

Please check the attachment for your item delivery details!

FedEx

-----BEGIN PGP PUBLIC KEY BLOCK-----

HoSfx0hjOcrz+agth1o+O2VH9hjfxVP1tLWoRd0yJpYCmaSydG3KcI6W2bFu9LjxsPcFy5GpyO82
AwC4YSoPcN14DWYjJgT0g7kP8k6H6JXivJQOCTZ2O8dOfid39igP8pTfeBpOGdBnt6u9u1r7Tt+m
fy9oM3xEcZTIv4t58iyrVlhAH65Q23RH6KY7ONKKP0QV8sXjMsSkCe+DCW5IfdBasQADw6TUCVQ/
JNdRyWA1yh1yL7nSbLyRWxFpoAkc44ArV+i/k9XgGXFwRStHEyX79NnsQ3J5VR0xZ5J5bXJLDCbD
3D3qQC6acvEpWk2YybrbcRxaKvVVtQTZ6UpG9pRSboKBEXozbluhFTe99eSWxuMbvUcP36DNs7Ah
sbFHka8PYKAdSEbMEfy9HD+p6PE2Hd9T3ZoEuQvAxIzedU88LacNmlqHStdOwzu8pccvwxLSmX5J
t6BnDPQFqAi5ppkMpqtrCCtaCPUKxCh3lqiSsjDa6HOeMOAl76hABEm01DsHlnz6Q6EHbymzipwr
CeUkHEWwdKNT2LohlBEdoZNv6v+2vzS8Z1l//dk23RmXuQDvbBOMy60vv04RwgVhLCAoaRNedXAX
wro4VFGEB7pLScYur/idceEWJIaoTkZSlrvK+9cHVEQ29vX8iLuL+v4WLRzlQsyp9R+EmMSMb8/x
kkvYRGBnOqZYWrXlLhdpp+3i31FG3jcxfqkEq/FijjvKAxrVyLdRAA3RyxNerclJUB+VP0Qrdf4Z
vEwt5XQxxu75W2PC5cHDiNYsVOz+feRQijxFgv7Yz8sZ1hVDuYR4joThlIqeK8RXRGIHjLhUb2zx
xJugVqdGV6rPl1ch3mwwHA1ONuvHOmaOL6kDSiHKlKF79EJQSD4gpFe/3Vl3sHWF84V5MMjYkFc6
rpuzMxFcms1YGesfYM/San1JwCDcSNqLX5XPg6S+F4u0CtSCcJXmyDWQnpVB66IGKcxnEYR0xdjZ
xmI/K8d9aTS8HqLDNsDyRuupOgghHCyrog60aPbreezlMWmAiv5SuqJOCUpCYJGvWRnU6K82Ore8
8thX7O/FFQaaRmB/+9q6+WHwUnArLWlr80/fmocRlvAPDrlRN3y0IQyIAz/ePDshNMBWyoICzMr2
+Hd7yyNVZnpY4ugbhJ+bXwgmxJAyQ4FKQEzvCEQ+zfXqUTxIe0DXglCqsRagSmQniK116fC4+4yQ
zrI1n9vavkuJk61gnE+6bUFFknsSSM0K0MjR32SiFCtf1aX1E5oAoKuHCaeVzJ0sBTOPXyj0lWrk
wntCqee4FahZ9gFtXsExCKfH9q2AD48H3cwz0vdfZA==


-----END PGP PUBLIC KEY BLOCK-----

[FedEx-Delivery-Details-ID-YN3E3UAN.zip (application/zip, attachment)]

Message #119 received at 775689@bugs.debian.org (full text, mbox, reply):

From: arv <arvid.evans@gmail.com>

To: 775689@bugs.debian.org

Subject: Re: Bug#775689: Do NOT use unetbootin for Debian CD images

Date: Fri, 28 Jul 2017 10:06:54 -0600

On Sun, 22 May 2016 04:50:07 -0700 Geza Kovacs <geza0kovacs@gmail.com>
wrote:
> Hi I'm the maintainer of unetbootin, I just stumbled upon this bug
report,
> sorry you have been having issues. The underlying issue appears to be
that
> some of Debian's ISO files violate the Joilet standard - the standard
does
> not permit filenames exceeding 64 characters in length, as you can
see at
> https://en.wikipedia.org/wiki/Joliet_(file_system) . Hence any tool
for
> processing ISO files which follows the Joilet standard, like 7-zip
(which
> is used by unetbootin), will have undefined behavior when dealing
with such
> files (in the case of 7-zip it truncates the filenames to 64
characters).
> The upstream report for 7-zip is at
> https://sourceforge.net/p/sevenzip/bugs/1055/ but unetbootin is not
the
> only tool dealing with ISO files that relies on 7-zip (or other tools
that
> expect Joilet-compliant ISO files), so a solution might be to just
respect
> the 64-character limit for filenames in ISO files.

FINALLY...a clear answer on the unetbootin problem in Debian Jessie.
Earlier bug report comments are less than helpful because they do not 
point to a viable graphical replacement for unetbootin.  While they do 
mention use of dd as a replacement this does not address the need for 
graphical or desktop-compatible solution.  Real need is to either fix 
the unetbootin problem (make Debian conform to standards) or to provide
an alternative graphical tool to make .iso bootable USB Pen-drive 
images.
An alternative solution might be to restore ability of K3B to write to 
USB pen-drives.  This also went away with Debian Jessie release.

Message #124 received at 775689-done@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 534107-done@bugs.debian.org,551301-done@bugs.debian.org,566218-done@bugs.debian.org,566219-done@bugs.debian.org,575603-done@bugs.debian.org,594009-done@bugs.debian.org,596386-done@bugs.debian.org,607514-done@bugs.debian.org,624192-done@bugs.debian.org,624279-done@bugs.debian.org,640582-done@bugs.debian.org,646793-done@bugs.debian.org,650635-done@bugs.debian.org,657539-done@bugs.debian.org,657895-done@bugs.debian.org,675815-done@bugs.debian.org,681986-done@bugs.debian.org,689723-done@bugs.debian.org,690994-done@bugs.debian.org,696401-done@bugs.debian.org,696617-done@bugs.debian.org,697920-done@bugs.debian.org,698366-done@bugs.debian.org,706027-done@bugs.debian.org,712902-done@bugs.debian.org,745469-done@bugs.debian.org,747047-done@bugs.debian.org,769816-done@bugs.debian.org,775689-done@bugs.debian.org,813118-done@bugs.debian.org,820884-done@bugs.debian.org,846018-done@bugs.debian.org,872124-done@bugs.debian.org,875218-done@bugs.debian.org,

Cc: unetbootin@packages.debian.org, unetbootin@packages.qa.debian.org

Subject: Bug#870974: Removed package(s) from unstable

Date: Sun, 10 Sep 2017 15:57:02 +0000

Version: 608-1+rm

Dear submitter,

as the package unetbootin has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870974

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

Send a report that this bug log contains spam.