| Summary: | screen blanked despite saving being disabled | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreensaver | Reporter: | Marcin Kasperski <Marcin.Kasperski> |
| Component: | general | Assignee: | kscreensaver bugs tracking <kscreensaver-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | kde-bugzilla, l.lunak |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Marcin Kasperski
2004-02-24 12:33:00 UTC
The problem disappeared after I disabled all APM settings in BIOS and it seems the real bug is related somewhere betweend my hardware, my kernel and my XFree. The KDE part of this bug is that although I deliberately disabled everything about APM I found in KDE config, KDE still enabled some energy saving features (or at least I interpret in this way the situation - using other window managers similar problem never happened). What's the ouput if you run "xset q" in Konsole? Are you really sure you have both screensaver disabled and monitor saving (DPMS - in Power control->Monitor control) disabled in KControl? I am not sure whether my current 'xset q' will matter anything, in the meantime I upgraded from debian woody to debian sarge (newer XFree, newer KDE, ....)
Nevertheless here it is:
$ xset q
Keyboard Control:
auto repeat: on key click percent: 0 LED mask: 00000010
auto repeat delay: 250 repeat rate: 30
auto repeating keys: 00ffffffdffffbbf
fadfffffffdfe5ff
ffffffffffffffff
ffffffffffffffff
bell percent: 50 bell pitch: 400 bell duration: 100
Pointer Control:
acceleration: 20/10 threshold: 4
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 0 cycle: 600
Colors:
default colormap: 0x20 BlackPixel: 0 WhitePixel: 65535
Font Path:
unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/cyrillic,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi,/home/marcink/.fonts,/home/marcink/.fonts/Ghostscript8,/home/marcink/.fonts/QuasiTrueType,/home/marcink/.fonts/TeXowe
Bug Mode: compatibility mode is disabled
DPMS (Energy Star):
Standby: 1200 Suspend: 1800 Off: 2400
DPMS is Disabled
Font cache:
hi-mark (KB): 5120 low-mark (KB): 3840 balance (%): 70
File paths:
Config file: /etc/X11/XF86Config-4
Modules path: /usr/X11R6/lib/modules
Log file: /var/log/XFree86.0.log
i'm seeing this too - but only after i played with the screensaver config, so i assume something goes wrong with the dcop signals. Screen Saver: prefer blanking: yes allow exposures: yes timeout: 70 cycle: 600 DPMS (Energy Star): Standby: 1200 Suspend: 1800 Off: 2400 DPMS is Disabled *** Bug 136315 has been marked as a duplicate of this bug. *** while this sounds like the inverse, i'm pretty sure it is the same ... *** This bug has been marked as a duplicate of 75254 *** ok, so it is not the same, after all ... ... but i think lubos fixed a). dunno what to make of b) - prolly an x bug and fixed meanwhile. I haven't observed this problem for quite a lot of time. It need not prove anything as I managed to switch to another PC twice in the meantime, but, well.... |