Marking as invalid in unetbootin (Ubuntu) since this relates to the
software itself not the packaging.
** Changed in: unetbootin (Ubuntu)
Status: New => Invalid
--
Intrepid netboot hangs on Acer Aspire One
https://bugs.launchpad.net/bugs/322001
You received this bug notification because y
ootin
Assignee: (unassigned) => Geza Kovacs (gezakovacs)
--
Intrepid netboot hangs on Acer Aspire One
https://bugs.launchpad.net/bugs/322001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Should be fixed as of package version 356 in karmic universe
repositories.
** Changed in: unetbootin (Ubuntu)
Status: New => Fix Released
--
Unetbootin does not work with GRUB2
https://bugs.launchpad.net/bugs/386862
You received this bug notification because you are a member of Ubuntu
Bug
Should be fixed as of package version 356 in karmic universe
repositories.
** Changed in: unetbootin (Ubuntu)
Status: Confirmed => Fix Released
--
[Karmic] vol_id not found
https://bugs.launchpad.net/bugs/376339
You received this bug notification because you are a member of Ubuntu
Bugs, w
Confirmed, working on it upstream.
** Changed in: unetbootin
Importance: Undecided => High
** Changed in: unetbootin
Status: New => In Progress
** Changed in: unetbootin
Assignee: (unassigned) => Geza Kovacs (gezakovacs)
--
Unetbootin does not work with GR
** Changed in: unetbootin
Importance: Undecided => High
** Changed in: unetbootin
Status: New => In Progress
** Changed in: unetbootin
Assignee: (unassigned) => Geza Kovacs (gezakovacs)
--
[Karmic] vol_id not found
https://bugs.launchpad.net/bugs/376339
You received
I've fixed this as of upstream release 356, Debian unstable should have
a package soon (which will fix this bug in the Ubuntu package once it's
imported into karmic).
** Changed in: unetbootin
Status: In Progress => Fix Released
--
[Karmic] vol_id not found
https://bugs.launchpad.net/bugs
I've fixed this as of upstream release 356, Debian unstable should have
a package soon (which will fix this bug in the Ubuntu package once it's
imported into karmic).
** Changed in: unetbootin
Status: In Progress => Fix Released
--
Unetbootin does not work with GRUB2
https://bugs.launchpa
/usr/bin/ubnsylnx isn't a file from Ubuntu; it's simply a copy of
/usr/bin/syslinux installed by the standalone i386-linux (not deb)
version of UNetbootin http://unetbootin.sourceforge.net/
http://launchpad.net/unetbootin since many distributions, including
Ubuntu, ship extremely outdated and buggy
Khaoz, that problem is probably because you put the Windows XP entry
inside the Debian Automagic Kernels section. Put it either before the
### BEGIN DEBIAN AUTOMAGIC KERNELS LIST or after the ### END DEBIAN
AUTOMAGIC KERNELS LIST and it should remain there after an update-grub.
If you have any othe
My /boot/grub/menu.lst in Ubuntu 7.10, which lists only Ubuntu 7.04 not
Windows under "Other OS", is attached
** Attachment added: "My /boot/grub/menu.lst in Ubuntu 7.10, which lists only
Ubuntu 7.04 not Windows under "Other OS""
http://launchpadlibrarian.net/9250535/menu.lst
--
Grub install
Public bug reported:
Binary package hint: grub-installer
I just installed Ubuntu 7.10 on a separate partition (/dev/sda8) on a
machine that already runs Ubuntu 7.04 on /dev/sda6 and Windows XP Media
Center Edition on /dev/sda1. However, the grub menu only shows Ubuntu
7.04 under the "Other OS" ca
Also, this bug breaks the grub-install command, as entering:
[EMAIL PROTECTED]:~$ sudo grub-install /dev/sda
returns:
/dev/sda does not have any corresponding BIOS drive.
While entering:
[EMAIL PROTECTED]:~$ sudo grub-install /dev/sde
returns:
/dev/sda8 does not have any corresponding BIOS d
Also, for some reason, when entering:
sudo grub-install '(hd0)'
The following error is returned:
/dev/sda8 does not have any corresponding BIOS drive.
However, given that (hd0) is supposed to be /dev/sda (first hard drive,
MBR), and /dev/sda8 is supposed to be (hd0,7), this appears to be a bug,
** Also affects: unetbootin
Importance: Undecided
Status: New
--
USB boot loops with "Initial menu has no LABEL entries"
https://bugs.launchpad.net/bugs/569603
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
ignee: (unassigned) => Geza Kovacs (gezakovacs)
--
USB boot loops with "Initial menu has no LABEL entries"
https://bugs.launchpad.net/bugs/569603
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
** Changed in: unetbootin (Ubuntu)
Assignee: Geza Kovacs (gezakovacs) => (unassigned)
** Changed in: unetbootin
Assignee: (unassigned) => Geza Kovacs (gezakovacs)
--
USB boot loops with "Initial menu has no LABEL entries"
https://bugs.launchpad.net/bugs/569603
You r
*** This bug is a duplicate of bug 373089 ***
https://bugs.launchpad.net/bugs/373089
This is actually an issue with 7-zip, as noted in
https://bugs.launchpad.net/unetbootin/+bug/373089 and
http://sourceforge.net/tracker/?func=detail&aid=2928072&group_id=14481&atid=114481
** Also affects: unet
That changelog is somewhat incomplete; various accessibility issues were
also fixed (accesskeys, see launchpad bug 371029, as well as
resizability for the interface). As I didn't introduce any additional
dependencies, and there were no major new features that could have
introduced regressions, I (u
Btw, I'm the upstream developer (and maintain that PPA you linked to).
Keep me updated on the MIA-debian-developer situation, if needed I'd be
perfectly happy to take over maintenance in debian... (I used to
maintain the CoffeeScript packaging, ie
http://piuparts.debian.org/sid/maintainer/g/gkov...
This was fixed a while ago, in release 625, which can be installed from
the official upstream PPA (
https://launchpad.net/~gezakovacs/+archive/ubuntu/ppa ).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
(the underlying reason is explained at
https://github.com/unetbootin/unetbootin/issues/66 - but again, I have
already fixed this in the latest upstream release and in the PPA, as of
version 625)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
actually checked the filesystem and found that
the filesystem.size file is missing, this should be marked invalid for
UNetbootin.
** Changed in: unetbootin (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: unetbootin (Ubuntu)
Assignee: (unassigned) => Geza Kovacs (gezakovacs
Based on https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/875519
it appears that the misleading error message Ubiquity is giving which
leads users to unmount /cdrom and get this error is "Can't unmount
/cdrom".
--
You received this bug notification because you are a member of Ubuntu
Bugs,
And observing
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/877032 the user
says the filesystem.size file is indeed there in the casper folder on
the filesystem in spite of getting this error, so yes, this indeed seems
to be users deciding to unmount the filesystem rather than UNetbootin
And I believe I now know what the scenario which is leading to this
error is. UNetbootin has an option to put the live environment (squashfs
and all) onto a hard drive partition (the hard drive install mode), so
that it can be booted in live mode. If a user has a single system
partition, puts the l
** Changed in: unetbootin (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/557388
Title:
Ubiquity crashes over recipe that leads to "Missing filesystem.siz
Hi I'm the upstream maintainer. No need to get trigger-happy. There is a
4-line fix to this, specifically add the QFileDialog::ReadOnly option to
the 4 occurrences of QFileDialog::getOpenFileName in
https://github.com/gkovacs/unetbootin/blob/master/src/unetbootin/unetbootin.cpp
. I'll update it soo
Hi I'm the upstream maintainer. No need to get trigger-happy. There is a
4-line fix to this, specifically add the QFileDialog::ReadOnly option to
the 4 occurrences of QFileDialog::getOpenFileName in
https://github.com/gkovacs/unetbootin/blob/master/src/unetbootin/unetbootin.cpp
. I'll update it soo
: New => Fix Released
** Changed in: unetbootin (Ubuntu)
Assignee: (unassigned) => Geza Kovacs (gezakovacs)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438236
Title:
The "Open
ovacs/unetbootin/commit/9dafdda9ad6765d27c62df52daa708db22835e3e
if you would like to cherry-pick it.
** Changed in: unetbootin (Ubuntu)
Status: New => Invalid
** Changed in: unetbootin (Ubuntu)
Assignee: (unassigned) => Geza Kovacs (gezakovacs)
--
You received this bug notification
*** This bug is a duplicate of bug 638845 ***
https://bugs.launchpad.net/bugs/638845
The issue is that for whatever reason Ubuntu defaults Qt applications
run as root to that style. You can fix the issue by installing the
qt4-qtconfig package, then running "gksudo qtconfig-qt4" and selecting
t
Hi, do you still encounter the same issue with the current release,
version 603? (It's in the PPA at
https://launchpad.net/~gezakovacs/+archive/ppa or alternatively as a
standalone binary at http://unetbootin.sourceforge.net/ )
--
You received this bug notification because you are a member of Ubu
note for reference that the correct command would have been:
wget http://unetbootin.sourceforge.net/unetbootin-linux-latest
which works fine for me. but no this doesn't seem to be a bug or a
security vulnerability
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
There do actually exist high-resolution versions; for example,
https://github.com/gkovacs/unetbootin/raw/master/src/unetbootin/unetbootin_512.png
; unfortunately the Debian packaging only ships a 32x32 xpm version of
the icon.
--
You received this bug notification because you are a member of Ubun
I assume you're trying to create an Ubuntu 13.04 iso and it isn't
booting? I'd suggest trying the latest release, 584, which fixed a few
bugs related to that, which you can find on the website at
http://unetbootin.sourceforge.net/ . There's even a PPA at
http://launchpad.net/~gezakovacs/+archive/pp
Sounds like it might be an issue with gksudo. UNetbootin doesn't
implement that part. Do you encounter the same issue when launching,
say, synaptic? Does "gksudo unetbootin" work? how about "sudo
unetbootin"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ah just saw your comment about sudo working. Yes, seems like an issue
with gksudo then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195061
Title:
Unetbootin asks for Administrative Password, pass
Not actually a unetbootin issue (it's an issue with gksudo), but see
https://bugs.launchpad.net/ubuntu/+source/unetbootin/+bug/1195061 for a
description of the solution
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
The issue is that for whatever reason Ubuntu defaults Qt applications
run as root to that style. You can fix the issue by installing the
qtconfig-qt4 package, then running "gksudo qtconfig-qt4" and selecting
the GTK theme instead. Might want to file a bug against Ubuntu.
--
You received this bug
Sorry, package name is actually qt4-qtconfig. Command is still "gksudo
qtconfig-qt4"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/638845
Title:
No native controls
To manage notifications about thi
An official icon has been added as of the latest UNetbootin release
(506).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/557045
Title:
UNetbootin has no icon in Xubuntu Lucid System menu
--
ubuntu
It appears that extlinux was moved out of the syslinux package and into
a separate package called extlinux as of maverick. The issue is that an
extlinux dependency wasn't added to the unetbootin package to reflect
this. Hence, this bug should actually affect the versions of unetbootin
in the maveri
@dEUS101: the issue of the 2 udeb files having the wrong names
(specifically, being truncated to 64 characters) is because 7-zip, which
is used by UNetbootin for extracting iso files, doesn't support the
RockRidge extensions which are used by the Ubuntu alternate iso for
having 64+ characters in fi
@Andrew Henry: the issue is that some udeb files in the Ubuntu alternate
iso have more than 64-character filenames, but unfortunately they are
truncated to 64 characters (and hence can't be found by the installer)
because 7-zip, which is used by UNetbootin for extracting iso files,
doesn't support
d.
** Changed in: unetbootin
Importance: Undecided => Medium
** Changed in: unetbootin
Status: New => Confirmed
** Changed in: unetbootin
Assignee: (unassigned) => Geza Kovacs (gezakovacs)
--
Installing Ubuntu 10.10 alternate gives Cd-rom related errors
https://bugs.launchpad.ne
Is there anything else that needs to be done before this fix can be
moved from lucid-proposed to lucid-updates? The SRU page doesn't seem to
indicate anything else after verifications, and if at all possible I'd
like to avoid having a huge influx of bug reports and negative reviews
from lucid users
Nevermind, I just noticed that there's a mandatory 7-day waiting period
for SRUs. Since this probably won't get an exception, I've put a notice
on the UNetbootin home page warning users not to use the lucid package
so hopefully that will take care of most of the unnecessary duplicate
bug reports.
/commit/feab255c7c67b9663092be2420fb69a1fc32d446#diff-1
** Changed in: unetbootin
Status: Confirmed => Fix Committed
** Changed in: unetbootin
Assignee: (unassigned) => Geza Kovacs (gezakovacs)
--
Cannot boot newer kernels (Ubuntu 10.10 alpha3): "No init found"
https://bu
Fixed released as part of UNetbootin 490
** Changed in: unetbootin
Status: Fix Committed => Fix Released
--
Cannot boot newer kernels (Ubuntu 10.10 alpha3): "No init found"
https://bugs.launchpad.net/bugs/615285
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Branch linked: lp:~gezakovacs/ubuntu/maverick/unetbootin/fix-10.10
-desktop-iso-loading
--
Cannot boot newer kernels (Ubuntu 10.10 alpha3): "No init found"
https://bugs.launchpad.net/bugs/615285
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
51 matches
Mail list logo
