[Bug 1060893] Re: Ubuntu messes up Kubuntu installation

Zwulf zwulf at rocketmail.com
Wed Oct 3 15:49:18 UTC 2012


I can not boot the affected system because grub does not recognize it,
means that it is not bootable anymore. I do not want to install ubuntu-
desktop and kubuntu-desktop on one system - the menu gets huge and
confusing by installing all standard apps from KDE and GNOME at the same
time.

Atm I work with GNOME because Kubuntu is not bootable anymore (but it
was before), as already mentioned. I attached files from
"/@/var/log/installer/*" from Kubuntu (I hope I got you right with
"affected system"). After installation of the first system I get a
normal "/" folder with all subfolders like "/boot", "/usr", "/var",
"/dev", "/etc", "/home", etc. After installing the second Quantal system
ubiquity moves all that folders from the first system into "@" and
"@home" on its partition. As a result the first system is not bootable
and not even recognized by grub because there is no "initrd.img" in
/boot, because /boot is now a subfolder of "@" which it was not before
installing the second Ubuntu flavor. I really wonder for what purpose
ubiquity does this. I even wonder why ubiquity touches other partitions
outside the actual install partition at all. I always do manual
partitioning in ubiquity and did not set any mountpoints on other
partitions.

Now that I use standard Ubuntu (also on btrfs) which made Kubuntu not
bootable anymore the actual system looks normal - there is no
"@"-folder. The "@" folder is definitely created by ubiquity - it was
not there before installing the second system (standard Ubuntu) -
Kubuntu was perfectly usable.

I tried to move all subfolders in "@" back to root folder, but most
files from "/@/dev" are not moveable, even with root-privileges.

History of what I did:
At first I did the same thing the other way round, means installing Ubuntu in /dev/sda6, then Kubuntu to /dev/sda7 - resulting in the same strange moving of all files and folders in "/" to "@" - resulting in standard Ubuntu not bootable with "@"-folder, not recognized by grub. From KDE I created another USB-stick with standard Ubuntu, installed it in /dev/sda6 (the actual system) - and now KDE is not bootable because of the "@"-folder. That is the actual situation as I mentioned it in the bug report.

I am quite sure, this behaviour is reproducible on any system. Try to
install Ubuntu in one partition, then another install on another
partition on the same hd, both btrfs. It is probably reproducible on a
virtual machine (I will try that now and let you know the result).

** Attachment added: "installer.tar.gz"
   https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1060893/+attachment/3368642/+files/installer.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1060893

Title:
  Ubuntu messes up Kubuntu installation

Status in “ubiquity” package in Ubuntu:
  Incomplete

Bug description:
  When installing Ubuntu 12.10 next to Kubuntu 12.10 it messes up whole
  Kubuntu system by moving whole system root to a directory named "@"
  and home folder to "@home", /var/lib remains as only directory on root
  partition but it is empty (no hidden files). When installing Kubuntu
  next to Ubuntu the same problem occurs. Attached file is created by
  ubiquity in /ubiquity-apt-clone. I want to use both, Kubuntu and
  Ubuntu, but that is not possible because many files can not be moved
  back to system root on the partition (mostly in /dev). That is really
  disturbing.

  I'm using btrfs as file system on both partitions. Both partitions are
  on the same disk. /dev/sda1 is ntfs, /dev/sda5 is swap, /dev/sda6 is
  Ubuntu and /dev/sda7 Kubuntu. I want the freedom to use both, not
  being restricted by Ubuntu to be able to use only one flavor of
  Ubuntu. If it was Fedora on the partition I could understand that
  somehow but another Ubuntu flavor? Why? That always worked, why was
  Ubiquity changed to do such a mess?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1060893/+subscriptions




More information about the foundations-bugs mailing list