Public bug reported:
Binary package hint: syslinux
If syslinux is used on an image with mtools 4.0 as shipped with Ubuntu
9.10, it fails to install itself into the image, and corrupts the image.
A simple test can reproduce this behavior.
Expected Behavior:
- syslinux properly writes a header to the image
Current Behavior
- The image is corrupted in such a way that is causes ls to report the
filesize is 2.0 TiB
How to Reproduce:
1. Create a empty VFAT image
2. Run syslinux on it
Console log:
mcasadev...@daybreak:~/tmp$ mkdosfs -C test.img 10000
mkdosfs 3.0.3 (18 May 2009)
mcasadev...@daybreak:~/tmp$ ls -lah test.img
-rw-r--r-- 1 mcasadevall mcasadevall 9.8M 2009-11-12 00:32 test.img
mcasadev...@daybreak:~/tmp$ syslinux test.img
mcasadev...@daybreak:~/tmp$ ls -lah test.img
-rw-r--r-- 1 mcasadevall mcasadevall 2.0T 2009-11-12 00:32 test.img
ProblemType: Bug
Architecture: amd64
Date: Thu Nov 12 00:27:31 2009
DistroRelease: Ubuntu 9.10
Package: syslinux 2:3.63+dfsg-2ubuntu3
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48+ureadahead2-generic
SourcePackage: syslinux
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
(polkit-gnome-authentication-agent-1:3521): GLib-CRITICAL **:
g_once_init_leave: assertion `initialization_value != 0' failed
(chromium-browser:27680): Gdk-WARNING **: XID collision, trouble ahead
** Affects: syslinux (Ubuntu)
Importance: High
Status: New
** Tags: amd64 apport-bug
--
syslinux corrupts images when used with mtools 4.0
https://bugs.launchpad.net/bugs/481124
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
