Starting unetbootin brings up a message. UNetbootin must be run as root. Close it, and re-run using either: sudo /usr/bin/unetbootin or: su - -c '/usr/bin/unetbootin' Would be nicer having the opportunity to give root-password right away, and go ahead.
Assigning to maintainer now that our maintainers database has an entry for this package. Please assign back to bugsquad@mageia.org in case of a mistake from me.
CC: (none) => stormiAssignee: bugsquad => sander.lepik
Fixed in cauldron.
Status: NEW => RESOLVEDResolution: (none) => FIXED
It's also valid for Mageia 1, could you provide an update too ?
Status: RESOLVED => REOPENEDVersion: Cauldron => 1Resolution: FIXED => (none)
unetbootin-0-0.549.1.mga1 submitted into updates_testing, please test.
Assignee: sander.lepik => qa-bugs
Can this be made to work with Mageia, I see Mandriva is listed? It would be useful for testing ISO's when they arrive. I don't have a USB to test with at the moment but can confirm it updates fine and does now ask for root password when started. Testing i586.
isa dora are you able to test this please too.
Hardware: i586 => All
Works here as well at 64-bits, thx.
Hardware: All => i586
(In reply to comment #7) > Works here as well at 64-bits, thx. Did you test on cauldron or on mageia 1?
CC: (none) => sander.lepik
Tested at Mageia 1, do you want to have it tested in Cauldron as well?
Nop, just wanted to know if we can validate it for mageia 1. It seems we can.
I think we can do, yes. Thankyou isa dora. It would be useful though to add a Mageia option if it's just a configuration change. It seems Mageia can be used to add anything except Mageia! Advisory: -------------------- This minor update adds a root authentication prompt when starting. -------------------- Source RPM: unetbootin-0-0.549.1.mga1.src.rpm Could sysadmin please push from core/updates_testing to core/updates. Thankyou!
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugsHardware: i586 => All
Unvalidating the update. With a usb drive plugged in, the drop down button to select the drive is not showing any drives, on my i586 Mageia 1 install. The device notifier does detect the drive, and gives me the option of mounting the filesystem that is on it's one current partition.
Keywords: validated_update => (none)CC: (none) => davidwhodgins
CC: sysadmin-bugs => (none)
(In reply to comment #12) > Unvalidating the update. > > With a usb drive plugged in, the drop down button to select the drive is > not showing any drives, on my i586 Mageia 1 install. You need to have fat32 partition mounted. Did you? If not then nothing will appear.
I changed the filesystem from ntfs to fat32, and after mounting, unetbootin was able to copy the mageia 1 dvd files to the drive. I replied yes to all, for overwriting files, though I don't see why that was required. But, trying to boot from the drive failed with non-system disk. After copying the mbr to a file, and opening hexedit on it the code shows 00000000 FA B8 00 10 8E D0 BC 00 B0 B8 00 00 8E D8 8E C0 FB BE 00 7C BF 00 06 B9 ...................|.... 00000018 00 02 F3 A4 EA 21 06 00 00 BE BE 07 38 04 75 0B 83 C6 10 81 FE FE 07 75 .....!......8.u........u 00000030 F3 EB 16 B4 02 B0 01 BB 00 7C B2 80 8A 74 01 8B 4C 02 CD 13 EA 00 7C 00 .........|...t..L.....|. 00000048 00 EB FE followed by hex zeroes up to the disk signature.
(In reply to comment #14) > I changed the filesystem from ntfs to fat32, and after mounting, unetbootin > was able to copy the mageia 1 dvd files to the drive. I replied yes to all, > for overwriting files, though I don't see why that was required. > > But, trying to boot from the drive failed with non-system disk. I'm not sure if it's possible to make Mageia boot with Unetbootin. But you can try with the current Unetbootin. You can only unvalidate the update if it breaks something that was working before. If you look at the changes then you should see that it's quite hard to happen as there is no changes to Unetbootin itself.
There isn't much point in pushing an update, where one of the primary purposes of the package is broken, whether it's a regression or not. In the case, I've found the problem. Unetbootin is not calling syslinux. I see three alternatives to fix it. 1. Create a symlink, on installation ... ln -f /usr/bin/syslinux /usr/bin/ubnsylnx 2. Build and install ubnsylnx 3. Rebuild with the NOSTATIC option, so that it will call syslinux if ubnsylnx isn't found. This is based on looking at the code and ... # grep -e ubnsylnx -e syslinux strace.txt 8749 stat64("/media/HODGINS/boot/syslinux/syslinux.cfg", 0xa311a34) = -1 ENOENT (No such file or directory) 8749 lstat64("/media/HODGINS/boot/syslinux/syslinux.cfg", 0xbfb4a4b0) = -1 ENOENT (No such file or directory) 8749 stat64("/media/HODGINS/syslinux/syslinux.cfg", 0xa24bbf4) = -1 ENOENT (No such file or directory) 8749 lstat64("/media/HODGINS/syslinux/syslinux.cfg", 0xbfb4a4b0) = -1 ENOENT (No such file or directory) 8749 stat64("/media/HODGINS/syslinux.cfg", {st_mode=S_IFREG|0644, st_size=2543, ...}) = 0 8749 chmod("/media/HODGINS/syslinux.cfg", 0200) = 0 8749 unlink("/media/HODGINS/syslinux.cfg") = 0 9012 execve("/usr/bin/ubnsylnx", ["/usr/bin/ubnsylnx", "/dev/sdc1"], [/* 69 vars */]) = -1 ENOENT (No such file or directory) 8749 stat64("/media/HODGINS/syslinux.cfg", 0xa2910a4) = -1 ENOENT (No such file or directory) 8749 lstat64("/media/HODGINS/syslinux.cfg", 0xbfb4a4b0) = -1 ENOENT (No such file or directory) 8749 open("/media/HODGINS/syslinux.cfg", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE|O_CLOEXEC, 0666) = 9 The only way this would work for someone else would be if they've previously run syslinux on the vfat filesystem on the usb drive, or they have /usr/bin/ubnsylnx from somewhere else.
(In reply to comment #16) > There isn't much point in pushing an update, where one of the primary purposes > of the package is broken, whether it's a regression or not. > > In the case, I've found the problem. Unetbootin is not calling syslinux. > > 3. Rebuild with the NOSTATIC option, so that it will call syslinux > if ubnsylnx isn't found. unetbootin-0-0.549.2.mga1 has been rebuilt with NOSTATIC, please test. And there is also new version in cauldron which is now switched to tarball source release, could you test this one as well?
Testing complete using dsl on i586. Only minor item, is that the reboot button doesn't work. Probably best to just remove the button, although I don't consider that a blocker for the update. Regarding the cauldron version, it needs dependencies added for syslinux, and extlinux. The extlinux package needs to set /usr/sbin/extlinux as executable. I've only tested the cauldron version with a vfat partition.
Cauldron package is now rebuilt and requires extlinux (which was splitted from syslinux), please test again. Also, could someone please test updates_testing version on x86_64 so we could validate update again..
(In reply to comment #19) > Cauldron package is now rebuilt and requires extlinux (which was splitted from > syslinux), please test again. > > Also, could someone please test updates_testing version on x86_64 so we could > validate update again.. Tested from updates_testing, no issues.
Update validated. Please push unetbootin-0-0.549.2.mga1 from Core Updates Testing to Core Updates. According to depcheck, no extra dependency to link. Advisory: This minor update adds a root authentication prompt when starting.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
update pushed.
Status: REOPENED => RESOLVEDCC: (none) => dmorganecResolution: (none) => FIXED
(In reply to comment #20) > (In reply to comment #19) > > Cauldron package is now rebuilt and requires extlinux (which was splitted from > > syslinux), please test again. Uninstalled unetbootin, extlinux, syslinux. Installed unetbootin, and it did pull in extlinux and syslinux. Except for having to run "chmod u+x /usr/sbin/extlinux", unetbootin on cauldron is working with an ext2 filesystem on the usb drive.