lubuntu yakkety alternate iso doesn't succeed with unetbootin

[mvsfrasson]

Hi

Problem: create bootable flashdrive with UNetbootin and lubuntu-16.10-alternate-i386.iso fails.

I intend to install with lubuntu yakkety alternate iso image, in a friend's netbook without dvd reader, probably low in ram.

In my laptop, I downloaded `lubuntu-16.10-alternate-i386.iso' file. I did verify md5sum and it matches the hashes provided at http://cdimage.ubuntu.com/lubuntu/releases/16.10/release/MD5SUMS

Trying to make a bootable flashdrive, I used UNetbootin. This image never succeeds after 26%, sometimes 25% (hours waiting, looks like stuck).
I don't remember it always stops at te same files, (now I see stuck at pool/main/b/bind9/libbind9-140_9.10.3.dfs), but I do remember that in the first times, it used to freeze at 26%, after some tries, always at 25%.

Then I did the same lubuntu-16.10-desktop-i386.iso, (checked md5sum as well). I even installed the desktop image on the same flashdrive, same hardware, etc, even three times, it always succeeds.

Switching to usb-creator-gtk, the alternate image (same flashdrive) finally succeeds (I did this twice, just to be sure)!

However, no luck with UNetbootin and alternate iso.

[mvsfrasson (mvsfrasson)]

Work-around: Use usb-creator-gtk instead of unetbooin.

[mvsfrasson (mvsfrasson)]

Compiled from source new UNetbootin 625 from their website, reproduced bug. Changed flashdisk, reproduced the bug.

I also reported to UNetbootin:
https://github.com/unetbootin/unetbootin/issues/95

[mvsfrasson (mvsfrasson)]

I realized that lubuntu-16.10-desktop-i386.iso has just 317 files in I use UNetbootin, while alternate iso image has 1894. Bug happens at file 504 of 1894.

A guess. Maybe some filelist of length 512 inside UNetbootin gets full with 504 files and some folders.

[Simon Quigley (tsimonq2)]

The maintenance of the Lubuntu Software Center is now limited to critical bugfixes on Lubuntu 16.04 only. It has been removed from the archive and does not ship in Lubuntu 17.10 and on. Therefore, I am closing this bug as Won't Fix.