[Bug 187081] KDE screensaver only blanks screen with any of selected screensaver
https://bugzilla.novell.com/show_bug.cgi?id=187081 ------- Comment #19 from jamnt@sbcglobal.net 2006-09-12 08:38 MST ------- are you trying to tell me that a bug I opened is not relevant to what I was saying? That is quite bizarre. See below: "problem: selecting any screensaver will only blank screen. Powersaved daemon is turned off. DPMS settings are off (sax2 and xset). It seems rather that selection of screensaver does not work, not that there is a problem with power settings?" I am talking all the time about the same issue: can't keep screensaver settings stable. A lot of factors affect these settings: 1) different powersave config files (independent four appletts that affect screensaver settings randomly) 2) login/logout (resets these settings) 3) apps (for example mplayer also resets these settings) 4) kpowersave that also resets screensaver settings without seting them back after computer is connected back with electric cord. To summarize: screensaver settings are not kept at all. example with mplayer (what this has to do with screensaver?): 1) xset -q before mplayer is started: xset -q Keyboard Control: auto repeat: on key click percent: 0 LED mask: 00000000 auto repeat delay: 250 repeat rate: 30 auto repeating keys: 00ffffffdffffbbf fadfffdfffdfe5ef ffffffffffffffff ffffffffffffffff bell percent: 50 bell pitch: 400 bell duration: 100 Pointer Control: acceleration: 20/10 threshold: 4 Screen Saver: prefer blanking: no allow exposures: yes timeout: 130 cycle: 600 Colors: default colormap: 0x20 BlackPixel: 0 WhitePixel: 16777215 Font Path: /usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/URW,/usr/X11R6/lib/X11/fonts/truetype,/usr/X11R6/lib/X11/fonts/uni:unscaled,/opt/kde3/share/fonts Bug Mode: compatibility mode is disabled DPMS (Energy Star): Standby: 7080 Suspend: 7140 Off: 7200 DPMS is Enabled Monitor is On File paths: Config file: /etc/X11/xorg.conf Modules path: /usr/X11R6/lib/modules/updates,/usr/X11R6/lib/modules Log file: /var/log/Xorg.0.log 2) xset after mplayer is started: xset -q Keyboard Control: auto repeat: on key click percent: 0 LED mask: 00000000 auto repeat delay: 250 repeat rate: 30 auto repeating keys: 00ffffffdffffbbf fadfffdfffdfe5ef ffffffffffffffff ffffffffffffffff bell percent: 50 bell pitch: 400 bell duration: 100 Pointer Control: acceleration: 20/10 threshold: 4 Screen Saver: prefer blanking: no allow exposures: yes timeout: 0 cycle: 600 <----------------------- Colors: default colormap: 0x20 BlackPixel: 0 WhitePixel: 16777215 Font Path: /usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/URW,/usr/X11R6/lib/X11/fonts/truetype,/usr/X11R6/lib/X11/fonts/uni:unscaled,/opt/kde3/share/fonts Bug Mode: compatibility mode is disabled DPMS (Energy Star): Standby: 7080 Suspend: 7140 Off: 7200 DPMS is Disabled <--------------------------- File paths: Config file: /etc/X11/xorg.conf Modules path: /usr/X11R6/lib/modules/updates,/usr/X11R6/lib/modules Log file: /var/log/Xorg.0.log For your convenience differences are pointed with arrows. timeout: 0 kills not only screensaver but also kills screen blanking. All this is a big mess with simple (in theory) problem: SuSe does not keep screensaver settings. This is not only my observation. What I ask for, is user control over these settings. Currently screensaver settings are controlled randomly by any possible/impossible application or user action that is not relevant to screensaver (action: login/logout, aplication: starting mplayer). This pretty obvious. Should I file separate bug for each app that affect one setting? This would be strangest thing I ever heard. Moreover I am interested in one thing: screensaver settings. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com