[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kscreensaver] [Bug 86195] wish: kscreensaver should "play nicely" with xscreensaver
From:       Martin Gräßlin <mgraesslin () kde ! org>
Date:       2015-01-23 12:14:38
Message-ID: bug-86195-17878-X3BgIiGSIk () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=86195

--- Comment #19 from Martin Gräßlin <mgraesslin@kde.org> ---
> > There won't be a config interface for other screen locker implementations.
> 
> Now I see where we are missing one another. I'm not asking for Kscreensaver
> to provide a configuration interface for other systems.
> 
> I'm asking that, when Kscreensaver detects something else is already
> running, it should simply advise the user not to configure Kscreensaver
> itself in addition.

that is what I consider as configuring other applications. This is completely 
out of scope for the locker.

> 
> As a general rule, all you have to check for is "ps aux | grep screensaver",
> since almost everything else uses either xscreensaver or (possibly)
> gnome-screensaver. (and in general, it's xscreensaver which is the
> cross-platform one which can be used under any Desktop).
> 
> Also, please remember that many people use KDE piecemeal - according to the
> Unix philosophy. We don't all think of it as a monolithic "Plasma", we think
> of it as a window manager + panel + some extras.

Just because people do, does not mean that we have to implement it.

Once again: this won't be implemented by the maintainer. If you come up with a 
patch we will judge it. But don't expect us to implement support for workflows 
we do not want to support.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]