Version: (using KDE KDE 3.2.0) Installed from: Gentoo Packages Compiler: 3.2.3 OS: Linux The swarm screen saver does not work as expected. It appears to grab the screen and it does not refresh until the screen saver stops. More specificly, when the scree saver starts it looks as if the display freezes and the desktop doesnt refresh until the screen saver is stoped.
This happens to me too. KDE 3.2.3 and QT compiled from source, X from x.org, gcc 3.3.4, binutils-2.14.90.0.3, glibc 2.3.2, slackware-current derived system.
I can't reproduce this at all. Can you try running the screensaver manually by opening a terminal window and running the command 'kswarm.kss' and see if that works properly? Thanks
When I upgraded to KDE 3.2 using debs provided by kde.org, kswarm stopped working properly. I found a copy of kscreensaver from KDE3.1 and apt-pinned it to that version, and it worked fine. . Currently I'm using KDE debs from Debian sarge (and kscreensaver3.1.4 depends on on the old kdelibs), so i have kscreensaver3.2 installed and kswarm is broken again. . kswarm.kss runs fine in a window from the command line, and it also runs full-screen when you 'test' it in the screen saver control module.
If you back this patch out and rebuild, kswarm will work again: http://webcvs.kde.org/kdeartwork/kscreensaver/xsavers/main.cpp?r1=1.8&r2=1.9
I can reproduce that. Just configure swarm, enable the seconds in the kicker clock and call "dcop kdesktop KScreensaverIface save" - you'll see the seconds stop
The solution is to just delete kswarm.kss after you build kde. (and all references to it in the config files). This has been broken forever. If you delete it then the users don't complain about it; most don't even know it is gone. JGH >From: Stephan Kulow <coolo@kde.org> >Reply-To: 74663@bugs.kde.org >To: llinux_boy@hotmail.com >Subject: [Bug 74663] Swarm screen saver is broke. Date: 28 Jan 2005 >12:29:18 -0000 >Received: from ktown.kde.org ([131.246.103.200]) by mc4-f25.hotmail.com >with Microsoft SMTPSVC(6.0.3790.211); Fri, 28 Jan 2005 04:29:58 -0800 >Received: (qmail 17262 invoked by uid 30); 28 Jan 2005 12:29:18 -0000 >X-Message-Info: JGTYoYF78jFIt0tU52DRpFWlHoWzwVhflQBbprFzfOE= >X-Bugzilla-URL: http://bugs.kde.org/ X-Bugzilla-Reason: Voter >Precedence: bulk Return-Path: anonymous@ktown.kde.org >X-OriginalArrivalTime: 28 Jan 2005 12:29:58.0400 (UTC) >FILETIME=[146CB000:01C50535] > >------- You are receiving this mail because: ------- >You are a voter for the bug, or are watching someone who is. > >http://bugs.kde.org/show_bug.cgi?id=74663 >coolo kde org changed: > > What |Removed |Added >---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEW > everconfirmed|0 |1 > > > >------- Additional Comments From coolo kde org 2005-01-28 13:29 ------- >I can reproduce that. Just configure swarm, enable the seconds in the >kicker clock and call "dcop kdesktop KScreensaverIface save" - you'll see >the seconds stop _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
*** Bug 83467 has been marked as a duplicate of this bug. ***
can't reproduce. as there were several fixes that are likely to have influenced any such bug, i assume it being fixed until shown otherwise.
The bug has been reported at http://bugs.debian.org/533048 for 4.2.4 and can be reproduced here with 4.4.1 => reopen
whoops, indeed - the kswarm and kspace savers have not been ported to libkscreensaver, but are instead duplicating the code. this means that they have missed the new features and bug fixes of the last years.
*** Bug 239011 has been marked as a duplicate of this bug. ***
*** Bug 274635 has been marked as a duplicate of this bug. ***
The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more. I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component.