Dapper installation notes/Stuff that needs fixing

[Dane Mutters]

On Tuesday 14 February 2006 01:51 pm, Duncan Lithgow wrote:
> I started a similar list as Dane so here's mine...

	Cool! :-)

>
> Checking CD-ROM integrity:
>     The height of the window is too small, so whenever longer files are
> checked the height changes, and then back again. This gives an annoying
> flickering appearance on my 19" screen.
>     Upon restarting from CD after the integrity check, instead of going
> back to the main menu it goes to "[!!] Configuring cdrom-checker-menu"
> as if I have asked to check the CD again. Selecting 'no' restarts the
> install properly.
>
> Totem:
> Totem has regularly failed to play any file I have given it. Is it short
> on codecs or what is the problem? It can't even play the WAV files
> created by the Sound Recorder,

	I agree whole-heartedly with this point.  Has ANYBODY ever had Totem work 
properly out-of-the-box?  I suggest that we ditch Totem entirely in favor of 
Mplayer.  This sounds like good bug report material to me.

>
> Network autoconfiguration:
>     The install still assumes users are on a network, and when it fails
> to get a (DHCP?) response the message is cryptic for users on dailup.
> The words 'protocol', 'DHCP' are too technical. Is there a way of
> including more information for new users. I think a lot of people with
> cable modems, which often connect to the ISP's LAN network, will be
> confused by this dialogue. Can I suggest we pull some text from
> wikipedia on networks and DHCP and include this in 6.10?

	I think that while "DHCP" and "protocol" are beyond the vocabulary of the 
average home user, it's really nice for those of us who understand them to be 
able to see what's going on.  Perhaps we can use something like, "Attempting 
to autoconfigure network device (DHCP)."

>     After not finding the network it still assumes I use a network. The
> only option after a failed autoconfiguration is "Continue", why not save
> people who don't understand networks some pain by adding the options "Do
> not configure the network now" or "Do not configure the network at this
> time" (which is in the next set of options anyway) and changing
> "Continue" to "Show more network configuration options"

	I would also like to see an option for simply not having a network, and one 
for configuring it later.  Maybe the options should be something like, "Skip 
Network Configuration" (before it tries to autoconfigure it), "Configure 
manually," and "Suggest some settings."  The latter would explain the other 
options and allow the user to try configuring the network again.

>
>     The option "Do not configure the network at this time" is unusual
> wording. I suggest either "Do not configure the network" or "Do not
> configure the network now"
>

	Hmmm...I've never really had problems with it.  Does it translate weirdly or 
something?

> Partition Manager:
> I can't use "Erase entire disk and use LVM:" as it complains that:
> "Selected device already contains a physical volume" (I used LVM last
> time). So what? Why is there no option to erase the partition table
> (with suitable warnings) and start over? I can do that manually, so why
> make it so hard?

	I don't really know about LVM to say much on that one.

>
> ... install goes ahead ...
>
> [!!] Configure apt
>     Why on earth are the security.ubuntu.com entries commented out? They
> should be ready to kick into play as soon as Ubuntu notices that it has
> access to them. This equates to "Just so you know, when you manage to
> get onto the internet your system will not look for security updates,
> will not give you any warning about this being a problem, and will not
> tell you how to fix this!"
>

	Yikes!  That's a bit scary, because just not being able to get suitable 
security patches poses a security threat.  Another bug worth reporting.

> Should any of those be filed as bug reports? I'm happy to do so, just
> don't know which ones are what.

	Keep up the good work.

	--Dane