[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kcmdisplay dumping core (KDE 2)
From:       David Faure <faure () alpha ! tat ! physik ! uni-tuebingen ! de>
Date:       1999-04-26 17:36:34
[Download RAW message or body]

On Mon, Apr 26, 1999 at 07:24:45PM +0200, Sean Kendall Schneyer wrote:
> I've started using the KDE 2 cvs code and am getting a core
> dump from kcmdisplay. Using gdb here is the stack dump
> that I get:
> 
> #0  0x408a216d in getenv (name=0x0) at ../sysdeps/generic/getenv.c:33
> ../sysdeps/generic/getenv.c:33: No such file or directory.
> (gdb) where
> #0  0x408a216d in getenv (name=0x0) at ../sysdeps/generic/getenv.c:33
> #1  0x401bf75e in KConfigBase::readEntry ()
> #2  0x806bb1a in KScreenSaver::getSaverNames ()
> #3  0x8068721 in KScreenSaver::KScreenSaver ()
> #4  0x80765d3 in KDisplayApplication::KDisplayApplication ()
> #5  0x80772b3 in main ()
> (gdb)            
> 
> Is anyone else experiencing any problems with this? Btw, is it
> too early in the development to start sending in these types
> of reports? 
It's not :)

I fixed this yesterday (the bug was in the screensaver themselves, not in kcmdisplay)
BUT : kcmdisplay caches the screensaver names in ~/.kde/share/config/kcmdisplayrc
so if you used the buggy version of it before, you need to clean up this file.

If it still doesn't work, please tell me which screensaver it's trying to
read (add debug output), and try thatscreensaver.kss -desc

-- 
David FAURE
david.faure@insa-lyon.fr, faure@kde.org
http://www.insa-lyon.fr/People/AEDI/dfaure/index.html 
KDE, Making The Future of Computing Available Today

[prev in list] [next in list] [prev in thread] [next in thread]