kde startup crash

Michael Adam micada at web.de
Sat Sep 20 22:42:35 BST 2003

Am Dienstag, 16. September 2003 18:52 schrieb John Sowden:
> I recently installed suse 8.2 pro, which came with kde 3.1 on a 1.2Ghz
> 256MB ram box.  All is fine.  Then yesterday, when I was demoing (sp?) my
> new machine to a windows kinda guy, I got an "Input Not Supported" message
> on the screen.  I have learned that this is an internal message generated
> by my Envision LCD screen display.  I can ctrl-alt-F1 to another console
> and it runs fine in text mode.  On boot, Lilo comes up in graphics fine.  I
> do not get the kde sign-on screen, and I read a message on the tty1 screen
> that said: DCOP communications error!  and   using insecure memory.  I have
> been using the machine for about 2 weeks with no other problems (except a
> modem issue).
> This might not be a kde issue, but I don't know where to start
Asked google? <-(

Does your xf86Config meet the monitor's capabilities?

This message is from the kde mailing list.
Account management:  http://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

More information about the kde mailing list