I wasn't able to reproduce this bug, but based on the empty syslinux.cfg file I believe it's probably caused by the fact that I remove syslinux.cfg and recreate it immediately afterwards, without doing a sync in between; Linux tends to have issues with that.
Anyhow, I've made a new release 424 which does a sync after removing a file, so hopefully that will fix it. I've uploaded it to mentors at http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=unetbootin could you verify that this fixes the issue? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
