Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#6956 - xscreensaver not working after latest upgrade(s)

Attached to Project: Arch Linux
Opened by David Rosenstrauch (darose) - Wednesday, 18 April 2007, 14:53 GMT
Last edited by Tobias Powalowski (tpowa) - Friday, 20 April 2007, 22:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Medium
Priority Normal
Reported Version 0.8 Voodoo
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After the latest upgrades, my xscreensaver no longer works. I use KDE as my desktop, and see the following problems:

1) when I lock the screen, no screensaver gets displayed
2) when I go into KDE Control Center -> Appearance & Themes -> Screen Saver
a) it doesn't display a running sample of the chosen screen saver in the little computer monitor picture on the right side
b) pressing the Test button does not temporarily activate the screen saver, as it should

There is some discussion at http://bbs.archlinux.org/viewtopic.php?pid=244230 as to the cause and a possible solution to this issue, but I don't know if the solution proposed is the right one.

This isn't a high priority item, but it is an annoying little peeve for me, which I'd like to get fixed soon.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Friday, 20 April 2007, 22:35 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Wednesday, 18 April 2007, 15:43 GMT
What version of xscreensaver do you use? 5.01-2 has this bug, 5.01-3 should have fixed this.
There's a possibility that KDE has its own screensaver implementation and doesn't follow XScreensaver in this, and still looks for the old screensaver location. A rebuild of kdebase should fix this problem in that case.
Comment by David Rosenstrauch (darose) - Wednesday, 18 April 2007, 15:49 GMT
I just upgraded to 5.01-3 this morning, but it didn't seem to fix the problem. Do I need to reboot? (I did drop to single-user mode when I did the upgrade, but didn't do a full reboot.)

As far as the KDE issue, can someone verify if this is the case and, if so, upgrade the kdebase package?
Comment by Darwin Bautista (djclue917) - Thursday, 19 April 2007, 12:42 GMT
Confirmed in KDE. The kdeartwork package should be the one rebuilt.
Comment by Jan de Groot (JGC) - Thursday, 19 April 2007, 12:51 GMT
You're sure about that one? AFAIK kdebase contains the basic screensaver support, kdeartwork provides the extra screensavers if I'm not mistaken.
Comment by Darwin Bautista (djclue917) - Thursday, 19 April 2007, 12:58 GMT
@JGC, yes. I'm sure about this. kdeartwork actually contains the apps needed to run and configure xscreensavers in KDE--kxsrun and kxsconfig respectively.

darwin@excelsior:~$ pacman -Qo /opt/kde/bin/kxsrun /opt/kde/bin/kxsconfig
/opt/kde/bin/kxsrun is owned by kdeartwork 3.5.6-1
/opt/kde/bin/kxsconfig is owned by kdeartwork 3.5.6-1

Also, the kdeartwork's PKGBUILD lists xscreensaver as a makedepends: makedepends=('xscreensaver' 'glut')
Comment by David Rosenstrauch (darose) - Thursday, 19 April 2007, 13:40 GMT
Yep! That did the trick! I just rebuilt and installed kdeartwork locally, and it fixed the problem.

So please bump the package number up to 3.5.6-2 and rebuild, and then this bug can be closed.

Cool! Thanks, djclue and jgc!

Loading...