Click to See Complete Forum and Search --> : Screensaver Crashes Xwindows


Marklar
02-15-2004, 06:05 PM
When I leave the computer for a while, xwindows (KDE) crashes. I think it started after I accidentally (OK maybe it wasnt really an accident) clicked on .Xclients in the /root directory while in KDE.

Anyhow here is my .xsession-errors log:

SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2052
Window manager warning: Window 0x2000007 (Konqueror) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM.
bitBlt: Incompatible destination pixmap
Window manager warning: Window 0x20003ac (KDE - Konq) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM.
Window manager warning: Window 0x2200007 (Konqueror) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM.
mcop warning: user defined signal handler found for SIG_PIPE, overriding
Window manager warning: Window 0x2600007 (desktop - ) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM.
Window manager warning: Window 0x2200007 (Konqueror) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM.
bitBlt: Incompatible destination pixmap
bitBlt: Incompatible destination pixmap
Window manager warning: Window 0x2000007 (Konqueror) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM.
mcop warning: user defined signal handler found for SIG_PIPE, overriding
Window manager warning: Window 0x2800007 (inittab - ) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM.
bitBlt: Incompatible destination pixmap
bitBlt: Incompatible destination pixmap
Window manager warning: Window 0x2200841 (Missing Pl) sets SM_CLIENT_ID on itself, instead of on the WM_CLIENT_LEADER window as specified in the ICCCM.
KLauncher: Exiting on signal 15
klauncher: Fatal IO error: client killed


What files would .Xclients modify ?
Thanks in advance for help fixing this one.

Shep
02-16-2004, 01:00 PM
What Linux are you using? When I was using Debian, and now Mepis, I had to add the line Option "DPMS" to my /etc/X11/XF86Config-4 file. Does the screen just go grey, then you are kicked out of your X session? This may fix it if so.

mdwatts
02-16-2004, 01:01 PM
Originally posted by Marklar
I think it started after I accidentally (OK maybe it wasnt really an accident) clicked on .Xclients in the /root directory while in KDE.

What files would .Xclients modify ?


Did it only happen once when you executed .Xclients or ever since?

All screensavers?

Have a look at the contents of .Xclients to see what it does.

Marklar
02-17-2004, 11:21 PM
It seems to have fixed itself. The only thing I can think of is that I tried a hard reboot (power off) so maybe some weird bit in some obscure register got reset.

The cool end to the story is that I got Xinerama working. Dual screens ROCK !!!!

I think I may add one or two more :D

Thanks for your helpful suggestions.

mdwatts
02-18-2004, 01:08 PM
Originally posted by Marklar
I
The cool end to the story is that I got Xinerama working. Dual screens ROCK !!!!


They certainly do. Twinview with dual Viewsonic 19" running both at 1800x1440. :)