Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in

  FAQ | Search | Memberlist | Usergroups | Statistics | Profile | Log in to check your private messages | Log in | Register

xscreensaver, kde screensaver do not work
 View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
wyvern
Tux's lil' helper
Tux's lil' helper


Joined: 04 Apr 2003
Posts: 99
Location: Victoria, B.C.
PostPosted: Thu Jun 01, 2006 10:42 pm    Post subject: xscreensaver, kde screensaver do not work Reply with quote
Hi,

Hopefully someone can help me with this puzzling problem. I checked the bugs database and couldn't find anything.

I have a dual core opteron, on which I'm running Gentoo x64 natively.

I've gotten everything to work, including opengl on the gfx card, a generic GeForce 7300. The monitor is a widescreen, and I've got X.org successfully running on it. In fact, everything is peachy. Except...

xscreensaver and the KDE screensaver refuse to work. The KDE screensaver works well when I test it in the KDE Control panel, but won't start automatically. Xscreensaver flat-out refuses to work, it just hangs on the command line when I invoke it manually. I've tried it on both fluxbox and KDE, so I don't think this is a KDE problem. I tried an strace, here's the excerpt at the end that it yielded (before I killed it with a Ctrl-C, it keeps looping after a pause on poll().)

Quote:

8) = 0
rt_sigaction(SIGABRT, {0x409490, [], SA_RESTORER|SA_NOMASK, 0x2b362976d840}, NULL, 8) = 0
rt_sigaction(SIGABRT, {0x409490, [], SA_RESTORER|SA_NOMASK, 0x2b362976d840}, NULL, 8) = 0
rt_sigaction(SIGFPE, {0x409490, [], SA_RESTORER|SA_NOMASK, 0x2b362976d840}, NULL, 8) = 0
rt_sigaction(SIGBUS, {0x409490, [], SA_RESTORER|SA_NOMASK, 0x2b362976d840}, NULL, 8) = 0
rt_sigaction(SIGSEGV, {0x409490, [], SA_RESTORER|SA_NOMASK, 0x2b362976d840}, NULL, 8) = 0
rt_sigaction(SIGSYS, {0x409490, [], SA_RESTORER|SA_NOMASK, 0x2b362976d840}, NULL, 8) = 0
rt_sigaction(SIGTERM, {0x409490, [], SA_RESTORER|SA_NOMASK, 0x2b362976d840}, NULL, 8) = 0
rt_sigaction(SIGXCPU, {0x409490, [], SA_RESTORER|SA_NOMASK, 0x2b362976d840}, NULL, 8) = 0
rt_sigaction(SIGXFSZ, {0x409490, [], SA_RESTORER|SA_NOMASK, 0x2b362976d840}, NULL, 8) = 0
gettimeofday({1149201523, 265202}, NULL) = 0
gettimeofday({1149201523, 265262}, NULL) = 0
time(NULL) = 1149201523
write(3, "&\2\2\0\1\0@\2", 8) = 8
read(3, "\1\1M\1\0\0\0\0006\1\0\0\0\0\0\0\337\4\333\3\337\4\333"..., 32) = 32
gettimeofday({1149201523, 265529}, NULL) = 0
time(NULL) = 1149201523
time(NULL) = 1149201523
gettimeofday({1149201523, 265702}, NULL) = 0
ioctl(3, FIONREAD, [0]) = 0
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1149201523, 265926}, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 4999) = 0
gettimeofday({1149201528, 264566}, NULL) = 0
ioctl(3, FIONREAD, [0]) = 0
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1149201528, 264751}, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0
gettimeofday({1149201528, 264866}, NULL) = 0
ioctl(3, FIONREAD, [0]) = 0
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1149201528, 265045}, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0
gettimeofday({1149201528, 265159}, NULL) = 0
ioctl(3, FIONREAD, [0]) = 0
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1149201528, 265338}, NULL) = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0
gettimeofday({1149201528, 265452}, NULL) = 0
gettimeofday({1149201528, 265516}, NULL) = 0
time(NULL) = 1149201528
write(3, "&\2\2\0\1\0@\2", 8) = 8
read(3, "\1\1N\1\0\0\0\0006\1\0\0\0\0\0\0\337\4\333\3\337\4\333"..., 32) = 32
gettimeofday({1149201528, 265772}, NULL) = 0
time(NULL) = 1149201528
time(NULL) = 1149201528
ioctl(3, FIONREAD, [0]) = 0
ioctl(3, FIONREAD, [0]) = 0
gettimeofday({1149201528, 266059}, NULL) = 0
poll( <unfinished ...>


Here's the contents of my x.org file:

Quote:

Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the font modules
# Load "type1"
# Load "speedo"
Load "freetype"
# Load "xtt"

# This loads the GLX module
Load "glx"
# This loads the DRI module
# Load "dri"
EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

# RgbPath "/usr/share/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
#

FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi"
# FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"

# The module search path. The default path is shown here.

# ModulePath "/usr/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

# Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

# Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

# Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

# Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Extensions
# **********************************************************************
#
Section "Extensions"

Option "Composite" "Enable"
EndSection


# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

Option "A# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"

# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xorg"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2" # IntelliMouse PS/2
Option "Device" "/dev/psaux"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"utoRepeat" "500 30"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

Option "ZAxisMapping" "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

# Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "vx2025wm"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5 - 64.3

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-70

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.

# Chipset "generic"

# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
Identifier "geforce7300"
Driver "nvidia"
#VideoRam 131072
# Insert Clocks lines here if appropriate
Option "RenderAccel" "true"

EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "geforce7300"
Monitor "vx2025wm"
DefaultDepth 24

Subsection "Display"
Depth 24
Modes "1650x1080"
ViewPort 0 0
EndSubsection
EndSection
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "geforce7300"
Monitor "vx2025wm"
DefaultDepth 24

Subsection "Display"
Depth 24
Modes "1650x1080"
ViewPort 0 0
EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
# Mode 0666
# EndSection

_________________
---
ex nihilo nihil fit
Back to top
View user's profile Send private message
psk31
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jun 2004
Posts: 143
Location: Calgary, AB, Canada
PostPosted: Mon Jun 05, 2006 8:38 pm    Post subject: Reply with quote
Same problem here. Upgraded to kde 3.5.3 and now screen saver will not auto start. Test function works fine however. Is this a kde bug in 3.5.3?

psk31
Back to top
View user's profile Send private message
Matteo Azzali
Retired Dev
Retired Dev


Joined: 23 Sep 2004
Posts: 1133
PostPosted: Tue Jun 06, 2006 12:33 am    Post subject: Reply with quote
Just a question, to make sure, it may be unrelated:
Did you masked xorg-x11-7.1.0 cause of binary drivers and emerged instead the latest xscreensaver-5.00 ?
(I'm nearly sure isn't this, but better to check)
_________________
Every day a new distro comes to birth. Every day a distro "eats" another.
If you're born distro, no matter what, start to run.
---- http://www.linuxprinting.org/ ---- http://tuxmobil.org/
Back to top
View user's profile Send private message
psk31
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jun 2004
Posts: 143
Location: Calgary, AB, Canada
PostPosted: Tue Jun 06, 2006 1:59 am    Post subject: Reply with quote
Currently have installed:
xscreensaver-4.24
xorg-x11-6.8.2-r7

Is a newer version of xscreensaver or xorg-x11 required?

psk31
Back to top
View user's profile Send private message
Matteo Azzali
Retired Dev
Retired Dev


Joined: 23 Sep 2004
Posts: 1133
PostPosted: Tue Jun 06, 2006 8:50 am    Post subject: Reply with quote
psk31 wrote:

Is a newer version of xscreensaver or xorg-x11 required?


Shouldn't.... do you have both GeForce 7300? If so,did you tried changing the drivers version (nvidia-kernel nvidia-glx)
_________________
Every day a new distro comes to birth. Every day a distro "eats" another.
If you're born distro, no matter what, start to run.
---- http://www.linuxprinting.org/ ---- http://tuxmobil.org/
Back to top
View user's profile Send private message
psk31
Tux's lil' helper
Tux's lil' helper


Joined: 10 Jun 2004
Posts: 143
Location: Calgary, AB, Canada
PostPosted: Tue Jun 06, 2006 3:01 pm    Post subject: Reply with quote
Well, went ahead and re-emerged nvidia-kernel-1.0.8762 and nvidia-glx
Still no luck.
I am running a older series of NVIDIA GEforce video card (worked just fine with 3.5.2)
Totally stumped at this point.

psk31
Back to top
View user's profile Send private message
cchee
Apprentice
Apprentice


Joined: 29 Jul 2003
Posts: 214
Location: NYC
PostPosted: Wed Jun 14, 2006 11:35 am    Post subject: Reply with quote
I have the same problem here. I am using inspiron 700m. the graphic chipset is intel. Just upgraded to kde 3.5.3, before upgrade it was fine. xscreensaver is not started and xscreensaver-command -lock works fine in command line. Trying to change screensaver settings in Control Center causes it to crash.
Back to top
View user's profile Send private message
Cottonee
n00b
n00b


Joined: 23 Sep 2003
Posts: 73
Location: Palmerston North, New Zealand
PostPosted: Thu Jun 15, 2006 9:28 pm    Post subject: Reply with quote
Same here :( , work fine before update KDE 3.5.3. Then screensaver won't start but it works in CLI with xscreensaver-demo

System:
x11-misc/xscreensaver 4.2.4
x11-base/xorg-x11 6.8.2-r7
media-video/nvidia-glx 1.0.7174-r5
media-video/nvidia-kernel 1.0.7174-r2
Nvidia GeForce 2 GTS ram 64Mb

Maybe a bug, kdelib? anyone?
Back to top
View user's profile Send private message
Carlo
Developer
Developer


Joined: 12 Aug 2002
Posts: 3356
PostPosted: Thu Jun 15, 2006 9:36 pm    Post subject: Re: xscreensaver, kde screensaver do not work Reply with quote
wyvern wrote:
I checked the bugs database and couldn't find anything.

Can't believe that. :arrow: bug 135726
_________________
Please make sure that you have searched for an answer to a question after reading all the relevant docs.
Back to top
View user's profile Send private message
Raistlin
l33t
l33t


Joined: 17 May 2004
Posts: 691
Location: Boston, MA
PostPosted: Fri Jun 16, 2006 4:51 pm    Post subject: Reply with quote
similar behaviour here: kde 3.5.2, AMD64 X2 4800+, Nvidia 6600GT.
With Nvidia's openGL implementation
Code:
eselect opengl set nvidia

the openGL screensavers don't show any picture. xorg-x11's openGL works, though...
_________________
Zwei Was Eins Initially

"Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."
Back to top
View user's profile Send private message
jrudy66606
n00b
n00b


Joined: 16 Apr 2004
Posts: 46
PostPosted: Fri Oct 13, 2006 8:14 pm    Post subject: Reply with quote
This seems to be an issue with the DPMS and xorg. Something to do with kde thinking DPMS is working so it never activates the screensaver. To fix this edit your /home/<user>/.kde/share/config/kdesktoprc file and add to the [ScreenSaver] section:

Code:
DPMS-dependent=false


You might have to restart the xserver, but it fixes the problem. No need to install xscreensaver
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



 Links: forums.gentoo.org | www.gentoo.org | bugs.gentoo.org | wiki.gentoo.org | forum-mods@gentoo.org

Copyright 2001-2024 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy