Sure. Though it does feel quite strange that a program called "xscreensaver" should require Wayland!
I will make the change as part of the next version bump.
| Git Clone URL: | https://aur.archlinux.org/xscreensaver-arch-logo.git (read-only, click to copy) |
|---|---|
| Package Base: | xscreensaver-arch-logo |
| Description: | Screen saver and locker for the X Window System with Arch Linux branding |
| Upstream URL: | https://www.jwz.org/xscreensaver/ |
| Licenses: | 0BSD |
| Conflicts: | xscreensaver |
| Provides: | xscreensaver |
| Submitter: | Harvie |
| Maintainer: | Geballin (morgenstern) |
| Last Packager: | morgenstern |
| Votes: | 213 |
| Popularity: | 0.125419 |
| First Submitted: | 2009-05-19 16:57 (UTC) |
| Last Updated: | 2026-09-24 09:48 (UTC) |
Sure. Though it does feel quite strange that a program called "xscreensaver" should require Wayland!
I will make the change as part of the next version bump.
It seems Wayland has become common enough that this package should have it enabled by default now. Can that be changed?
Please note that the PKGBUILD for version 6.11 includes the build option --enable-pam-check-account-type (see here and here).
If you get the message "password initialization failed" when trying to unlock your screen, then you may need to uncomment the following line in /etc/pam.d/xscreensaver:
auth include system-auth
Updated, apologies for the delay.
bug in 6.04: Unable to flush stdout: Bad file descriptor.
diff --git a/hacks/xscreensaver-getimage-file b/hacks/xscreensaver-getimage-file
index 54ce2a8b..80a69e77 100755
--- a/hacks/xscreensaver-getimage-file
+++ b/hacks/xscreensaver-getimage-file
@@ -1545,6 +1545,13 @@ sub main() {
my $abs_p = 0;
my $flush_p = 0;
+ # Some time between perl 5.16.3 and 5.28.3, invoking a script with >&-
+ # started writing "Unable to flush stdout: Bad file descriptor" to stderr
+ # at exit. So if stdout is closed, open it as /dev/null instead.
+ #
+ open (STDOUT, '>', '/dev/null')
+ if (! defined (syswrite (STDOUT, ""))); # undef if fd closed; 0 if open.
+
while ($_ = $ARGV[0]) {
shift @ARGV;
if (m/^--?verbose$/s) { $verbose++; }
Nice, seems to be displaying the Arch logos properly now.
@alex.forencich the Arch logos are distributed with the PKGBUILD and are applied in the prepare() function by replacing the default xscreensaver logo images and bitmaps. However, it looks like some additional xscreensaver logos were added in xscreensaver-6.00 and xscreensaver-6.04.
I have pushed an update that includes additional Arch logos to replace the new xscreensaver ones. Let me know if that resolves your issue.
Is it just me, or has this package not been displaying the Arch logo for quite some time now? Is there a configuration setting that needs to be adjusted to get it to display the Arch logo instead of the xscreensaver one?
Hi, this package is recommended in the wiki.
Initially I had an error, installing via ssh. using the terminal on the actual device it worked fine.
Thank you for maintaining this package.
Pinned Comments
morgenstern commented on 2025-07-05 10:05 (UTC) (edited on 2025-07-05 12:33 (UTC) by morgenstern)
Please note that the
PKGBUILDfor version 6.11 includes the build option--enable-pam-check-account-type(see here and here).If you get the message "password initialization failed" when trying to unlock your screen, then you may need to uncomment the following line in
/etc/pam.d/xscreensaver: