Garbled screen after updating x11-common

[dp]

Binary package hint: xorg

I installed all available updates for Ubuntu 9.10 on my MacBook 2,1 today. After a reboot, the login screen was garbled (see attached photo). Using "ps aux" I was able to decode the error message that was supposed to be shown in the garbled window: "Failed to load module i810 (module does not exist, 0)"

Console screens were affected as well, probably even worse. On the X11 screen, I can still move the mouse and click on things. Terminal screens show a garbled cursor (no photo, sorry) - no other output is reported (blindly logging in an typing "sudo reboot" is possible though).

I fixed this by logging in via SSH and downgrading the Package x11-common from 7.3+3ubuntu10 to 7.4+3ubuntu7 (the only alternative available in aptitude).

Description: Ubuntu 9.10
Release: 9.10

(the following shows my system with the downgraded package)
x11-common:
  Installiert: 1:7.4+3ubuntu7
  Kandidat: 1:7.4+3ubuntu10
  Versions-Tabelle:
     1:7.4+3ubuntu10 0
        500 http://de.archive.ubuntu.com karmic-updates/main Packages
 *** 1:7.4+3ubuntu7 0
        500 http://de.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

[Rajeswaran M (rajeswaran-m)]

I had the same error. To fix this I installed ubuntu in new partition, and copied the below files from xorg 7.4+3ubuntu7, then everything was ok with the old partition.

/etc/gdm/failsafeXinit
/etc/gdm/failsafeXServer

Attached is the log file when it failed.

[Rajeswaran M (rajeswaran-m)]

Attached is the new log file where it does not report any error.

[Thomas Dreibholz (dreibh)]

I can confirm the same problem on my ThinkPad W500 using the internal Intel graphics. After an upgrade to the latest version of x11-common, the X11 server becomes unusable when started. Restarting (even after removing batteries and AC adapter) does not solve the problem. Going to a console login is not possible, since the graphics output is completely garbled. SSH to the system remained possible, so that I have been able to downgrade to 7.4+3ubuntu7. Since that, the system again works as it should.

The importance of this bug should be set to the highest priority, since this bug makes a system unusable.

[Timo Aaltonen (tjaalton)]

check bug 491483 to see if this is a dupe of that one