[SOLVED] Mint 13 KDE 64-bit Installer crashes

ghoultek · 09-02-2012, 01:34 PM

There is an issue with the KDE installer where it will fail if the user chooses to do manual partition setup/selection. The issue is in the PartitionModel.py script. During one of several install attempts it produced the following error message:

Code:

Traceback (most recent call last):
  File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/PartitionModel.py", line 100, in parent
    parentItem = childItem.parent()
AttributeError: 'list' object has no attribute 'parent'

There are many people who are encountering this problem but I've yet to find a fix or workaround. I was wondering if anyone at LQ might have a workaround or know how to fix the issue so that the install can complete.

FYI,
I'm attempting to install Mint 13 KDE 64 bit into a 30GB partition (/dev/sda7).
sda1 = Mint 13 Cinnamon 64bit
sda5 = Mint 13 Mate 64bit
sda6 = Mint 13 XFCE 64bit
sda7 = **was for KDE**
sda8 = /home for all linux installs
sda9 = swap

sda1 is the only primary partition
sda5-9 are logical drives
All partitions are 30GB with the exception of the swap being 8GB (rarely used since I have 8GB of RAM).

Only the KDE install fails (from USB keys and DVDs). Prior Linx Mint, Ubuntu, and Arch Linux versions installed without a problem.

andrewthomas · 09-03-2012, 07:57 AM

manual partitioning in installer crashes

https://bugs.launchpad.net/ubuntu/+s...y/+bug/1038522

Could you please add any additional information to the above bug report and subscribe to it?

By the way, is there a reason why you choose to have four different installs as opposed to having one and selecting which desktop environment that you wish to use from the log-in screen?

ghoultek · 09-03-2012, 11:52 AM

As requested I added my info. to the bug thread and subscribed to it. As noted in my bug thread comments, the issue is wide spread affecting many people. A google search for "PartitionModel.py crash" or "PartitionModel.py fails" will reveal the large number of other people encountered the installer bug.

I'm trying out different distros. and desktop environments while learning Linux. I'm still a newbie (currently posting from Mint 13 Mate 64bit). Each distro./desktop environment has their own idiosyncrosies. I'll learn how stuff works, what I like and don't like, and tailor my environment to my tastes. Also, I would like to contribute.

A more detailed explanation of why I have separate distro. installs can be found here --> http://www.linuxquestions.org/questi...2/#post4771629.

andrewthomas · 09-09-2012, 12:37 PM

Did the md5 of your download match?

Code:

[lxde@slack-asus ~]$ md5sum /media/storage/distro/linuxmint-13-kde-dvd-64bit.iso 
5cc25450a0b401b939f6e274c4fdb186  /media/storage/distro/linuxmint-13-kde-dvd-64bit.iso

I had a spare partition that I was about to install the latest version of Slackware to that I used to install the above KDE mint iso to.

It worked just fine.

ghoultek · 09-10-2012, 02:02 AM

Yes the ISO file checks out fine via MD5 but the install fails. I tried installing via USB key and several DVDs. Did you attempt to manually partition the drive from within the installer? The installer bug seems to be pretty well known. I've installed multiple versions of Linux Mint 11.04 and 13 without any problems, with the exception being Mint 13 KDE 64bit.

andrewthomas · 09-10-2012, 04:18 PM

Quote:

Originally Posted by ghoultek

Did you attempt to manually partition the drive from within the installer?

Yes. I didn't create any new partitions, but I chose to install to an existing ext4 partition.

ghoultek · 09-11-2012, 12:14 PM

During my trips through the installer I picked the manual partition option. I didn't need to create a new partition either since I had already setup the partitions from within Mint 13 Cinnamon 64bit. I just needed to select the partitions for Mint 13 KDE's /root, /home, and swap. Grub was installed during the Mint 13 Cinnamon install.

I've already tried several DVDs, different burning software, different DVD burner drives, and several USB keys. Any ideas on how I can get the install to complete?

ghoultek · 09-12-2012, 01:06 AM

Ok this is quite frustrating but I figured out how to get around the installer bug, which will seem quite stupid.

When I attempted to do the installs I would pick the manual partition option, and only select the partitions for root, /home, and swap. The fix is:
1 - Use a partitioning program (the one in the KDE 64bit installer or another like gParted) to create the desired partitions and format them.
2 - Reboot the PC and boot from the install CD, DVD, or USB key.
3 - Select the manual option.
4 - Select the previously created partition for root, /home, and the others except DO NOT CLICK ON THE SWAP PARTITION AND THEN CLICK THE CHANGE BUTTON.
5 - Select the desired location for the Grub boot loader.
6 - Click the Install or Continue button on the bottom right for the installation to proceed.

On the hard drive that I use for my Linux installs, there is only one partition marked as swap (the others are marked ext4) so the installer will figured it out. For some odd reason it chokes it you attempt to actually specify the swap partition during the manual partition setup/selection process.

FYI,
I was able to install Kubuntu 12.04 64bit from USB key using the same fix as above.

andrewthomas · 09-12-2012, 05:19 PM

Quote:

Originally Posted by ghoultek

For some odd reason it chokes it you attempt to actually specify the swap partition during the manual partition setup/selection process.

OK, I never tell it about my swap partition, for fear of a new UUID being created during a format and probably why I didn't have a problem with my test either.

ghoultek · 09-14-2012, 10:55 AM

Off-topic: Is the UUID stored in the master boot record?

andrewthomas · 09-17-2012, 07:02 PM

I don't think so. Not in the partition table at least.

Code:

sfdisk -d /dev/sda > /home/lxde/sda.partition.table

Code:

# partition table of /dev/sda
unit: sectors

/dev/sda1 : start=     2048, size=125829120, Id=83
/dev/sda2 : start=125837206, size=3781185642, Id= 5
/dev/sda3 : start=        0, size=        0, Id= 0
/dev/sda4 : start=        0, size=        0, Id= 0
/dev/sda5 : start=125837208, size=125829224, Id=83
/dev/sda6 : start=251668480, size=125829120, Id=83
/dev/sda7 : start=377499648, size=125829120, Id=83
/dev/sda8 : start=503330816, size=125829120, Id=83
/dev/sda9 : start=629161984, size= 66584576, Id=83
/dev/sda10: start=754993152, size= 41943040, Id=83
/dev/sda11: start=796938240, size=125829120, Id=83
/dev/sda12: start=922769408, size=2661423104, Id=83
/dev/sda13: start=3584194560, size=312342528, Id=83
/dev/sda14: start=3896539136, size= 10483712, Id=82

ghoultek · 09-19-2012, 10:27 PM

Thanks Andrew. I was just curious about the UUID. I suspect it may be written in a known location in the partition itself.

andrewthomas · 09-20-2012, 06:40 PM

Quote:

Originally Posted by ghoultek

Thanks Andrew. I was just curious about the UUID. I suspect it may be written in a known location in the partition itself.

I agree. tune2fs can alter it and libblkid can read it. I am just unclear exactly where it is.