Version: 0.10.0 (using 4.3.4 (KDE 4.3.4) "release 2", KDE:KDE4:STABLE:Desktop / openSUSE_11.1) Compiler: gcc OS: Linux (x86_64) release 2.6.27.37-0.1-default My screensaver is deactivated. When I start a picture-show with Digikam/Showfoto/Gwenview the screensaver is set, when the picture-show ends. Worst: the checkbox in systemsettings is not checked. I wish that Digikam checks, if the screensaver is set and deactivates it only when the saver is set. Hartmut
This is irrelevant of digiKam. we never touch KDE screensaver settings... Gilles Caulier
It is fact: I have no screensaver, my computer can run days without screensaver appearing. But if I run a pictureshow one minute after the end of the show my sceen is black, but not black because of monotor-sleeping - black with backlight. And we have three maschines here - all do the same. Hartmut Gilles Caulier schrieb: > https://bugs.kde.org/show_bug.cgi?id=218187 > > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution| |INVALID > > > > > --- Comment #1 from Gilles Caulier <caulier gilles gmail com> 2009-12-10 22:28:17 --- > This is irrelevant of digiKam. we never touch KDE screensaver settings... > > Gilles Caulier > >
perhaps this is the kipi-plugins Slideshow (and not digikam)?
Rex Dieter schrieb: > https://bugs.kde.org/show_bug.cgi?id=218187 > > > Rex Dieter <rdieter@math.unl.edu> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |rdieter@math.unl.edu > > > > > --- Comment #3 from Rex Dieter <rdieter math unl edu> 2009-12-11 00:07:58 --- > perhaps this is the kipi-plugins Slideshow (and not digikam)? > > Maybe, but how do I know? It's not a crash, where I can see which modul has crashed ... Complement: it is the screensaver and nothing else, because if I if I go to systemsettings/screensaver and "activate" it (it is activ but not checked) and then deactivate it, the screensaver is off. Hartmut
The answer to Rex' question is which slideshow you select: From the "Slideshow" button you can choose between four different actions - All, Selection, Including subalbums, or Advanced Slideshow.
It happens with All, Selection, Including subalbums. The advanced slideshow crashes my x-server! Hartmut Marcel Wiesweg schrieb: > https://bugs.kde.org/show_bug.cgi?id=218187 > > > Marcel Wiesweg <marcel.wiesweg@gmx.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |marcel.wiesweg@gmx.de > > > > > --- Comment #5 from Marcel Wiesweg <marcel wiesweg gmx de> 2009-12-11 16:15:11 --- > The answer to Rex' question is which slideshow you select: > >From the "Slideshow" button you can choose between four different actions - > All, Selection, Including subalbums, or Advanced Slideshow. > >
Digikam uses the standard freedesktop screensaver inhibition interface via DBus. In fact, the relevant code is copied verbatim from okular. (that means, starting a presentation from a PDF in okular should give the same problem).
Am 16.12.2009 22:31, schrieb Marcel Wiesweg: > https://bugs.kde.org/show_bug.cgi?id=218187 > > > > > > --- Comment #7 from Marcel Wiesweg <marcel wiesweg gmx de> 2009-12-16 22:31:09 --- > Digikam uses the standard freedesktop screensaver inhibition interface via > DBus. In fact, the relevant code is copied verbatim from okular. (that means, > starting a presentation from a PDF in okular should give the same problem). > > I tried it and you are right: its the same with okular. I did not find out earlier, because I never ever startet a presentation of PDFs ... What do I do now? Bugreport or wish to bugs@okular? Hartmut
Either the code in okular and digikam is wrong, though I dont see what could be wrong there. Or there is a problem with the process implementing the DBus interface. For a normal KDE/Plasma desktop, that is KRunner.
Here i've got the exact same problem. I think its caused from a wrong KRunner implementation of the screensaver. Specificly screensaver/saverengine.cpp from krunner ( http://websvn.kde.org/trunk/KDE/kdebase/workspace/krunner/screensaver/saverengine.cpp ). The code for uninhibiting doesn't check whether the screensaver is enabled altogether (line 424). As long as an application inhibits and later uninhibits the (possibly disabled) screensaver, the screensaver gets enabled. The correct call in this line should read enable( KScreenSaverSettings::screenSaverEnabled() ) Maybe somebody can reassign this bug to krunner ?
The screensaver is no longer part of KRunner.