linstaller 6.0.0 now in master.
Merge branch 'master' into debian
linstaller 6.0.0 now in debian(master).
6.0.0-1
Use old, ugly way to add new partitions. The method we used since 5.1 has been a bit buggy.
Merge branch 'master' into debian
6.0.1-1
Try not to 'crash' when rebooting.
Merge branch 'master' into debian
6.0.2-1
services/glade: on update_and_show_notification(), properly catch eventual Exceptions.

We do not want to have the installer taken down by a simple notification, do we?
Thanks to Filip Danilovic for the bug report.
linstaller.py: do not force garbage collection anymore (at least for now)

This should resolve some issues with missing objects during the installation,
at the expense of a slightly higher memory usage.
modules/partdisks/front: fixed display issue.

With the latest GTK+ (~3.12) the entire installer window was too large because
of the text of every button in partdisks's toolbar.
A workaround has been added that fixes this issue.
Also, partdisks.glade now requires GTK+3.10 or higher.
modules/bootloader.inst: ensure we skip eventual SD cards when installing to MBR.

In some cases grub-mkdevicemap will put the SD card ahead of the internal disks,
and linstaller will then get fooled and try to install the bootloader there.
modules/userhost/inst: cli: ensure we actually start the progressbar, otherwise we will enter in a crash loop...

The missing progress.start() call after the progressbar creation made the progressbar crash
when update() is called.
This commit also ensures that the new progressbar created to replace the crashed one is actually
started, otherwise we will end in a crash loop.
Thanks to Filip Danilovic for the bug report.
modules/bootloader: inst: ensure we take the realpath of the device.

When fixing the SD card bug (see commit 610038d6ff2327d151b39c4ed3c5dc5ca54ad69d),
I forgot the os.path.realpath call to get the real device (grub-mkdevicemap only
shows the links in /dev/disk).
modules/partdisks: front/glade: on manual_frame_creator() prefer device objects in self.changed.

If the device is already in self.changed, we should take the objects directly from it, otherwise
bad things will happen when committing things (e.g. new partitions will not be physically created).
I fighted with this for months, and in the end it's only a three line fix. Wow.
modules/partdisks/front/glade: automatic: actually delete the disk after the user has pressed Yes.

I really do not know why the delete calls were done before the confirmation dialog,
maybe I was drunk too much that day.
To test this 'fix' I trashed my entire partition table (and an entire day). Karma.

(Man, I <3 testdisk)
modules/partdisks/front/glade: automatic_calc(): when setting up self.changed in order to switch to the manual summary scene, properly store the device and disk objects.

self.changed[diskpath]["obj"] was a Disk object, instead of a Device. Disks should be associated with the "disk" key.
This broke the automatic mode after 77371d5fcd043fd7685f486795027796105519d5, as manual_frame_creator() now expects a Device object (to retrieve its path).
This commit should also fix the intermittent issues with the automatic partitioner.
Thanks again to Filip Danilovic for the bug report.
glade service: properly catch eventual pynotify exceptions.

It's better to have non-working notifications than that infamous alcohol-powered crash dialog!
Thanks again to Filip Danilovic for the bug report.