Bug 373087 - Alpha3 is unusable after installation into VMWare
Summary: Alpha3 is unusable after installation into VMWare
Status: RESOLVED DUPLICATE of bug 372189
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Alpha 3
Hardware: x86-64 openSUSE 11.0
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-21 21:20 UTC by Vadim Krevs
Modified: 2008-03-21 21:30 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vadim Krevs 2008-03-21 21:20:24 UTC 
Attempted to install openSUSE 11.0 Alpha3 for x86-64 from the KDE CD into VMWare running on my openSUSE 10.3 for x86_64 notebook (Dell Inspiron 9400).

Had to boot with "hwprobe=-parallel,-misc.par" (see bug #371997), otherwise install hangs. Accepted all defaults except for timezone and language (chose London and English UK). However, the installation appears to hang again after installing all software packages when the GUI installer (so pretty!) for some reason switches back to text mode and starts probing for some hardware ...

Tried reinstalling from scratch 3 times, and got the same result.

So I decided to poweroff and restart the hung VMWare image. The system detects that previous installation was aborted, and offers to resume it. Resuming seems to work, and I end up in a KDE4 desktop.

The only problem is that the mouse does not seem to be able to interact with anything on the desktop. The cursor moves around, but mouse clicks with either mouse button have no effect. Keyboard seems to work - I could bring up Process Manager by pressing "Ctrl-Escape". Needless to say that mouse not working renders the system pretty useless.
Comment 1 Magnus Boman 2008-03-21 21:30:06 UTC 

*** This bug has been marked as a duplicate of bug 372189 ***