I am using split ebuilds for my KDE build. The kdeartwork-kscreensaver module cannot locate xscreensaver modules for xscreensaver 4.22-r1 or 4.22-r2, and thus when compiled does not include any xscreensavers. RSS-Glx screensavers are included, but fail to work. Also, if kdeartwork-kscreensaver was built agains an earlier xscreensaver version, then upgrading to xscreensaver 4.22-r1 or later causes the xscreensaver modules to fail. (Well, actually I noticed my rss-glx screensaver break). This issue seems to be caused by the xscreensaver 4.22-r1 compiling with "--with-hackdir=/usr/lib/misc/xscreensaver". There is a comment in the ChangeLog along the lines of "changed hackdir to something more suitable". Unfortunately in this case, "more suitable" also meant "incompatible with KDE as it stands". Reproducible: Always Steps to Reproduce: 1. install or upgrade xscreensaver to v4.22-r1 or -r2 2. re-emerge kdeartwork-kscreensaver 3. notice that no xscreensaver modules appear in the KDE screensavers dialog Actual Results: KDE "./configure" was unable to locate the xscreensaver modules, and dropped xscreensaver support. The CONTENTS file for kdeartwork-kscreensaver clearly shows that no ".desktop" files for xscreensavers get installed. Expected Results: "It should just work". Seriously, either the xscreensaver hackdir change should be reverted, or the kdeartwork-kscreensaver "configure" system (well, the automake/autoconf bits presumably) need patching to be compatible with the new location. I cannot provide such a patch at this time, due to lack of familiarity with the auto* toolset.
Oh, I did discover a workaround: cd /usr/lib; ln -s misc/xscreensaver xscreensaver (but this kind-of negates the whole point of changing the hackdir!)
*** This bug has been marked as a duplicate of 96074 ***
Actually this is valid, the kdeartwork configure scripts need a fix.
Bug about this on bugs.kde.org: http://bugs.kde.org/show_bug.cgi?id=105748
Created attachment 63624 [details, diff] Patch resolving the xscreensaver install path issue This patch resolves the problem of finding xscreensaver by adding an additional check for lib/misc/xscreensaver/flame to the configure script. It should be added to the official portage tree as soon as possible.
x11-misc/fireflies also has /usr/lib/xscreensaver hard coded in its ebuild, which could cause a problem unless /usr/lib/xscreensaver is linked. In addition, during configure, this error occurs. I think it needs to be /usr/lib/misc/xscreensaver, not /usr/lib/xscreensaver. ln: creating symbolic link '/var/tmp/portage/xscreensaver-4.22-r3/image//usr/lib/xscreensaver/config' to /usr/share/xscreensaver/config': No such file or directory HTH
> In addition, during configure, this error occurs. You mean in fireflies? Please file a separate bug for that and assign to the maintainer.
Gregorio, I noticed you submitted a patch at the kde.org bug that adds a configure switch to specify the hacks dir - why not commit it to portage?
(In reply to comment #8) > Gregorio, I noticed you submitted a patch at the kde.org bug that adds a > configure switch to specify the hacks dir - why not commit it to portage? I committed it to kdeartwork, and I was just committing it to kdeartwork-kscreensaver as we speak... So this is fixed now.
*** Bug 101261 has been marked as a duplicate of this bug. ***
*** Bug 102177 has been marked as a duplicate of this bug. ***
(In reply to comment #9) > (In reply to comment #8) > > Gregorio, I noticed you submitted a patch at the kde.org bug that adds a > > configure switch to specify the hacks dir - why not commit it to portage? > > I committed it to kdeartwork, and I was just committing it to > kdeartwork-kscreensaver as we speak... So this is fixed now. Are you entirely sure that this is fixed, because xscreensaver-4.22-r2 still does not register with kdeartwork-kscreensaver-3.4.1. Here is a snippet from a build of kdeartwork-kscreensaver-3.4.1. from a few minutes ago: checking for lib64/xscreensaver/flame... not found checking for lib/xscreensaver/flame... not found checking for bin/xscreensaver-hacks/flame... not found checking for hacks/flame... not found checking if kscreensaver should be compiled... yes configure: creating ./config.status fast creating Makefile fast creating kscreensaver/Makefile fast creating kscreensaver/kdesavers/Makefile fast creating kscreensaver/kdesavers/data/Makefile fast creating kscreensaver/kpartsaver/Makefile fast creating kscreensaver/kxsconfig/Makefile fast creating kscreensaver/kxsconfig/ScreenSavers/Makefile fast creating kscreensaver/xsavers/Makefile config.pl: fast created 8 file(s). config.status: creating config.h config.status: executing depfiles commands xscreensaver could not be detected on your system. Check www.jwz.org/xscreensaver if you're loving to have tons of screensavers in KDE I would be inclined to reopen the bug for investigation.
> I would be inclined to reopen the bug for investigation. > I agree, an emerge of xscreensaver-4.22-r2 and kdeartwork-kscreensaver-3.4.1 (both with +kde +xscreensaver +opengl USE flags) did NOT result in the xscreensavers being accessable with kscreensaver. The suggested work around: cd /usr/lib; ln -s misc/xscreensaver xscreensaver then re-emerge kscreensaver worked however. So it seems the configure script still does not look in /usr/lib/misc/xscreensaver.
