Mailinglist Archive: opensuse-features (10 mails)

[fate_noreply@xxxxxxx]

Feature changed by: locilka
Feature #304395, revision 3
  Title: Disabling (or handling) screensaver during installation
   
  openSUSE-11.1: New
  Priority
      Requester: Desirable
   
  Requested by: locilka@xxxxxxxxxx
  Partner organization: openSUSE.org
   
Description:
  We currently have screen-saver active during installation/upgrade. This
  is a bit problematic when some exception occurs and opens a pop-up
  window requesting some user-decision (Abort/Retry/Ignore/...).
  On slower networks, installation can take tens of minutes, even a few
  hours. It would be nice to disable the screen-saver (easy) or at least
  handle all the exceptions by disabling the screen-saver.
   
  References:
  Bug 393890 - How to disable screen blank during installation
  https://bugzilla.novell.com/show_bug.cgi?id=393890
   
  Use Case:
  Installation on slower computer and/or via slower network
   
  Discussion:
  #1: aschnell@xxxxxxxxxx (2008-05-27 15:10:07) 
  On slow computers people might actually want the screensaver. Suppose
  you start the installation and go home or sleeping: I would expect that
  the monitor powers off after some time.
  We could add a call "xset dpms force on" to popups. But I doubt that
  this is worth the effort.
   
+ #2: locilka@xxxxxxxxxx (2008-05-27 15:43:16) (reply to #1)
+ Bug 393890 says exactly:
+ During installation the screen will blank when for some period no
+ keyboard and
+   mouse activity is recognized. The drawback is, that you will not
+ notice error
+   messages that pop up. So one has to move the mouse every 5 minutes or
+ so and is
+   bound to the installation.
+   It would be cool, if we could
+   either do not blank the screen at all,
+   or "deblank" it, when a error message pops up.
+ ... and Stefan Hundhammer adds:
+ The screen saver should be off during installation. Why would there be
+ any
+   exception to this rule? (It's not even that screen savers serve their
+ real
+   purpose these days - it was an issue with old (very old) CRT monitors
+ that
+   could "burn in" images that would be displayed for a long, long time -
+ and
+   then, we are talking about months, not about hours).
   
   

-- 
SUSE Feature Tool: 
http://partnerfate.suse.de/?rm=feature_show&id=304395