** Branch linked: lp:ubiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/188976
Title:
ubiquity crashed with OSError in copy_all()
To manage notifications about this bug go to:
This bug was fixed in the package ubiquity - 2.9.19
---
ubiquity (2.9.19) precise; urgency=low
* Install pixmaps/windows_square.png in ubiquity-frontend-gtk.
* Make it possible to run the test suite against installed packages, and
add a DEP-8 control file for this.
*
Encountered this on Linux Mint. The installer fatally crashed without
even leaving the option to use the automatic reporting tool. Manually
doing rm -rf /target/usr/local/share/* allows the installer to
complete, because only removing the man directory makes the installer
create a symlink and it
This problem affects Linux Mint, Kubuntu and Ubuntu. I have had the
same problem on all three flavors. I have been using the manual
partitioning.
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/188976
You received this bug notification because you are a member of
Crash log from /var/log/installer/debug:
File /usr/share/ubiquity/install.py, line 2566, in module
install.run()
File /usr/share/ubiquity/install.py, line 353, in run
self.copy_all()
File /usr/share/ubiquity/install.py, line 741, in copy_all
os.unlink(targetpath)
OSError: [Errno
There's further traffic on bug 573220 that I posted but can't properly
file as a dupe of this one because of some internal launchpad silliness
as near as I can tell.
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/188976
You received this bug notification because
I had /usr/local symlinked to /local/usr/local (on a different disk from /).
I guess the installer had trouble because / is mounted as /target, and there is
no /local.
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/188976
You received this bug notification
depending on what the first this means, this bug is potentially still
viable as of 10.4 release / Lucid Lynx
I just logged bug 573220 (which I can't flag as dupe right now because
of it's dupe bug 573218 that's a result of impatient clicking and is
unable to be accessed (with OOPS-1582B2194 )).
Installing Mythbuntu 10.4 beta1 over Ubuntu 9.10 after contaminating
original O/S with Lucid Lynx files.
In trying to preserve the original user files, I re-used the / partition
without formatting it and re-used the swap partition. The other
partition on the disk and the one on another drive were
Can this be confirmed as the cause of this error? Has anyone used
different partitioners to see if the bug is repeatable? I'm marking
this incomplete for now, because it seems like we need a little more
info to proceed.
** Changed in: ubiquity (Ubuntu)
Status: New = Incomplete
--
I know what you did, HughDaniel: You tried to partition your drive by
not only making their mount points high-level directories but also
mounting other partitions as their subdirectories (also known as tree-
partitioning). Ubiquity cannot handle this, and so the OSError will
result.
--
ubiquity
As Bug #512634 is marked as duplicate of this one I add this comment here: I
faced the problem of regularly crashing installation attempts, too. After some
web search I found a comment that this problem was related with the chosen file
systems. After a new try I can confirm, that while crashing
I'm got the problem while installing Ubuntu 9.10 on the disk with old
partition /home.
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/188976
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
OK now, there is no doubt now - in the manual partitioning mode, If
there is a (dead) symlink named 'opt' onte partition that is supposed to
be the root partition of the new installations, ubuquitty fails with the
errors in the last comment.
I remoded the link and installation went just fine.
--
I can confirm that this issue still exists in the Installer of Ubuntu 9.10 , on
an AMD64 system.
I tried to install on an already existing 9.10 installation, I used that
partition as the root partition for my
installation attempt.
Looks like it does not like the already existing /opt folder in
I believe we fixed this in the final Ubuntu 9.10 release CDs. I would
greatly appreciate anyone who is still getting this error with the CDs
that will be released today to run `sudo apport-collect 188976` after
the installer crashes.
If this bug is fixed for you, please report back as well.
ust got the problem while installing Ubuntu 9.10. Not specifying
/usr/local got me past this bug (I could specify an existing /home
without any problem).
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/188976
You received this bug notification because you are a
This bug affect me also with Mythbuntu 9.10 (RC).
So my original bug #458980 get closed as duplicate of this one.
The question if for me, did I really hit a bug that is so old (reported
2008-02-04)?
Or more important for me, what can i do to workaround this bug? Since it let me
not install
The workaround that got me through was simply to not specify the
offending partition during the install then to manually add it to
/etc/fstab once I'd finished.
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/188976
You received this bug notification because you
Thanks to Tony Green and StealthBanana, had the same problem on
installing a 9.04 keeping a Slack's /usr/local (ot to be formatted). No
problem with other partitions, /tmp, /var, /home, seems to be relative
to the second level directory structure as said StealthBanana.
--
ubiquity crashed with
This bug is in the golden Ubuntu 9.04, very bad.
I suspect the bug is related to having more then a few partitions, or partitions
where the installer did not expect them. This prevents using Ubuntu for
serious installs (servers, robust work stations, etc.).
FYI I have now seen this bug in both
Duh, I should give you the set of partitions that caused todays failure.
This is a test system, so it's simple. One 250GB SATA drive, and in
todays case the install was off of USB key, but I have seen the same off
of CD-ROM.
Here are the partitions I made that caused it to fail:
Partition
Still ongoing in 9.04 beta. Problem only with /usr/local. Other kept
partitions fine, /home and nonstandard /mp3 and /data , just the second
level directory structure of /usr/local it seems. /etc/fstab redited
and working fine.
--
ubiquity crashed with OSError in copy_all()
** Changed in: ubiquity (Ubuntu)
Status: Incomplete = Confirmed
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/188976
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Successfully installed by not telling the installer about the partitions
I wanted to keep. So then I had to re-edit /etc/fstab to put them back
and delete all the stuff the installer put in the directories I was
going to mount over.
Luckily I know Unix well; this would have defeated a lot of
I've tried several times and the installer crashes every time, leaving me with
an unusable system. It makes no difference if I clean out the install
partitions before installing, or get ubiquity to clear them or even leave them
with old files in them.
The last message in /var/log/syslog, which
I have just hit this problem using the release version of Kubuntu.
From the comment above about a non-empty filesystem, I have looked at
the partitions and it appears that despite telling the installer to
format them, it has failed to do so, as there are many old files still
there.
I noticed
** Visibility changed to: Public
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/188976
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.ubuntu.com
Can you please retry with the latest daily live CD:
http://cdimage.ubuntu.com/daily-live/current/
I believe the problem you were seeing was caused by the code that would
normally clear such conflicting files off the partition being
temporarily disabled while a serious bug was fixed. Please
29 matches
Mail list logo
