On 17 May 2012, Arnt Karlsen wrote: > > ..ok, what sort of networking do you run?
Just connected via cables with static links. > > ..ok, they may both be alive, despite the zero response. > No blinkenlight trio? (CapLock+NumLock+ScrollLock LED's) > Nothing visible when that happens. > > up. > > ..the 3 tail -f $logfile ideas; 1, over ssh until ssh breaks, > 2, over the grub serial console, or, 3, log to your syslog > server on your 3'rd box, to capture log files when you try > crash X again. Can you spell this out please? I don/t understand. Incidentally, in the last couple of days I made a second installation of Debian on a spare section of disk. In stable everything worked correctly, as expected. I upgraded to Testing and it still worked. I then upgraded to Sid and the problem reappeared. I really can't believe I am the only user finding this. Is it a bug in X on Sid? (I originally reported it as a bug in i3 but it is not confined to that wm.) Anthony -- Anthony Campbell - a...@acampbell.org.uk Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk - sample my ebooks at http://www.smashwords.com/profile/view/acampbell -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120517082231.gb5...@acampbell.org.uk