[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:       Richard Neill <kde () richardneill ! org>
Date:       2015-01-23 10:49:56
Message-ID: bug-86195-17878-vi4FjOUyk3 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #16 from Richard Neill <kde@richardneill.org> ---
> but it's not our task to implement support for all competitive screen lockers.

However, may I suggest that it *is* KDE's task not to confuse the user. I have
seen several occasions where the system admin had set up xscreensaver (or
light-locker) and the user then gets confused, and goes into KDE system
settings and tries to configure it. The worst usability muddle is when the user
ends up running 2 screensavers.

All that is necessary is a very simple code change:
   In the systemsettings screensaver module,   pgrep for the other screensaver
processes.
   If one is running, show this message:
   "You are already running a screensaver ($name). You should not configure the
KDE screensaver as well".

This will take less time to code than to discuss, and will have zero impact on
anyone who isn't affected.  Please consider that it is massively frustrating
when software knows what's wrong, but doesn't take the time to tell the user.

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