Setting splash to False has no effect on outdated-messages

Bug #1407119 reported by Removed by request
10
Affects Status Importance Assigned to Milestone
xscreensaver (Debian)
Fix Released
Unknown
xscreensaver (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm using Ubuntu 15.04 dev with xscreensaver 5.26-1ubuntu3 and currently I'm seeing the message "WARNING: This version is very old!
Please upgrade!" on every login on my desktop even if the option splash is set to False. Because this message is affected by the option splashDuration I'm assuming it should also be affected by the option splash.

Revision history for this message
Jamie Zawinski (jwz) wrote : Re: [Bug 1407119] [NEW] Setting splash to False has no effect on outdated-messages

Here's a better idea -- why don't you switch to a distro that doesn't force software on you that is thirteen months old and six releases behind?

It is unconscionable that your distro is making their users deal with bugs that were fixed *years* before. That's a despicable way to treat the users (you) and the developers (me).

Revision history for this message
Jamie Zawinski (jwz) wrote :

If your distro refuses to ship current versions of my software, then my preference is that your distro not ship my software at all.

I'm completely serious. If you're not going to keep xscreensaver up to date, then I request that you please remove xscreensaver from your distro.

Revision history for this message
Removed by request (removed3425744) wrote :

While I agree that it would be nice to have up to date software there is still a bug (except "It is unconscionable that your distro is making their users deal with bugs that were fixed *years* before." means that this bug is already fixed in a newer version) that could also trigger in an up to date version of xscreensaver.

Revision history for this message
Jamie Zawinski (jwz) wrote : Re: [Bug 1407119] Setting splash to False has no effect on outdated-messages

The only bug here is that your distro is not shipping up-to-date software.

xscreensaver is behaving as intended.

Revision history for this message
Removed by request (removed3425744) wrote :

> xscreensaver is behaving as intended.

And what if the system clock of a system with an up to date xscreensaver gets changed while the option splash is set to False? Or what if the development gets inactive for a too long time? Would xscreensaver then show the message too?

Revision history for this message
Jamie Zawinski (jwz) wrote :

You should probably ask these questions here: https://what-if.xkcd.com/

Revision history for this message
Fefu (fefu) wrote :

I've found a workaround. You can modify the file ~/.xscreensaver . The variable
  splash: True
should be switched to
  splash: False

You can do it by hand with
  # nano ~/.xscreensaver

or by executing these two lines which will make a backup (~/.xscreensaver.old) of the original configuration file and filter it with sed to place the modified version in the place of the previous one:
# cp ~/.xscreensaver ~/.xscreensaver.old
# sed 's/splash:.*/splash: False/' ~/.xscreensaver.old > ~/.xscreensaver

Once you are satisfied with the results, you can remove the backup file with
# rm ~/.xscreensaver.old

Revision history for this message
Removed by request (removed3425744) wrote :

Are you sure that you have tested this against an outdated-message and not another message? Because this problem was reported because setting the option splash to False did not solve this issue.

Changed in xscreensaver (Debian):
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.