xorg broken vmware upgrade 6.06 to feisty

Bug #90139 reported by Paul Hoch
4
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Chris Rose

Bug Description

Binary package hint: xorg

I have a VMWare virtual machine that was running 6.06 and I have attempted to upgrade to feisty. Can't get X to start even with default configurations.

Error output is:

(EE) Module ABI Major version (0) doesn't match server's version (1)
(EE) Failed to load module "vmware" (module requirement mismatch, 0)
(EE) No drivers available.

I have attempted to reconfigure x several times, including trying to use vesa but I've had no luck. This appears to be specific to the upgrade as I have a "fresh" install also on VMWare and I don't have the same issue.

Revision history for this message
Chris Rose (chris-vault5) wrote :

Thanks for your bug report. Have you also upgraded VMWare tools inside the VM?

Changed in xorg:
status: Unconfirmed → Needs Info
Revision history for this message
Paul Hoch (paulbhoch) wrote :

Yes I did. I had to upgrade my version of VMWare in order for the tools to build. Once I upgraded my version of VMWare I reinstalled the VMWare tools and rebuilt them. It built successfully and appears to be running.

Revision history for this message
Chris Rose (chris-vault5) wrote :

Thanks.

Can you please upgrade your copy of feisty to the latest, reinstall VMWare tools and see if this goes away? Xorg has been updated a lot recently and this bug might have been zapped along the way.

Changed in xorg:
assignee: nobody → chris-vault5
Revision history for this message
Paul Hoch (paulbhoch) wrote :

Sorry - I upgraded again tonight and reinstalled VMWare tools. Still getting the same error and I'm not able to get an X session running using any combination of drivers/configs.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Please attach Xorg.0.log and xorg.conf so we can have a look.

Revision history for this message
Paul Hoch (paulbhoch) wrote :

Here is the xorg.conf

Revision history for this message
Paul Hoch (paulbhoch) wrote :

Here is the log.

Revision history for this message
Paul Hoch (paulbhoch) wrote :

With the latest round of updates, my system will only boot into recovery mode. I did an upgrade yesterday and then again today and I'm still stuck. If I boot "normally", it gets to the point where it attempts to start x, then gives me the "failed to start x would you like to see log..." at which point I hit no, then it says "X is disabled" and I hit ok, then the "X is disabled" message comes back up and the system is stuck. If I hit alt-f8 I see "Running local boot scripts (/etc/rc.local) [ OK ] " and then nothing. alt-f1 shows "X Server is now disabled. Restart GDM when it is configured correctly" with "OK" highlighted but it does not respond to input. alt f2 - f7 show a single underscore as though it were a cursor. The system sits like this until I "stop" the VM. I have booted into recovery mode several times and attempted to reconfigure X, reinstall VM Tools, etc. all with no luck.

Revision history for this message
Paul Hoch (paulbhoch) wrote :

I did another update today and I'm still experiencing the same symptoms. I did manage to get a screen shot of the XServer output which I'm attaching.

Revision history for this message
Paul Hoch (paulbhoch) wrote :

I got it fixed today! From the recovery console, I did apt-get remove xserver-xorg, rebooted and then did apt-get install xserver-xorg. That seemed to correct whatever leftover driver was causing the issue.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Good to hear, maybe there was something wrong with the config after all..

Changed in xorg:
status: Needs Info → Rejected
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.