Bug 517391

It works for me on F-11, lemme test my F12 live image...

You *may* be experiencing side effects of a prelink bug #515539

Confirmed ok here for rawhide too.

(In reply to comment #2)
> Confirmed ok here for rawhide too.  

My guess is it's the presence of xscreensaver-base. Is that installed in your test systems?

(In reply to comment #3)
> (In reply to comment #2)
> > Confirmed ok here for rawhide too.  
> 
> My guess is it's the presence of xscreensaver-base. 

.. and xscreensaver-* was pulled in because of kdeartwork-kxs deps, and that was needed by kdeartwork-screensavers, which only got pulled in because I did "yum groupinstall "KDE (K Desktop Environment)". Yuk.

yum -y erase xscreensaver\*
solved the problem.

fair nuf, I only tested the tried-n-true "blank" screensaver.

I'll test xscreensaver-based ones too.  In particular, which ones did you try?

(In reply to comment #5)
> fair nuf, I only tested the tried-n-true "blank" screensaver.
> 
> I'll test xscreensaver-based ones too.  In particular, which ones did you try?  

I believe this machine had only been set to Random.

Ping

-- 
Steven M. Parrish - KDE Triage Master
                  - PackageKit Triager
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

we probably want someone (on rawhide) to test/verify this or close worksforme.

I just reproduced this on rawhide, similar to my statements above:
- take normally running KDE system, but without packages below
- yum groupinstall "KDE (K Desktop Environment)"
[for example. ymmv]
yum then installed:

polkit-gnome
kdeartwork-screensavers
xscreensaver-extras
kdeartwork-kxs
xscreensaver-base
xscreensaver-gl-base
xscreensaver-gl-extras

Voilà! Normal, no password KDE, screensaver is now partnered with X screensaver and the ugly password prompt I didn't ask for.

Ping?

-- 
Steven M. Parrish - KDE Triage Master
                  - PackageKit Triager
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

(In reply to comment #10)
> Ping?

Still present in the current rawhide.
Reproduced it by:
1. adding a new test user. [this seemed to be a key point]
2. login as new user.
3. in system settings - screensaver, note nothing is checked by default.
4. exit system settings and do nothing on the system
[optionally, open konsole and observe the running "xscreensaver -nosplash" process started by kdeinit4.

(In reply to comment #11)
> (In reply to comment #10)
> > Ping?
> 
> Still present in the current rawhide.
> Reproduced it by:
> 1. adding a new test user. [this seemed to be a key point]

Not needed, I just realized. Just by setting 
After: in systemsettings low enough, the xscreensaver will kick in over the KDE version.

See, that's the problem.  There should be no xscreensaver running.

OK then, kdeinit4 started it, so I'm changing the component.
# ps -ewwf |  grep -E '(screen|kdeinit4 Running)'
dtilocal  7223     1  0 11:29 ?        00:00:00 kdeinit4: kdeinit4 Running...
dtilocal  7281  7223  0 11:29 ?        00:00:11 xscreensaver -nosplash

I don't know how it got running for you, but I'm fairly certain nothing in kde runs xscreensaver (directly), that's the point I've been trying to make.

(In reply to comment #15)
> I don't know how it got running for you, but I'm fairly certain nothing in kde
> runs xscreensaver (directly), that's the point I've been trying to make.  

The source indicates otherwise:
$ grep -r xscreensaver rpmbuild/BUILD/kdeartwork-4.3.1/ 2> /dev/null | wc -l
257

As the sequence of this bug indicates, it's not *me* running xscreensaver. That's the point I'm trying to make. :-)

Try again,

grep -r nosplash rpmbuild/BUILD/kdeartwork-4.3.1/ 2> /dev/null | wc -l

Of course, there are xscreensaver references, but kde launches them, just not via the xscreensaver binary.

Arg, looks like xscreensaver is autostarting itself on F12+.  boo, bad form.

Re-assigning to xscreensaver, for comment.

methinks the autostart .desktop file best include
NotShowIn=KDE

Or perhaps a
OnlyShowIn=...
so only the desktops that want/need this get it, minimizes surprises (like this one).

(In reply to comment #17)
> Try again,
> 
> grep -r nosplash rpmbuild/BUILD/kdeartwork-4.3.1/ 2> /dev/null | wc -l

Thanks for the reality check. I knew something was going on, and just threw each thing out there I could think of to find it. Looks like we're on the right path now, so I've also changed the Summary.

Well, I think that KDE is the only desktop environment which does its own xscreensaver integration. GNOME does its own thing with gnome-screensaver. Still, I guess you also don't want xscreensaver to run under GNOME by default.

I'd suggest:
NotShowIn=KDE;GNOME;

(That said, I'm not familiar with how XFCE, LXDE, Sugar etc. do things, they may want xscreensaver not to run by default either.)

Please don't add words such as "recklessly"......
Please be kind to everyone.

(In reply to comment #23)
> Please don't add words such as "recklessly"......
> Please be kind to everyone.  

I'm sorry, I meant no offense.

Should be fixed in 5.10-2.fc12 (tagged as dist-f12/f12-beta), thank you.

Added OnlyShowIn=GNOME. Note that 5.10-2.fc12 has a wrapper script
and even on GNOME session xscreensaver won't start if gnome-screensaver
is installed, which is the same behavior as F-11.

Hmm. While looking into something else I notice that this appears to have reverted bug 483495 without any comments here or there to that effect. Was that deliberate?