Hope this doesn't confuse, but I have just performed the same exercise myself, and this is what worked for me:
Should I Remove the UNetbootin in the SM
sudo apt-get remove unetbootin
and then run sudo apt-get update, then run sudo apt-get update, then re-install?
My method was (and read all the way through before taking step by step):
Firstly, to try
Not the desired result. This triggered me to thinking there was a ppa to be added, so looked up sourceforge and launchpad, and then commenced as follows
Entered and so
At this point, the ppa is added, and we can look for a newer Unetbootin
Your Software Sources should appear as follows, all you need is the last line (I check Sources as well)
Your Package Manager should show as follows:
... and so we want 603.
Right-clicking shows this
...all greyed out except for the removal options. So we have to remove Unetbootin first.
Removing it shows what is left
We can then do the following, which is the usual Apply the changes and Install:
We now have Unetbootin 603 in place, or have we?
sudo apt-get update
... again, just as a precaution, but when I fired up Unetbootin got this warning
I say a warning, because OKing it still opened Unetbootin for me, but decided to cover all angles.
extlinux here is v4.05 and despite the description also supports NTFS and FAT32. It comes from syslinux family. There are more updated versions out there, but I would leave as is.
The updated versions are for Utopic Unicorn and Vivid Vervet (under development), so there might be conflicts.
Once the above is all completed, fire up Unetbootin
... and you should have the newest version on your block!
Note that with the above, more could have been done at Terminal, more could have been done with GUI - I just used both
BTW - for Kernel updating, see Nick's new article here
Edited add BTW
Edited by wizardfromoz, 18 December 2014 - 10:06 PM.