[karmic-alpha-2] gparted is accidentally installed by ubiquity

[Propagation of Sound]

Binary package hint: gparted

On a clean install of Karmic Alpha 2, Gparted is installed 0.4.5 is installed by default.
However, it does not appear in System->Administration
Going into Add/Remove programs shows it is installed, and it works fine from the command line

ProblemType: Bug
Architecture: i386
Date: Thu Jun 18 11:44:31 2009
DistroRelease: Ubuntu 9.10
Package: gparted 0.4.5-2
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
SourcePackage: gparted
Uname: Linux 2.6.30-8-generic i686

[David Stansby (dstansby-deactivatedaccount)]

As far as I know I don't think gparted is part of the default install in ubuntu (though is still present on the livecd) Once installation has finished I think gparted is meant to be uninstalled, but I might be wrong here.

[Propagation of Sound (propagationofsound)]

I know Gparted is installed by default in Jaunty. So unless it was removed it must still be there. And gparted is installed by default in karmic alpha 2 because when I run it from the command line, it starts.

The problem here is that it does not appear by default in the System->Administration folder and when it is reinstalled, it does not bear the correct name. Even if it wasn't supposed to be installed by default, then installing should give it the right name on the menu at least!

[David Stansby (dstansby-deactivatedaccount)]

Hmm, strange. My jaunty install did not have gparted installed and hence I had to install it manually. I'm not sure about the name, though I suspect that gparted is the correct name.

[David Stansby (dstansby-deactivatedaccount)]

Gparted is not meant to be installed at all by default. Either this is a problem with ubiquity or is new intended behavior in karmic. Either way, this has nothing to do with gparted

[Propagation of Sound (propagationofsound)]

I'm not sure whether this is a ubiquity bug because it has not been proven that it was ubiquity that put it there. If you assume that the name change and the default install are both the same bug, then it can't be ubiquity that caused this bug

[David Stansby (dstansby-deactivatedaccount)]

Gparted is present on the liveCD, but is not present on the default install. Either ubiquity has accidentally installed gparted, or this was a concious decision taken by the devs to have gparted part of the default install. Either way, it isn't gparted's fault.

[Nathan Dorfman (ndorf)]

Hi,

After a fresh install of Karmic Alpha 2, I've noticed a bunch of packages 'left behind' by the installer. These packages were *not* present on a second machine, which is running karmic but was upgraded twice from an intrepid install.

Looking at /var/log/apt on both machines, it seems that intrepid's installer removed all of these packages, but the karmic one did not.

On the intrepid->jaunty->karmic upgraded box, the log began with the removal of these packages (2009-04-01 was the installation date):

--------------------------------------------------
Log ended: 2008-10-29 23:17:10

Log started: 2009-04-01 04:37:31
Log ended: 2009-04-01 04:37:31

Log started: 2009-04-01 04:40:44
Log ended: 2009-04-01 04:40:44

Log started: 2009-04-01 04:41:25
(Reading database ... 102341 files and directories currently installed.)
Removing lupin-casper ...
Removing casper ...
Purging configuration files for casper ...
Removing gparted ...
Purging configuration files for gparted ...
....
Removing ubiquity ...
Purging configuration files for ubiquity ...
Removing ubiquity-frontend-gtk ...
....
--------------------------------------------------

By contrast, such a step is missing from the log on the freshly installed karmic system, and all of the above and more are installed on it. This seems clearly wrong, in particular as regards Ubiquity, whose own package description states:

 Installing this package on a normal system is unlikely to be useful.

[David Stansby (dstansby-deactivatedaccount)]

I think this has been fixed now in lucid.