- openSUSE Features

[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

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

30 Apr '08

Feature changed by: prusnak Feature #303751, revision 7 Title: Support 802.1X Authentication on Wired Networks openSUSE-11.1: New Priority Requester: Desirable SLED-11: New 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 303751] Support 802.1X Authentication on Wired Networks
by fate_noreply＠suse.de 30 Apr '08

30 Apr '08

Feature changed by: tambet Feature #303751, revision 6 Title: Support 802.1X Authentication on Wired Networks openSUSE-11.1: New Priority Requester: Desirable SLED-11: New 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? + #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 303751] Support 802.1X Authentication on Wired Networks
by fate_noreply＠suse.de 30 Apr '08

30 Apr '08

Feature changed by: snwint Feature #303751, revision 5 Title: Support 802.1X Authentication on Wired Networks openSUSE-11.1: New Priority Requester: Desirable SLED-11: New 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? -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303751

1 0

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

30 Apr '08

Feature changed by: prusnak Feature #303751, revision 4 Title: Support 802.1X Authentication on Wired Networks openSUSE-11.1: New Priority Requester: Desirable SLED-11: New 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. -- SUSE Feature Tool: http://partnerfate.suse.de/?rm=feature_show&id=303751

1 0