NO cursor control on installation at step 1 of 6

Bug #516660 reported by Ed80
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: ubuntu-docs

I am trying to install Ubuntu 9.1 on a new Toshiba L505D laptop with factory Windows 7.
During the load from CD I see one possible problem: " WORKER [1041] unexpectedly returns with status 0X0100"

When I get to the question and answer part of the install, STEP ONE OF SIX, I have no way to input the answers. No control of cursor in midle of screen. Touch pad does not work, nor do the arrow keys, the mouse or ANY other key on the keyboard.

In one of my many attempts I tried to run Ubuntu from the CD rather than from my PARTITIONED drive. It worked perfectly all the way through step 6 of the install. I was instructed to reboot at that point. WHen I rebooted I lost all control of the cursor again.

Any help would be greatly appreciated.

Alex Wardle (awardle)
affects: ubuntu-docs (Ubuntu) → ubuntu
Revision history for this message
Monkey (monkey-libre) wrote :

I´ve assigned this bug to the ubiquity package. Please give more information, I´ve added a link for that.
https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs

Thank You for making Ubuntu better.

affects: ubuntu → ubiquity (Ubuntu)
Revision history for this message
Ed80 (emc2-lighthouse) wrote : Re: [Bug 516660] Re: NO cursor control on installation at step 1 of 6

Sorry, I am unable to respond. Windows restore failed to restore my HD
as expected and the computer has to be returned to Toshiba to have the
HD restored. Might be two weeks before I can try to install Ubuntu
again. Now I really want a Linux system...
Ed

Monkey wrote:
> I´ve assigned this bug to the ubiquity package. Please give more information, I´ve added a link for that.
> https://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs
>
> Thank You for making Ubuntu better.
>
> ** Package changed: ubuntu => ubiquity (Ubuntu)
>
>

Revision history for this message
Monkey (monkey-libre) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in ubiquity (Ubuntu):
status: New → Invalid
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.