[Feisty] Installer is very slow when changing pages

Bug #108731 reported by Martin Pagh Goodwin
4
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Low
Unassigned

Bug Description

For every page change in the installer, the CD has to spin up and down before next bit of information is presented. For instance the "select timezone" has 2 up/down's, one per click/zoom. In the keyboard selection the imstaller almost dies, as it seems to want to spin the CD up for every character typed in the "test your keyboard layout here". In the partitioner a similar behavior was noted when the "format" checkbox was ticked or when a partition was selected for editing.

Martin

Revision history for this message
Colin Watson (cjwatson) wrote :

Not all of this is straightforwardly fixable: in order to avoid massive duplication of effort and divergent bugs between the alternate installer and the desktop installer, the latter is implemented as much in terms of the former as possible, and this involves running external programs from time to time which is probably what's causing the CD to spin up and down. However, I don't understand why clicking on the timezone map would do this, nor why typing characters in the keymap test box would do this.

I'm gradually working on optimising the new partitioner.

Changed in ubiquity:
importance: Undecided → Low
status: Unconfirmed → Confirmed
Revision history for this message
Martin Pagh Goodwin (martin-goodwin) wrote :

OK I have gone back to the installer as I wanted to reinstall the laptop, as I have problems with many aspects of Ubuntus operation (wireless, eth0, etc.) Among other things I am having kern.log and syslog filled with garbage:

<timestamp> ubuntu kernel 111111111111111111111111111111111111111111111111111111111111111111111111111111111111
111111111111111111111111111111111111111111111111111111111111111111111111111111111111
111111111111111111 <etc>

every second.

I thought this was due to problems in the latest kernel release, but booting the installer I just checked kern.log and found it being flooded too.

I am writing this from my workstation, which has a KVM switch to allow me to access my workstation, my firewall/server, and two laptops (one via port extender, the other - the one with the problem just by plugging in the KVM plugs). Well, I boot up the laptop and bring it onto my desk screen

tail /var/log/kern.log -f

and my screen (and the open laptop next to it) fills with "11111". I switch the KVM to my workstation to report my problems, and presto the laptop now shows a series of "legible" errors:

Jun 27 19:28:01 ubuntu last message repeated 172 times
Jun 27 19:28:01 ubuntu kernel: [ 714.452000] ACPI Error (evgpe-0711): No handler or method for GPE[17], disabling event [20060707]

If I switch the KVM back the "111111" messages continue. If I unplug the screen I get the [ 714.... messages again.

There is a brief section of "171717171717" the moment the monitor tries (unsuccessfully) to match the resolution of the laptop

The installer is nice and snappy - no problems as long as I keep my external screen unplugged.

This has nothing to do with the installer, but something with the video adaptor. Now I just need to find out where to look

Martin

Revision history for this message
Robert Roth (evfool) wrote :

Thank you for reporting this bug to Ubuntu. Feisty reached EOL in October 2008.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with Oneiric and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.

Please feel free to report any other bugs you may find.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.