May 2008 - openSUSE Features - openSUSE Mailing Lists

[Fate 303751] Support 802.1X Authentication on Wired Networks
by fate_noreply＠suse.de 29 May '08

29 May '08

Feature changed by: gekker Feature #303751, revision 8 Title: Support 802.1X Authentication on Wired Networks - openSUSE-11.1: New + openSUSE-11.1: Duplicate of #301902 Priority Requester: Desirable - SLED-11: New + SLED-11: Duplicate of #301902 Priority Requester: Desirable Requested by: prusnak(a)novell.com Partner organization: openSUSE.org Description: SUSE Linux does not support 802.1X authentication on Wired Networks. That means that users which need this feature have to install and configure it manually. What's even worse, users in authenticated environment cannot install SUSE from network. This feature consists of 3 tasks: 1) add suport to sysconfig/netcontrol (e.g. by calling wpa_supplicant - D wired -i eth0 -c /etc/wpa_supplicant/wpa_wired.conf in network scripts) 2) add support to NetworkManager (and its frontends - NetworkManager-gnome and NetworkManager-kde) 3) add configuration dialogs to YaST (during the installation and outside the installation - on running system) PS: Fedora Rawhide (equivalent of openSUSE Factory) already has working implementation in NetworkManager-gnome. I do not know about other tasks. Discussion: #1: snwint(a)novell.com (2008-04-30 11:01:48) We already run wpa_suplicant during installation. Could you please explain the difference to your proposal and what exactly needs to be changed? #2: prusnak(a)novell.com (2008-04-30 11:23:26) (reply to #1) I'm talking about 802.1x authentication on wired networks (Ethernet). I'm not able to enter my credentials during install phase and even worse I cannot enter them in installed system either and I have to create wpa_supplicant with credentials by hand. #3: snwint(a)novell.com (2008-04-30 12:00:41) (reply to #2) And what needs to be changed to the present wpa_supplicant call? #5: prusnak(a)novell.com (2008-04-30 13:06:57) (reply to #3) Probably nothing, but installation lacks configuration of user credentials and there seem to be no way to input them in installed system too (eg. using YaST). #4: tambet(a)novell.com (2008-04-30 13:22:45) NetworkManager does support wired 802.1x authentication (SLED10-SP2 and opensuse 11.0 beta1) and the feature request is already in FATE: 301902. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303751

1 0

[Fate 304395] Disabling (or handling) screensaver during installation
by fate_noreply＠suse.de 28 May '08

28 May '08

Feature changed by: locilka Feature #304395, revision 7 Title: Disabling (or handling) screensaver during installation openSUSE-11.1: New Priority Requester: Desirable Requested by: locilka(a)novell.com 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 + Black monitor (thread): "The screen suudenly went black" + http://lists.opensuse.org/opensuse-factory/2008-05/msg00675.html Use Case: Installation on slower computer and/or via slower network Discussion: #1: aschnell(a)novell.com (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(a)novell.com (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). #3: sh(a)novell.com (2008-05-27 16:10:19) (reply to #1) aschnell wrote: 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. When I go home during such a lengthy operation, what's wrong with simply turning the monitor off? This is the most natural and the simplest thing to do. #4: sh(a)novell.com (2008-05-27 16:18:21) See also Bug #393890 (https://bugzilla.novell.com/show_bug.cgi?id=393890) Changing screen saver settings in a widget toolkit (!) such as the YaST2 Qt UI would affect ALL applications written with that toolkit. Right now, that's all YaST2 modules, but since this UI is now available as a general toolkit, you'll never know what other applications this might affect in the future. An X11 application is not to change the user's screen saver settings (unless it is a dedicated application to configure screen saver settings, of course), much less silently in the background. We'd get a lot of surprised and very angry users, and they would have every right to be angry with us. You wouldn't even be able to find out why your screen saver doesn't work any more. #5: locilka(a)novell.com (2008-05-27 16:27:02) (reply to #4) The feature request is about installation, not about running system. But it's a good point that we should not change that in general... (the whole toolkit). Thanks. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304395

1 0

[Fate 303367] Better Beagle Acceptance
by fate_noreply＠suse.de 27 May '08

27 May '08

Feature changed by: gekker Feature #303367, revision 8 Title: Better Beagle Acceptance - openSUSE-11.0: Evaluation + openSUSE-11.0: Rejected by gekker(a)novell.com + reject date: 2008-05-27 09:03:27 + reject reason: Not done for 11.0. Priority Requester: Mandatory Projectmanager: Important + openSUSE-11.1: Evaluation + Priority + Requester: Mandatory + Projectmanager: Important + SLED-11: Evaluation + Priority + Requester: Mandatory + Projectmanager: Important Requested by: aj(a)novell.com Partner organization: openSUSE.org Description: There have been several discussions on the public openSUSE mailing lists, e.g. http://lists.opensuse.org/opensuse-factory/2008-01/msg00157.html where people complain about resource usage or garbage from beagle. I suggest that we analyze the current situation and check where are real problems and consider solutions. One option would be to make it easier for users to not enable beagle on their systems. Note: The feature request is about getting a better acceptance by our users of our indexing technology - and therefore let's figure out what are the problems they are hitting in real life. References: https://bugzilla.novell.com/show_bug.cgi?id=282678 Discussion: #1: aj(a)novell.com (2008-01-20 11:12:58) See also bug 282678. #2: aj(a)novell.com (2008-01-23 16:23:51) Note: powertop advises "Suggestion: Disable or remove 'beagle' from your system. Beagle is the program that indexes for easy desktop search, however it's not very efficient and costs a significant amount of battery life.". #3: jpr(a)novell.com (2008-01-23 10:38:58) (reply to #2) Yes, this is well known and was covered extensively last year and caused by polling for battery status in some cases. 0.3.2 uses hal to detect battery status: http://www.mail-archive.com/dashboard-hackers@gnome.org/msg03464.html #4: jpr(a)novell.com (2008-01-23 10:41:35) (reply to #3) Also part of it was a mono issue: http://www.nabble.com/Beagle-indexing-when-running-on-batteries-td13842939.… -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303367

1 0

[Fate 302957] Combined "where am I" page
by fate_noreply＠suse.de 27 May '08

27 May '08

Feature changed by: visnov Feature #302957, revision 32 Title: Combined "where am I" page openSUSE-11.0: Done Priority Requester: Mandatory Projectmanager: Important - SLED-11: Evaluation + SLED-11: Done Priority Requester: Mandatory SLES-11: Done Priority Requester: Mandatory Requested by: coolo(a)novell.com Partner organization: openSUSE.org Description: Our (openSUSE) statistics show that most of our users are not native english speakers. So I'm blindly assuming they do not have a english keyboard either and do not live in an english speaking timezone. So I want the first page to be not just the language in a blue box, but to have _one_ installation page with language, timezone and keyboard selection. These selections should depend on each other, so depending on where I click first the others change. To have a good looking addon, I picture the timezone selection as picture and not as fullscreen list boxes. Discussion: #1: coolo(a)novell.com (2007-11-09 11:48:30) An additional note, feature #302955 is related (split translations out of installation system). #2: jsrain(a)novell.com (2007-11-09 13:27:05) Isn't it easier for users who do not speak English to have the first dialog really as simple as possible (since they cannot read it)? Having just one selection box leads them straight where they need to get; I guess that most of them use mouse for installation, so keyboard is not an issue either... Also, we already have a support in isolinux to select language; then the first dialog is skipped. #3: coolo(a)novell.com (2007-11-09 14:13:14) If isolinux provides a language, then the page is not worse than the timezone page is now. Just that it also allows to change the language after the fact. If users do not grasp english _at all_, they will have a hard time booting the installation off the CD. So I would blindly assume that users have no problem with selecting Deutsch, русский or čeština when presented with a list even if they do not understand the exact context. And when next to that list is even a graphical presentation of the world, most will be able to select the part of the world they live in. #4: evamaria.fuchs(a)novell.com (2007-11-09 16:00:35) I think for the secondary target market of opensuse (first time user, home user)an installer wizard that consists of a series of screens would be convenient. Basically it's preferable that language-, time-zone- and keyboard- selection depend on each other so that modifying one will effect the others. But - as I prefer a picture (e.g. a rotating globe) for time- zone selection - sticking them together in one screen would clutter the whole thing up. #5: coolo(a)novell.com (2007-11-15 13:01:50) after some discussions with Eva, I want to reexpress my request: I want the language selection to be on one page together with license and a welcome text and the timezone dialog to be graphical and a proposed keyboard layout associated to the language from the first page. The license text doesn't have to be visible in full beauty. I talked with the lawyer and what I got was: it's ok if the license can be read, it doesn't have to optimized for scrolling. I'll work on a mockup. The challenge is that we might need a slightly different work flow for ncurses, but I think popups are ok for it. So you can write UI code, that either fills a special widget or opens a popup. #6: coolo(a)novell.com (2007-11-18 13:53:57) (reply to #5) Danger Mouse! I'm very far from a capable mockup designer. But here is my show: http://ktown.kde.org/~coolo/Namenlos.png #7: coolo(a)novell.com (2007-11-18 13:54:45) (reply to #6) Ciaran, just to verify: is this way to present the license ok? #9: cfarrell(a)suse.de (2007-11-19 08:51:13) (reply to #7) Provided that we maintain the status quo with regard to not proceeding with the installation until the user actually accepts the license. #8: coolo(a)novell.com (2007-11-18 14:39:45) (reply to #6) mocking up the timezone page, I leave to the interested reader. For reference: this is how unbuntu's installer looks like: https://help.ubuntu.com/community/GraphicalInstall?action=AttachFile&do=get… I would make the map a little smaller and do not show a region and not the name of the timezone again, but rather have the value of the combobox fill in what we have now as Europe/Berlin. Because I want a "Keyboard: English" with a little test field in there. But that is to be discussed. The main goal is to have a graphical selection instead of these fullscreen list boxes. #10: michl(a)novell.com (2007-11-19 13:28:22) Mockup looks good. And the whole thing should simplify and shorten the installation process. #11: jsrain(a)novell.com (2007-11-19 16:57:23) The timezone dialog looks good to me, however, we should not present the other one in the current form. Even if we have a different dialog for NCurses, we still must take care of Qt with the resolution of 800x600. With the current font size, the text itself will not fit into the screen if it is 800x600. Also consider the license - if one wants to read it, he wants to read a reasonable part of the license without scrolling - and not to scroll every 3rd line. IMO this suggestion puts the usability a huge step back #12: coolo(a)novell.com (2007-11-19 18:23:04) (reply to #11) damn, fate crashed on my comment ;( Again: I'm not a good designer But as a matter of fact: we do not design the default screen estate for reading the license, but of course a better design can add a popup to read the full text in full screen. #14: locilka(a)novell.com (2007-11-29 13:10:32) Additional step to help user understand where he is and what he can do there is to remove a [Show Release Notes] button and place that button to a Welcome Dialog only. The button doesn't need to occupy installation wizard screen all the time, it often rather confuses users. Frankly, this wasn't my idea but I found it useful :) ;) #15: jsuchome(a)novell.com (2007-12-20 16:19:25) Proposal of timezone dialog with a map: http://w3.suse.de/~jsuchome/screenshots/yast2-timezone-wordmap-zoomed.png BTW, it may not have a sense to offer keyboard configuration together with timezone. Keyboard layout is currently decided according to selected language, so it may better fit together with language. But the language dialog could get eventually too crowded. #16: coolo(a)novell.com (2007-12-22 14:05:24) new screenshot for the first page (I tried ycp): http://ktown.kde.org/~coolo/yast7.png Some icons and some more text would help the design I'd think. #17: coolo(a)novell.com (2008-01-08 12:40:13) http://en.opensuse.org/Image:Yast8.png is Martin's counter proposal. This one needs icons to differ the combo boxes though, but I believe a keyboard and an UN flag should make this obvious enough. #18: locilka(a)novell.com (2008-01-10 15:24:31) (reply to #17) BTW: This complex dialog will not be part of yast2-country (or similar) but directly yast2-installation because it contains more than just defining the language and keyboard settings. License handling needs to be reworked. #19: jsuchome(a)novell.com (2008-01-23 09:37:39) (reply to #18) Well, OK than. I expect you will ask for creating some API of Language (and maybe Keyboard) module, because current one probably is not sufficient. The API should be used instead writing whole stuff again separately, so we don't have the language handling on more places. #20: locilka(a)novell.com (2008-01-28 11:22:59) (reply to #19) Yes, Language API would probably help a lot. Please, propose, what you could create considering the default state at http://svn.opensuse.org/svn/yast/trunk/installation/src/clients/inst_comple… For instance, generating the combo boxes for language and keyboard selections might be moved to the API (I saw some functions in the current API though). The current implementation has been done in a hurry before the alpha deadline, it needs to be polished. Feel free to change it directly, it's open source. #21: jsuchome(a)novell.com (2008-01-28 11:32:01) (reply to #20) I agree, currently the API for generating the widget contents is needed, maybe that's all. I have to check it. #22: locilka(a)novell.com (2008-02-01 04:09:18) New "where am I page" with Language, Keyboard, and License will be in 11.0 Alpha2. #23: locilka(a)novell.com (2008-02-27 11:10:18) (reply to #22) Done in openSUSE 11.0 Alpha2 (and later). There were some bugfixes and internal changes though... -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=302957

1 0

[Fate 304395] Disabling (or handling) screensaver during installation
by fate_noreply＠suse.de 27 May '08

27 May '08

Feature changed by: locilka Feature #304395, revision 6 Title: Disabling (or handling) screensaver during installation openSUSE-11.1: New Priority Requester: Desirable Requested by: locilka(a)novell.com 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(a)novell.com (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(a)novell.com (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). #3: sh(a)novell.com (2008-05-27 16:10:19) (reply to #1) aschnell wrote: 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. When I go home during such a lengthy operation, what's wrong with simply turning the monitor off? This is the most natural and the simplest thing to do. #4: sh(a)novell.com (2008-05-27 16:18:21) See also Bug #393890 (https://bugzilla.novell.com/show_bug.cgi?id=393890) Changing screen saver settings in a widget toolkit (!) such as the YaST2 Qt UI would affect ALL applications written with that toolkit. Right now, that's all YaST2 modules, but since this UI is now available as a general toolkit, you'll never know what other applications this might affect in the future. An X11 application is not to change the user's screen saver settings (unless it is a dedicated application to configure screen saver settings, of course), much less silently in the background. We'd get a lot of surprised and very angry users, and they would have every right to be angry with us. You wouldn't even be able to find out why your screen saver doesn't work any more. + #5: locilka(a)novell.com (2008-05-27 16:27:02) (reply to #4) + The feature request is about installation, not about running system. + But it's a good point that we should not change that in general... (the + whole toolkit). Thanks. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304395

1 0

[Fate 304395] Disabling (or handling) screensaver during installation
by fate_noreply＠suse.de 27 May '08

27 May '08

Feature changed by: sh Feature #304395, revision 5 Title: Disabling (or handling) screensaver during installation openSUSE-11.1: New Priority Requester: Desirable Requested by: locilka(a)novell.com 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(a)novell.com (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(a)novell.com (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). + #3: sh(a)novell.com (2008-05-27 16:10:19) (reply to #1) + aschnell wrote: + 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. + When I go home during such a lengthy operation, what's wrong with + simply turning the monitor off? This is the most natural and the + simplest thing to do. + #4: sh(a)novell.com (2008-05-27 16:18:21) + See also Bug #393890 + (https://bugzilla.novell.com/show_bug.cgi?id=393890) + Changing screen saver settings in a widget toolkit (!) such as the + YaST2 Qt UI would affect ALL applications written with that toolkit. + Right now, that's all YaST2 modules, but since this UI is now available + as a general toolkit, you'll never know what other applications this + might affect in the future. + An X11 application is not to change the user's screen saver settings + (unless it is a dedicated application to configure screen saver + settings, of course), much less silently in the background. We'd get a + lot of surprised and very angry users, and they would have every right + to be angry with us. You wouldn't even be able to find out why your + screen saver doesn't work any more. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304395

1 0

[Fate 304395] Disabling (or handling) screensaver during installation
by fate_noreply＠suse.de 27 May '08

27 May '08

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(a)novell.com 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(a)novell.com (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(a)novell.com (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

1 0

[Fate 304395] Disabling (or handling) screensaver during installation
by fate_noreply＠suse.de 27 May '08

27 May '08

Feature changed by: aschnell Feature #304395, revision 2 Title: Disabling (or handling) screensaver during installation openSUSE-11.1: New Priority Requester: Desirable Requested by: locilka(a)novell.com 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(a)novell.com (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. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304395

1 0

[Fate 304429] Package cache handling in yast
by fate_noreply＠suse.de 27 May '08

27 May '08

Feature added by: lslezak Feature #304429, revision 1 Title: Package cache handling in yast openSUSE-11.1: New Priority Requester: Important SLES-11: New Priority Requester: Important Requested by: lslezak(a)novell.com Partner organization: openSUSE.org Description: Add a possibility to edit 'keeppackages' option in *.repo files. The downloaded packages are not kept by default, but it should be configurable by user. The question is how it should be configurable. My suggestions are a check box or an extra menu item in the repositoru manager (repositories.ycp) . References: https://bugzilla.novell.com/show_bug.cgi?id=393709 -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304429

1 0

[Fate 304395] Disabling (or handling) screensaver during installation
by fate_noreply＠suse.de 26 May '08

26 May '08

Feature added by: locilka Feature #304395, revision 1 Title: Disabling (or handling) screensaver during installation openSUSE-11.1: New Priority Requester: Desirable Requested by: locilka(a)novell.com 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 -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=304395

1 0