Hello,

i simply made an system update yesterday and after restart X does not start anymore!
The system is in usage so i have to wipe it and install an backup from the beginning of the month where everything was fine.

I suppose the XServer is broken, because the Xorg.0.log stops without an error message.
The main system is running and i can connect to it via SSH.
But the screen is only black and also a TTY1 cannot be accessed locally!
If this problem does not belong to the XServer, please move it to the correct package.
Thanks.

Here the packages that where updated.

Start-Date: 2014-12-30  19:52:20
Upgrade: libsox-fmt-all:amd64 (14.4.0-3, 14.4.0-3+deb7u1), bind9-host:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2,
9.8.4.dfsg.P1-6+nmu2+deb7u3), libsox-fmt-mp3:amd64 (14.4.0-3, 14.4.0-3+deb7u1), libsox-fmt-base:amd64 (14.4.0-3,
14.4.0-3+deb7u1), dnsutils:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), libdbus-1-3:amd64
(1.6.8-1+deb7u4, 1.6.8-1+deb7u5), libdbus-1-3:i386 (1.6.8-1+deb7u4, 1.6.8-1+deb7u5), unzip:amd64 (6.0-8, 6.0-8+deb7u1),
apache2-suexec:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4), apache2-mpm-worker:amd64 (2.2.22-13+deb7u3,
2.2.22-13+deb7u4), xserver-xorg-core:amd64 (1.12.4-6+deb7u2, 1.12.4-6+deb7u5), libsox-fmt-oss:amd64 (14.4.0-3,
14.4.0-3+deb7u1), libsox-fmt-pulse:amd64 (14.4.0-3, 14.4.0-3+deb7u1), linux-compiler-gcc-4.6-x86:amd64
(3.16.7-2~bpo70+1, 3.16.7-ckt2-1~bpo70+1), xserver-common:amd64 (1.12.4-6+deb7u2, 1.12.4-6+deb7u5),
libsox-fmt-alsa:amd64 (14.4.0-3, 14.4.0-3+deb7u1), libdns88:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2,
9.8.4.dfsg.P1-6+nmu2+deb7u3), subversion:amd64 (1.6.17dfsg-
4+deb7u6, 1.6.17dfsg-4+deb7u8), libsox2:amd64 (14.4.0-3, 14.4.0-3+deb7u1), linux-image-3.2.0-4-amd64:amd64
(3.2.63-2+deb7u1, 3.2.63-2+deb7u2), linux-headers-3.2.0-4-amd64:amd64 (3.2.63-2+deb7u1, 3.2.63-2+deb7u2),
libisccc80:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), apache2-utils:amd64 (2.2.22-13+deb7u3,
2.2.22-13+deb7u4), iucode-tool:amd64 (0.8.3-1, 0.8.3-2), apache2:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4),
libsvn1:amd64 (1.6.17dfsg-4+deb7u6, 1.6.17dfsg-4+deb7u8), dbus:amd64 (1.6.8-1+deb7u4, 1.6.8-1+deb7u5),
apache2.2-common:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4), linux-headers-3.2.0-4-common:amd64 (3.2.63-2+deb7u1,
3.2.63-2+deb7u2), liblwres80:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), cpio:amd64
(2.11+dfsg-0.1, 2.11+dfsg-0.1+deb7u1), apache2.2-bin:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4), libsox-fmt-ao:amd64
(14.4.0-3, 14.4.0-3+deb7u1), libbind9-80:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), ntp:amd64
(4.2.6.p5+dfsg-2, 4.2.6.
p5+dfsg-2+deb7u1), sox:amd64 (14.4.0-3, 14.4.0-3+deb7u1), mime-support:amd64 (3.52-1, 3.52-1+deb7u1), libjasper1:amd64
(1.900.1-13+deb7u1, 1.900.1-13+deb7u2), libisccfg82:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3),
apache2-doc:amd64 (2.2.22-13+deb7u3, 2.2.22-13+deb7u4), bsd-mailx:amd64 (8.1.2-0.20111106cvs-1,
8.1.2-0.20111106cvs-1+deb7u1), libsox-fmt-ffmpeg:amd64 (14.4.0-3, 14.4.0-3+deb7u1), linux-libc-dev:amd64
(3.2.63-2+deb7u1, 3.2.63-2+deb7u2), host:amd64 (9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3),
intel-microcode:amd64 (1.20140624.1, 1.20140913.1), dbus-x11:amd64 (1.6.8-1+deb7u4, 1.6.8-1+deb7u5), libisc84:amd64
(9.8.4.dfsg.P1-6+nmu2+deb7u2, 9.8.4.dfsg.P1-6+nmu2+deb7u3), deb-multimedia-keyring:amd64 (2012.05.10-dmo4, 2014.2)
End-Date: 2014-12-30  19:53:50

Hello together,

i did not install the backup and found the problem now.
The ATI driver from March 2014 did not fit together with the updated X-Server package.

I downloaded and installed the newest Catalyst driver from here and X is running now again:
http://support.amd.com/de-de/download/desktop?os=Linux+x86
Version Omega (14.12) from 09.12.2014.

So this bug can be closed now.

But you should think about an solution for the problem, because after the upgrade you did not have the chance to see
anything, because the graphic card was dead.
When you have not another PC, network and a running SSH-Server on the system, you can't do anything to get it working
again. This is really fatal!

 From my experience in the last year it is getting more and more difficult to get an working desktop system with running
X and sound with Debian.
There are problems with ATI and NVidia, such as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767678

Is there really no chance to get this problems covered?
A failsafe system that has the possibilty to have X with a standard VGA resolution would be a milestone for Debian.

I wish you a happy new year!
Karsten

 > But you should think about an solution for the problem, because after the upgrade you did not have the chance to see
anything, because the graphic card was dead.
 > When you have not another PC, network and a running SSH-Server on the system, you can't do anything to get it working
again. This is really fatal!

Here is an idea for other users who encounter the problem:

When you are booting with grub you can manually edit the boot options in grub.
https://www.gnu.org/software/grub/manual/html_node/gfxpayload.html

Add "text" at the end of the kernel parameters to boot in a text console so that the X system will not be started.
Then you can download and install the ATI driver in text mode.