Community Packages

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#16400 - [electricsheep] not available to xscreensaver

Attached to Project: Community Packages
Opened by PiousMinion (PiousMinion) - Wednesday, 30 September 2009, 02:25 GMT
Last edited by Eric Belanger (Snowman) - Saturday, 17 October 2009, 19:37 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
electricsheep is not available to xscreensaver
Linking to electricsheeps's binary causes a cascade of multiple instances upon screensaver activation.

Additional info:
2.7b12-1

Steps to reproduce:
$pacman -Sy xscreensaver electricsheep
$xscreensaver-demo
-electricsheep not an option.
This task depends upon

Closed by  Eric Belanger (Snowman)
Saturday, 17 October 2009, 19:37 GMT
Reason for closing:  Fixed
Additional comments about closing:  see my comment
Comment by Jelle van der Waa (jelly) - Saturday, 03 October 2009, 16:13 GMT
A solution can be found @ bbs : http://bbs.archlinux.org/viewtopic.php?id=61535
Comment by PiousMinion (PiousMinion) - Saturday, 03 October 2009, 22:17 GMT
Instructions at your link provide information for getting it to work with "gnome-screensaver", not xscreensaver which uses entirely different config files. Following those instructions, but applying them to xscreensaver configs, causes electricsheep to spawn new instances over and over until the system cannot handle any more. I believe the lack of an xscreensaver config for electrichseep to be a bug in the electricsheep package as it's use without xscreensaver(and anything that requires it) is not at all useful.
Comment by Eric Belanger (Snowman) - Saturday, 17 October 2009, 19:37 GMT
Fixed in:
electricsheep-2.7b12-2
xscreensaver-5.10-2

I've fixed it so that is will work out of the box when installing/running xscreensaver for the first time. That's the only way I found that worked. You'll need to fix it manually on your system. There are 2 ways to do that:

1) manually fix the config
- backup your config: cp ~/.xscreensaver ~/.xscreensaver.bak
- find in it the list of available screensavers and go to the last item
- add a \ after the last item then add the following line:
electricsheep --root 1 \n

2) regenerate the config
- remove old config: mv ~/.xscreensaver ~/.xscreensaver.bak
- start xscreensaver-demo and reconfigure xscreensaver

Loading...