Found a solution to the screensaver problem...

[penguin.ch]

Re: Found a solution to the screensaver problem...

I don't understand what putting *.desktop in the autostart folder actually means.

In short, when a user logs in to KDE, his personal autostart folder gets scanned for "jobs to be done" (as, for example, kicking the screensaver daemon alive ...).

HTH
Birdy

[Unforgiven]

Re: Found a solution to the screensaver problem...

Referring to the original post, there's actually no need to sudo. You're editing a file you own anyway.

Not that it hurts anything, but, you know.

[Dice]

Re: Found a solution to the screensaver problem...

This fix used to work for me too but now it doesn't anymore.
I also tried commenting out the DPMS option in the monitor section of xorg.conf but I still get a blank screen when the screensaver should start.
I noticed the first time this happened there was a big capitol X on the screen (just in case that means something to any of the talented folks here)
Next I tried running kcontrol as root, from console using sudo I got this
"X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
ERROR: Communication problem with kcontrol, it probably crashed."
but kcontrol ran anyway & while I was there I saw that no screensaver was selected & nun of them would display.
Long story short I think root is taking over the screensaver.
Is there a fix for that?

As for this, if you haven't yet found the fix, I read somewhere on here (or somewhere else, maybe?) that if you do:

kdesu kate /etc/X11/xorg.conf

...and change the lines which appear thusly:

 Section "InputDevice"
 /dev/input/event
 for USB
 Identifier   "stylus"
 Driver     "wacom"
 Option     "Device" "/dev/wacom"# Change to 
 Option     "Type" "stylus"
 Option     "ForceDevice" "ISDV4"# Tablet PC ONLY
 EndSection

 Section "InputDevice"
 /dev/input/event
 for USB
 Identifier   "eraser"
 Driver     "wacom"
 Option     "Device" "/dev/wacom"# Change to 
 Option     "Type" "eraser"
 Option     "ForceDevice" "ISDV4"# Tablet PC ONLY
 EndSection

Section "InputDevice"
 /dev/input/event
 for USB
 Identifier   "cursor"
 Driver     "wacom"
 Option     "Device" "/dev/wacom"# Change to 
 Option     "Type" "cursor"
 Option     "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "ServerLayout"

InputDevice  "stylus" "SendCoreEvents"
InputDevice  "cursor" "SendCoreEvents"
InputDevice  "eraser" "SendCoreEvents"
  Identifier   "Default Layout"
  Screen   0 "Default Screen" 0 0
  InputDevice  "Generic Keyboard"
  InputDevice  "Configured Mouse"
EndSection

...To this:

# Section "InputDevice"
 # /dev/input/event
 # for USB
  # Identifier   "stylus"
  # Driver     "wacom"
  # Option     "Device" "/dev/wacom"# Change to 
  # Option     "Type" "stylus"
  # Option     "ForceDevice" "ISDV4"# Tablet PC ONLY
# EndSection
# Section "InputDevice"
 # /dev/input/event
 # for USB
 # Identifier   "eraser"
 # Driver     "wacom"
 # Option     "Device" "/dev/wacom"# Change to 
 # Option     "Type" "eraser"
 # Option     "ForceDevice" "ISDV4"# Tablet PC ONLY
# EndSection
# Section "InputDevice"
 # /dev/input/event
 # for USB
 # Identifier   "cursor"
 # Driver     "wacom"
 # Option     "Device" "/dev/wacom"# Change to 
 # Option     "Type" "cursor"
 # Option     "ForceDevice" "ISDV4"# Tablet PC ONLY
# EndSection

Section "ServerLayout"

  # InputDevice  "stylus" "SendCoreEvents"
  # InputDevice  "cursor" "SendCoreEvents"
  # InputDevice  "eraser" "SendCoreEvents"
  Identifier   "Default Layout"
  Screen   0 "Default Screen" 0 0
  InputDevice  "Generic Keyboard"
  InputDevice  "Configured Mouse"
EndSection

You can be rid of those errors seen when using the "kdesu" command.

This, as explained elsewhere, revents the loading of all wacom devices which are (only?) used on laptops.