October 2016 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 309353] Make hermes working on local OBS installations
by fate_noreply＠suse.de 18 Apr '17

18 Apr '17

Feature added by: Adrian Schröter (adrianSuSE) Feature #309353, revision 1 Title: Make hermes working on local OBS installations Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: We need to * be able to run without iChain * package Hermes * configure it to be easy usable with OBS. -- openSUSE Feature: https://features.opensuse.org/309353

1 2

[openFATE 307597] Courgette
by fate_noreply＠suse.de 18 Apr '17

18 Apr '17

Feature added by: T. J. Brumfield (enderandrew) Feature #307597, revision 1 Title: Courgette openFATE: Unconfirmed Priority Requester: Important Requested by: T. J. Brumfield (enderandrew) Description: Utilize Courgette for binary diff packages. * This will save on bandwidth costs for Novell and mirrors. * This will make updating quicker and easier for end-users. * This will especially benefit users who have capped bandwidth for downloading updates from their ISPs. * By making the update process easier, it encourages users to stay up-to-date, making systems more secure. http://dev.chromium.org/developers/design-documents/software-updates-courge… (http://dev.chromium.org/developers/design-documents/software-updates-courge…) -- openSUSE Feature: https://features.opensuse.org/307597

1 7

[New: openFATE 309701] osc blame
by fate_noreply＠suse.de 18 Apr '17

18 Apr '17

Feature added by: Ludwig Nussel (lnussel) Feature #309701, revision 1 Title: osc blame Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Description: a feature like "osc blame" or "osc annotate" would be nice to find out who changed what and when -- openSUSE Feature: https://features.opensuse.org/309701

1 3

[New: openFATE 313282] Full automated setup for printers in the network
by fate_noreply＠suse.de 20 Mar '17

20 Mar '17

Feature added by: Johannes Meixner (jsmeix) Feature #313282, revision 1 Title: Full automated setup for printers in the network openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Johannes Meixner (jsmeix) Partner organization: openSUSE.org Description: I would like to have it evaluated whether or not and/or to what extent it is possible to setup printer devices which are accessible via network in a full automated way. The basic idea behind: For locally connected USB printers there is already full automated setup. I would like to have it evaluated if and/or to what extent this could be extended reagarding printer devices which are accessible via network. FYI: For printer devices which are accessible via a CUPS server there is nothing to do because this works already via the so called "CUPS Browsing". Some use cases: Network printer) A network printer is a printer with a built-in network interface so that the printer device is directly accessible via network. The problem regarding full automated setup is how to autodetect the printer model so that the right driver for this model can be set up. Therefore the problem is how to autodetect the parinter model on a printer device which is directly accessible via network. Usually this is possible via some generic SNMP query. The CUPS tool "lpinfo -l -v" results this for the "socket" device URI e.g.: # lpinfo -l -v Device: uri = socket://10.10.2.92 make-and-model = HP LaserJet 4050 Series Device: uri = lpd://10.10.4.4/ make-and-model = Kyocera FS-C5100DN SMB) A printer device which is accessible via a SMB printer share: In this case the client system must submit readymade printer specific data to the SMB share (i.e. there is no so called "filtering" on a SMB print server). Therefore on the client system usually a printer driver must run. If it is a PostScript printer, the client must at least provide generic PostScript (e.g. when printing image data it must be converted into PostScript on the client system). The problem regarding full automated setup is how to autodetect the printer model so that the right driver for this model can be set up but the printer device is "hidden" behind the SMB share. Therefore the problem is how to autodetect the parinter model via a SMB share. -- openSUSE Feature: https://features.opensuse.org/313282

1 10

[openFATE 306528] Info banner for projects/packages
by fate_noreply＠suse.de 12 Mar '17

12 Mar '17

Feature added by: Jan-Simon Möller (dl9pf) Feature #306528, revision 1 Title: Info banner for projects/packages Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Jan-Simon Möller (dl9pf) Description: I'd propose to add an info banner (as on the monitor page - aka "Adrians Blog" ;) ) to the projects or even packages. This would allow the new groups of packagers to leave status messages right in place for the projects. -- openSUSE Feature: https://features.opensuse.org/306528

1 4

[New: openFATE 321407] Add support for dnscrypt and dnssec
by fate_noreply＠suse.de 20 Feb '17

20 Feb '17

Feature added by: Alfredo Amaya (alfre2) Feature #321407, revision 1 Title: Add support for dnscrypt and dnssec Requested by: Alfredo Amaya (alfre2) Partner organization: openSUSE.org Description: You need to add an third party repository to install dnscrypt and dnssec for encrypting and validating DNS queries. The main repository lacks both packages. Business case (Partner benefit): openSUSE.org: Encrypting DNS queries is an important step forward for improving privacy. It's a reliable and fast service nowadays and is becoming popular. Besides, DNSSEC acts as a complement ensuring the content of these queries. Right now there's an unofficial repository providing these packages: http://download.opensuse.org/repositories/server:/dns/openSUSE_42.1/ -- openSUSE Feature: https://features.opensuse.org/321407

1 2

[New: openFATE 320755] Warn the user with a popup that the profile A2DP is required for HIFI
by fate_noreply＠suse.de 19 Feb '17

19 Feb '17

Feature added by: Stakanov Schufter (stakanov) Feature #320755, revision 1 Title: Warn the user with a popup that the profile A2DP is required for HIFI openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Stakanov Schufter (stakanov) Partner organization: openSUSE.org Description: Currently when connecting a BT headset they do default to HSP/HFP. This will be O.K. if the user wants to use VOIP. However the main part of BT Headsets support now the profile A2DP. While it may be to early to default to it, it would be good to have a pop-up when pairing or an explanation in BT setup that for HIFI you have to set the profile to A2DP. Otherwise you will get a garbled output. Besides on my machine it was necessary to first pair, restart one time the system and then only it was possible to change the profile to A2DP. So at least for leap, the support and switching to A2DP should be looked after too. Use Case: consumer connects a BT headset Business case (Partner benefit): openSUSE.org: A first time BT user could think that a) linux cannot provide hifi output to BT headsets b) will not find easily the solution if not explained because users do not find / know about audio profiles c) may have a negative use experience for a longer time period BT Headset should be "pair-and-you-go" as much as possible. -- openSUSE Feature: https://features.opensuse.org/320755

1 1

[New: openFATE 319627] Minimal KDE and GNOME installation option
by fate_noreply＠suse.de 19 Feb '17

19 Feb '17

Feature added by: Arnold Mesper (amesper) Feature #319627, revision 1 Title: Minimal KDE and GNOME installation option openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Arnold Mesper (amesper) Partner organization: openSUSE.org Description: The installer must provide an option to install a minimal KDE and a minimal GNOME desktop in addition to the current KDE and GNOME desktop options, which install a lot of software. A minimal GNOME desktop should, for example, only install the software necessary to boot the system, login into GNOME and the GNOME shell. In addition it should include drivers only for hardware that is available on the system and corresponding configuration software (e.g. network manager if network card is installed) and the package manager in order to install additional software as required either from DVD or via internet. It must also include and enable security software (e.g. AppArmor, Firewall), thus the system is secured from the beginning. What a minimal GNOME desktop should not have: - hardware drivers for hardware that is not available (e.g. bluetooth) or has been disabled in the BIOS (e.g. WLAN, web cam, etc.) - software that can be easily installed afterwards (e.g. office suite, web browser, e-mail client, chat client, terminals, file managers, text editors, character maps, etc.) - software which is not intended for a minimal desktop (e.g. server software, development software) - Java, Flash There is also a grey zone of software, that might be useful, but should not be mandatory part of a minimal install (e.g. Avahi). Here the user should be shown with a list of software recommendations (with description) during the installation, which he must explicitly enable to be installed. Use Case: Use Case 1: Install a clean GNOME or a clean KDE desktop as a host for virtual machines. After installing the minimal desktop, the user only needs to install VirtualBox. Use Case 2: Install a clean GNOME or a clean KDE desktop as a virtual machine guest and install the required software afterwards. E.g. easily install a web browser VM or a mail client VM or an office VM. Business case (Partner benefit): openSUSE.org: For novice users the current desktop options full with software are good choice as they do not need to think about what to install. For expert users the openSUSE has the wonderful possibility to customize the system to be installed by selecting / deselecting software. I think this is the biggest plus of openSUSE in comparison to other distributions. But what is lacking is an interim solution for advanced users, that only want to install a clean KDE or GNOME desktop and decide on what additional software to install afterwards. This is especially when working with virtual machines, it is very useful to have an option to install a clean desktop without much effort. -- openSUSE Feature: https://features.opensuse.org/319627

1 4

[New: openFATE 313272] zypper: Display vendor when newer package is offered by different vendor
by fate_noreply＠suse.de 11 Feb '17

11 Feb '17

Feature added by: Richard Bos (rbos) Feature #313272, revision 1 Title: zypper: Display vendor when newer package is offered by different vendor openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Richard Bos (rbos) Partner organization: openSUSE.org Description: >From the output below it is not clear which other vendor offers the newer package version: # zypper in curl Loading repository data... Reading installed packages... 'curl' is already installed. There is an update candidate for 'curl', but it is from different vendor. Use 'zypper install curl-7.23.1-72.1.x86_64' to install this candidate. Resolving package dependencies... Nothing to do. It is useful to know which other vendor(s) offers the newer package to dertermine if the package should be used. 2) Is it possible to devide the string over 2 lines, it is now 1 long line, like this: There is an update candidate for 'curl', but it is from different vendor. Use 'zypper install curl-7.23.1-72.1.x86_64' to install this candidate. With 2 lines it becomes: There is an update candidate for 'curl', but it is from different vendor. Use 'zypper install curl-7.23.1-72.1.x86_64' to install this candidate. Use Case: zypper up shows: zyp up Loading repository data... Reading installed packages... The following package updates will NOT be installed: ..extreme-tuxracer...<many other packages> Nothing to do. Select extreme-tuxracer to investigate why they are not installed: # zyp in extreme-tuxracer Loading repository data... Reading installed packages... 'extreme-tuxracer' is already installed. There is an update candidate for 'extreme-tuxracer', but it is from different vendor. Use 'zypper install extreme-tuxracer-0.4-118.1.x86_64' to install this candidate. Resolving package dependencies... Nothing to do. One details is missing the name of the vendor. Business case (Partner benefit): openSUSE.org: Give the user the necessary information to be able to judge if he / she wants this newer package version from the other vendor or not. -- openSUSE Feature: https://features.opensuse.org/313272

1 1

[New: openFATE 308685] Gnome Slab's More Applications not open another Window
by fate_noreply＠suse.de 11 Feb '17

11 Feb '17

Feature added by: Drew Kwashnak (dragonbite) Feature #308685, revision 1 Title: Gnome Slab's More Applications not open another Window Package Wishlist: Unconfirmed Priority Requester: Desirable Requested by: Drew Kwashnak (dragonbite) Partner organization: openSUSE.org Description: In the Gnome Slab, if the Application has not been pinned to the Favorites you are forced to click "More Applications" and it opens up a Window. Maybe this could open a window like Windows XP does? Or can slide to the side like KDE 4 does? Something should be in place by default. Is there something called "Lancelot" which would apply here, or is just KDE? Business case (Partner benefit): openSUSE.org: The opened window may get lost in Windows, can be easily pushed behind something else or a pushy application that finally loads may pop-up over it and otherwise be annoying. -- openSUSE Feature: https://features.opensuse.org/308685

1 4

[New: openFATE 312871] Auto-lock with password when screen saver kicks in.
by fate_noreply＠suse.de 11 Feb '17

11 Feb '17

Feature added by: Per Jessen (pjessen) Feature #312871, revision 1 Title: Auto-lock with password when screen saver kicks in. openSUSE 12.1: Unconfirmed Priority Requester: Important Requested by: Per Jessen (pjessen) Partner organization: openSUSE.org Description: * Enable automatic screen-lock with password required. E.g. after 5mins and 10seconds respectively. * add a default "lock" button to the GUI taskbar Business case (Partner benefit): openSUSE.org: To increase security. We have many and varied security-related features and policies. Requiring a password when the screen auto-locks is just common sense. An easily accessible lock button makes it more likely that a user will use it when he leaves his desk. These both ought to be the default setup. -- openSUSE Feature: https://features.opensuse.org/312871

1 8

[New: openFATE 312873] Login screen after lock screen
by fate_noreply＠suse.de 11 Feb '17

11 Feb '17

Feature added by: Christian Giorgio galeffi (gallochri) Feature #312873, revision 1 Title: Login screen after lock screen openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Christian Giorgio galeffi (gallochri) Partner organization: openSUSE.org Description: Why does not require a password to unlock the screen with the same login screen of KDM or GDM, instead of a dialog box? Such as Windows XP. -- openSUSE Feature: https://features.opensuse.org/312873

1 4

[New: openFATE 320696] Provide interface to show worker capabilities
by fate_noreply＠suse.de 27 Jan '17

27 Jan '17

Feature added by: Adrian Schröter (adrianSuSE) Feature #320696, revision 1 Title: Provide interface to show worker capabilities Buildservice: New Milestone: 2.8 Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: To be able to define proper constraints it is important which capabilities exists. The minimum approch would be to provide the data from /srv/obs/workers directory via the api. Means listing the workers and offer to show (a filtered?) the list of capabilities. A webui for this would be very nice too. -- openSUSE Feature: https://features.opensuse.org/320696

1 2

[New: openFATE 309393] Make "unpublish" files and removing files from :full tree easy
by fate_noreply＠suse.de 27 Jan '17

27 Jan '17

Feature added by: Adrian Schröter (adrianSuSE) Feature #309393, revision 1 Title: Make "unpublish" files and removing files from :full tree easy Buildservice: New Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Description: Currently it is quite complex to remove build results from public repo or :full repo tree, if you do not want to remove the source package. We need to extend wipebinaries call with a target for :full and :repo dir and make this easy accessable via osc and webui. -- openSUSE Feature: https://features.opensuse.org/309393

1 6

[New: openFATE 321753] working dmesg in installer
by fate_noreply＠suse.de 17 Jan '17

17 Jan '17

Feature added by: Michal Suchanek (michals) Feature #321753, revision 1 Title: working dmesg in installer Requested by: Michal Suchanek (michals) Partner organization: openSUSE.org Description: In the installer dmesg buffer is empty. This is different from every Linux and BSD distribution I tried so far, even installers. In order to not alienate people who are not running SUSE from the very start the kernel messages should be left in said buffer for everyone to look at when needed. Supposedly there are these messages on virtual terminal 4 and /var/log/boot.msg Virtual terminal 4 is not accessible when installing - over ssh - over serial console - over IPMI which are probably scenarios for which SUSE should care more than most distributions out there given the focus on server. /var/log/boot.msg is either misnamed or it contains only the kernel messages from system startup and not messages which result from inserting a device for example. -- openSUSE Feature: https://features.opensuse.org/321753

1 1

[New: openFATE 313441] Easy Upgrade
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Mário Castanheira (SpeccyMan) Feature #313441, revision 1 Title: Easy Upgrade openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Mário Castanheira (speccyman) Partner organization: openSUSE.org Description: An easy way to allow users to make upgrades (e.g.: changing from version 12.1 to version 12.2) as easy as they can in Ubuntu. Something like one-click, instead of having to deal whit the work of disable and update of the repositories manually. Would be good if all this would be automatic and maybe even integrated it into the new Software Center. Use Case: User gets notified that there's a new version of opensuse available and it is asked if he wishes to upgarde. If he selects "upgrade" the system should ask for permissions and then start upgrading itself. (pretty much like in ubuntu). Nothing else required! Business case (Partner benefit): openSUSE.org: Because it will invite users to keep their distro in it's last version, even if they don't understand much about computers! And because it's something all Ubuntu users keep saying it's one of their loved features. -- openSUSE Feature: https://features.opensuse.org/313441

1 34

[New: openFATE 310405] yast2 wagon should be a fully graphic upgrade tool
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Greg Freemyer (gregfreemyer) Feature #310405, revision 1 Title: yast2 wagon should be a fully graphic upgrade tool openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Greg Freemyer (gregfreemyer) Description: I really like it that yast2-wagon exists for users to upgrade from release to release. It effectively does a zypper dup, but via a nicer gui interface. The trouble in my mind is that it still takes way to many seperate steps as is. Quoting just the top level details from http://old-en.opensuse.org/Wagon === 1) Ensure you have yast2-wagon installed 2) As of openSUSE 11.2 Wagon will update the upgrade stack as part of its automated process, so there is no need to ensure you have run zypper up or equivalent 3) Ensure you have the the correct repositories enabled 4) Start YaST2 wagon 5) Follow the dialogs 6) reboot === Taking those steps one at a time: 1) yast2-wagon should be part of the standand yast pattern in my opinion. It currently is not, so it has to be separately installed which makes little sense for a tool designed to simplify the upgrade process. 2) That was a great improvement that went into 11.2, so I'm happy. (Other than the current bugzilla against the yast2-wagon dependencies in the 11.3 release. I wish that would be fixed.) 3) It would be great if yast2-wagon would launch with a user selectable distro to upgrade to. Then once a user selected 11.4 as an example, it would walk the user through upgrading his repos to the 11.4 compatible ones. 4) Once 3) is incorporated it would be great to get a easy to click icon for wagon either within yast itself, or on the system menus. 5) This appears to be an effort to achieve automatic repo updates, but I'm not sure. Unfortunately, the above can be implemented for the 11.3 => 11.4 upgrade but only if the upgraded yast2-wagon is released via online update. That is because it involves updating the repo handling prior to pulling down a new copy of wagon from the 11.4 repos. -- openSUSE Feature: https://features.opensuse.org/310405

1 4

[openFATE 308189] Consolidating terminology: update and upgrade
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Karl Eichwalder (keichwa) Feature #308189, revision 1 Title: Consolidating terminology: update and upgrade openSUSE-11.3: New Priority Requester: Mandatory Requested by: Karl Eichwalder (keichwa) Partner organization: openSUSE.org Description: In the past, we just used the term "update" for all update related things, because we were told "upgrade" is suitable for hardware related upgrades only. With the advent of zypper, the term "upgrade" (dup, dist-upgrade) is back for upgrading the system complete from one version "n" to the next version "n+1" (yes, you can "upgrade" within one version, but that's a special case...). The term is fine and I'd like us to use "upgrade" in YaST and everywhere else where suitable. Business case (Partner benefit): openSUSE.org: Avoid confusion. ATM, I'm force to use different terms in the chapter of the manual, if I describe the same task. -- openSUSE Feature: https://features.opensuse.org/308189

1 13

[New: openFATE 312799] Safer distribution updates
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Duncan Mac-Vicar (dmacvicar) Feature #312799, revision 1 Title: Safer distribution updates openSUSE Distribution: New Priority Requester: Desirable Requested by: Duncan Mac-Vicar (dmacvicar) Product Manager: Michael Elliott (mge) Developer: ma ds (ma) Partner organization: openSUSE.org Description: Currently the documentation says that to do a distribution upgrade you should first update your software stack to the target distribution, then do a zypper dup. The software stack update can already kill your system. zypper could allow an option that makes it first install a miniroot containing the update stack itself, then automatically switch over to the miniroot to do the "zypper dup". Use Case: Bob wants to migrate his server from SLE12 to SLE13. Upgrading the package management stack fails, but he keeps his original system untouched. Business case (Partner benefit): openSUSE.org: Failsafe migrations for SLE -- openSUSE Feature: https://features.opensuse.org/312799

1 18

[openFATE 308147] Simplify "Online update" in Yast
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Birger Kollstrand (MrKane) Feature #308147, revision 1 Title: Simplify "Online update" in Yast openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Birger Kollstrand (mrkane) Description: In 11.2 there are two Online Update applications - one for configuration of online update - one for doing a manual online update I suggest that this is merged to one application which looks mostly like todays "Online update configureation" but has an aditional button on the page that when pushed does an online update. This will simplify the Yast GUI. -- openSUSE Feature: https://features.opensuse.org/308147

1 1

[New: openFATE 316789] Fundamental re-design how to set up the whole printing stuff
by fate_noreply＠suse.de 10 Jan '17

10 Jan '17

Feature added by: Johannes Meixner (jsmeix) Feature #316789, revision 1 Title: Fundamental re-design how to set up the whole printing stuff Requested by: Johannes Meixner (jsmeix) Partner organization: openSUSE.org Description: The current YaST printer module provides different buttons (i.e. entry points) with different workflows for the different kind of printing setup actions: One via "Add", one via "Printing via Network", one via "Share Printers", and so on. This means the user must know in advance what to choose for his particular kind of printing setup. The software cannot guide the user towards the right entry point according to what the user wants to get in the end. To guide the user towards an actually right solution the initial dialog should show the list of currently available print queues plus one single button to "do whatever can be done" when something is not as expected (e.g. when something is missing) in that list. This means a fundamental re-design of the dialogs and workflows to set up the whole printing stuff is needed. -- openSUSE Feature: https://features.opensuse.org/316789

1 13

[New: openFATE 321183] Add package Money Manager Ex
by fate_noreply＠suse.de 09 Jan '17

09 Jan '17

Feature added by: Jorge Vallejo (Geoplace1) Feature #321183, revision 1 Title: Add package Money Manager Ex Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Jorge Vallejo (geoplace1) Partner organization: openSUSE.org Description: http://www.moneymanagerex.org/ These is a great open source Finance Manager. Could you make it available to install on opensuse, please? Regards. -- openSUSE Feature: https://features.opensuse.org/321183

1 3

[New: openFATE 308853] Add tab-to-complete and doubletab-to-query functionality to zypper
by fate_noreply＠suse.de 19 Dec '16

19 Dec '16

Feature added by: Michael Jones (toupeiro) Feature #308853, revision 1 Title: Add tab-to-complete and doubletab-to-query functionality to zypper openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Michael Jones (toupeiro) Description: Extend zyppers command line capabilities by enabling tab to complete against indexed repository packages and doubletab-to-query to essentialy perform a zypper se on the active installation command line. This would give zypper some functionality already present in debians aptitude package management system and would increase application installs and removals from the CLI. -- openSUSE Feature: https://features.opensuse.org/308853

1 5

[New: openFATE 310883] File Integrity GUI/Nautilus/GOME/Right click
by fate_noreply＠suse.de 19 Dec '16

19 Dec '16

Feature added by: Narayansamy S (vazhavandan) Feature #310883, revision 1 Title: File Integrity GUI/Nautilus/GOME/Right click Package Wishlist: Unconfirmed Priority Requester: Important Requested by: Narayansamy S (vazhavandan) Partner organization: openSUSE.org Description: Need a file Integrity checker like a GUI pop up or right click menu in nautilus/gnome which calculates checksum so that file downloaded file intergity check can be done on the fly -- openSUSE Feature: https://features.opensuse.org/310883

1 3

[New: openFATE 310913] Add YAST module to set up multiseat installations
by fate_noreply＠suse.de 19 Dec '16

19 Dec '16

Feature added by: Matthias Schünemann (wodenhof) Feature #310913, revision 1 Title: Add YAST module to set up multiseat installations openSUSE-11.4: Unconfirmed Priority Requester: Important openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Matthias Schünemann (wodenhof) Partner organization: openSUSE.org Description: Set up a computer with a YAST module to run with multiple graphic cards, mice and keyboards for multiple users at once. The module would allow the administration of "working places". Currently one can reach sessions only on one screen via the function keys (F7 - F12). I suggest a module which lets the administrator bundle the devices into "seats", i.e. physically separated working places each with their own mouse, keyboard and display. Common use of DVD-reader/burner or card readers could be allowed, USB-sticks could e.g. get assigned hubs. Somebody (Chris Tyler) already started here: https://fedoraproject.org/wiki/Features/Multiseat (https://fedoraproject.org/wiki/Features/Multiseat) CPU-power is abundant in modern machines, so one machine has enough for the easier tasks (browsing, text input etc.) of a whole family. I'd appreciate an easy set up with this feature. Business case (Partner benefit): openSUSE.org: Use of this power in any family's home would be a powerful demonstration of this OS's qualities. It would save money, particularly nice for families with tight budgets and in developing countries. When multi seat set-ups get more common the feature could be extended to virtual machines, i.e. one machine per seat. Those could be connected (via a virtual net / sockets ...) and run future multi-player games... -- openSUSE Feature: https://features.opensuse.org/310913

1 9

[New: openFATE 314709] Remove cylinder measurement in Yast Partitioner
by fate_noreply＠suse.de 18 Dec '16

18 Dec '16

Feature added by: Roman Bysh (Romanator) Feature #314709, revision 1 Title: Remove cylinder measurement in Yast Partitioner openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Roman Bysh (romanator) Partner organization: openSUSE.org Description: I propose that openSUSE remove the use of "cylinder measurement" during the partitioning phase of installation. This is due to the fact that the newer drives use " LBA " and no longer require the outdated cylinder line up. This should be replaced with a slider that measures partitions in megabytes, gigabytes and in the near future terabytes. -- openSUSE Feature: https://features.opensuse.org/314709

1 14

[New: openFATE 310100] YaST Software Manager - Installation after download
by fate_noreply＠suse.de 18 Dec '16

18 Dec '16

Feature added by: Muhammad Javaid (BrownieCat) Feature #310100, revision 1 Title: YaST Software Manager - Installation after download openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Muhammad Javaid (browniecat) Description: Once a package install/system update has begun in Software Manager it's not very easy to stop it. The 'Abort' button doesn't really seem to work and if you force kill the process, you likely end up with broken packages. It would be nice if first all the packages were downloaded, and then installed (like it is in Ubuntu), rather than the sequence of: Download Package 1, install package 1, download package 2, install package 2 and so on. That way the installation could be aborted safely during the downloading part with no fear of broken packages. -- openSUSE Feature: https://features.opensuse.org/310100

1 4

[New: openFATE 316602] Better Appstore!
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: dillon oliviero (dillon101001) Feature #316602, revision 1 Title: Better Appstore! openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: dillon oliviero (dillon101001) Partner organization: openSUSE.org Description: It would be better to have an app store like Ubuntu software center. -- openSUSE Feature: https://features.opensuse.org/316602

1 2

[New: openFATE 316601] Better Appstore!
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: dillon oliviero (dillon101001) Feature #316601, revision 1 Title: Better Appstore! openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: dillon oliviero (dillon101001) Partner organization: openSUSE.org Description: It would be better to have an app store like Ubuntu software center. -- openSUSE Feature: https://features.opensuse.org/316601

1 3

[New: openFATE 316809] Update to newest Angelscript version
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: Hanka Bielicka (lorgenheim) Feature #316809, revision 1 Title: Update to newest Angelscript version openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Hanka Bielicka (lorgenheim) Partner organization: openSUSE.org Description: Update to newest Angelscript version Need to maintain my game on OpenSuse . Newest is 2.28.0 , so you are far behind it . -- openSUSE Feature: https://features.opensuse.org/316809

1 1

[New: openFATE 310888] We fail at...
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: tys lefering (twlevo) Feature #310888, revision 1 Title: We fail at... openSUSE.org: Unconfirmed Priority Requester: Desirable Requested by: tys lefering (twlevo) Partner organization: openSUSE.org Description: the 'startx twm' should start twm window manager but that does not work for years and needs hacking scripts to use it. twm is used to run 1 graphic program with lower mem+cpu usage during tests. -- openSUSE Feature: https://features.opensuse.org/310888

1 2

[New: openFATE 310658] bypass "partitioning" option for pre-partitioned installation targets
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: Felix Miata (mrmazda) Feature #310658, revision 1 Title: bypass "partitioning" option for pre-partitioned installation targets openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Felix Miata (mrmazda) Description: Mandriva provides installation cmdline option that I always use: readonly=1 This causes normal partitioning steps to be bypassed. No creatiion, deletion, or modification of existing partitions is possible. Instead is presented a list of Linux native partitions for mountpoint selection, mount options selection, whether to format, and format to use. This is handy for both advanced users like myself, and for frequently repeated installs, such as development milestones. It can save significant time initializing an installation, and it can avoid some opportunities for mistakes in one of the more dangerous and difficult installation phases. It would be excellent for openSUSE to have a similar installation option. -- openSUSE Feature: https://features.opensuse.org/310658

1 2

[New: openFATE 308343] external screen detection
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: marco mendoza (marcomendoza) Feature #308343, revision 1 Title: external screen detection Package Wishlist: Unconfirmed Priority Requester: Important Requested by: marco mendoza (marcomendoza) Description: Dear Suse comunity, Im proud to say Im getting involved into the Suse world, and even though Im a simple user of the OS systems, I found essential to have a performing OS in order to perform my current work. Whereas I got in love to Opensuse (I did start with it wo knowing anything...ubuntu or Suse...I have taken Suse and Im loving it), there is a couple of current options from comercial OS systems that I feel it is missing even in the last version of Opensuse. Particulary I would like to suggest the necessity of having an external screen detection system, I heart that some people manages to do it manually, but I think that such functionality should be part of an OS at the level of Opensuse. I have in in mind other couple of whishes, I will come with them in a following post in case my suggestions are taken in consideration. Thanks for commenting on this idea and the feasibility of it. greetings Marco A. -- openSUSE Feature: https://features.opensuse.org/308343

1 7

[New: openFATE 310236] KDE-metapackages for avoid mixing packages versions from different repos
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: Alex Savin (alexqwesa) Feature #310236, revision 1 Title: KDE-metapackages for avoid mixing packages versions from different repos openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Alex Savin (alexqwesa) Description: KDE have many repos and often user get mismatch of packages versions and various strange bugs due this. create KDE-metapackages for avoid mixing packages versions from different repos -- openSUSE Feature: https://features.opensuse.org/310236

1 1

[openFATE 308138] Easy way to install corresponding debuginfo RPM for all existing packages
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: Silviu Marin-Caea (silviumc) Feature #308138, revision 1 Title: Easy way to install corresponding debuginfo RPM for all existing packages openFATE: Unconfirmed Priority Requester: Important Requested by: Silviu Marin-Caea (silviumc) Partner organization: openSUSE.org Description: KDE4 applications crash more often than they should. The bugreporting helper that pops up is not user friendly. It expects the user to know what particular debuginfo RPMs to install in order to get a useful bug report. It also expects the user to toil through a long "wizard" that asks a lot of questions. It's not cool to punish the user on top of an application crash. Does KDE hate us or what? The user shouldn't have to do anything more than giving the accept to send the crash information or not. Examples: Firefox, Windows. If KDE couldn't come up with something easier than this, at least SUSE should do something to work around it. My suggestion would be a way to install all debuginfo RPMs for every package that's already installed. This way, all bugreports will be useful. Business case (Partner benefit): openSUSE.org: We want to get statistic data so we can focus on bugs that crash KDE applications -- openSUSE Feature: https://features.opensuse.org/308138

1 8

[New: openFATE 310431] Create automatic private group for new user
by fate_noreply＠suse.de 09 Dec '16

09 Dec '16

Feature added by: Steven Bert (dodydog) Feature #310431, revision 1 Title: Create automatic private group for new user openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Steven Bert (dodydog) Description: In Yast user management, add an option in the new user dialog to have a new, private group created for the user. The group should be named as the user. The reason for this feature is to allow simple data sharing between users based on projects with a project group and a default umask giving read permisssions to group members (which is the default right now). The only measure to share a file with a project is to set group ownership to the appropriate group. As of now additional file permisssions would have to be changed. -- openSUSE Feature: https://features.opensuse.org/310431

1 2

[New: openFATE 310322] Install, uninstall and change desktop environments easier.
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: jpxviii jpxviii (jpxviii) Feature #310322, revision 1 Title: Install, uninstall and change desktop environments easier. Hackweek V: Unconfirmed Priority Requester: Important openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: jpxviii jpxviii (jpxviii) Description: Some people use and prefer a single desk and others prefer to use multiple. It would be good for non-technical users can make installations and removals of each desktop environments and change KDM - GDM - so easy. -- openSUSE Feature: https://features.opensuse.org/310322

1 3

[New: openFATE 309296] YaST2-Qt : Add "Action after Installation" option
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Rémy Marquis (Spyhawk) Feature #309296, revision 1 Title: YaST2-Qt : Add "Action after Installation" option openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Rémy Marquis (spyhawk) Description: YaST-Qt package manager module should have an additional option in Configuration menu, similarly to the ncurse version (yast sw_single > Configuration > Action after Package Installation). Use Case: * A user wants to change the default behavior, but doesn't know that he needs to change PKGMGR_ACTION_AT_EXIT in /etc/sysconfig/yast2 * A user that have used ncurse yast expects that this option is also in the Qt interface, -- openSUSE Feature: https://features.opensuse.org/309296

1 10

[New: openFATE 312622] add DVB-USB drivers to kernel
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Axel Braun (DocB) Feature #312622, revision 1 Title: add DVB-USB drivers to kernel openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Axel Braun (docb) Partner organization: openSUSE.org Description: For whatever reason, the dvb-USB drivers are not shipped with openSUSE. Drivers are available (see e.g. http://www.linuxquestions.org/questions/showthread.php?p=4265470#post4265470 ) but at least not in 11.4, which makes use of DVBT-Sticks quite complicated Use Case: Some of the USB-DVB-T stick just work out of the box if the right driver is available, e.g. my TrekStor Terres DVB-Stick using the dvb_usb_rtl2832u driver Business case (Partner benefit): openSUSE.org: Makes life easier esp. for users with a lower level of experience. Searching drivers or building kernel modules by yourself is not something an anverage users does. -- openSUSE Feature: https://features.opensuse.org/312622

1 2

[New: openFATE 310604] Push repository Status to Users
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Tejas Guruswamy (MasterPatricko) Feature #310604, revision 1 Title: Push repository Status to Users Buildservice: Unconfirmed Priority Requester: Important openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Tejas Guruswamy (masterpatricko) Description: One of the major complaints from users of the OBS is that it is too hard to identify which package out of multiple available ones is the correct, "safe", one to install. Also repository changes have no way of being noticed except with zypp refreshes suddenly start failing. The OBS provides an amazing, amazing service but still little complications arise; repositories disappear, change content, etc. Three parts would need to be implemented: 1) A "status" or "stability" attribute for all repositories on the OBS. It could have values like * UNSTABLE - This repository contains unreleased software / alpha-quality, possibly direct from source control. Bugs are to be expected. (e.g. KDE:Unstable:Distro ) * FACTORY (or LATEST?) - This repository contains the latest released software from this upstream project, to be submitted to openSUSE Factory. Bugs are possible, please report them. (e.g. KDE:Distro:Factory) * STABLE - This repository contains software as it was in the last stable release of openSUSE, possibly with some additional bugfixes. Bugs should be infrequent. (e.g. KDE:Distro:Stable) * HOME(?) - This repository is someone's Home project. Packages may be added and removed at any time. (maybe not necessary) * VERSION(?) - This repository contains a snapshot of a specific released version of this software. (maybe not necessary) (e.g. KDE:SC:45) I know the OBS supports attributes, so maybe that infrastructure can be used. The current solution of trying to explain it in the repository name is not sufficient as people have conflicting ideas of what "Factory" means, etc. With the explanations side-by-side, there can be no confusion. What would need to be added is * integration with software.opensuse.org and webpin - so repository state is clearly visible in search results, with the explanations of each state also visible on the same page. * integration with Yast2/zypper - in the repository configuration, the repository state should be shown (does it need to be updated every so often? will repositories ever change their state?) 2) A NEWS/ChangeLog file/attribute for every repository on the OBS. This allows the repository owner/maintainer to communicate with the users letting them know of important changes that affect them. This would be downloaded with the repository metadata. This would need to be integrated into: * OBS - easy way to edit this file should be possible (maybe it can be based on the repository description?) * Yast2/zypper/updateapplet - when refreshing a repository, if a changed NEWS is detected, inform the user. something like > zypper ref Repository "foobar" has updated its NEWS file. [Read/Ignore/Skip]: where you can choose to read the changes now, leave it till next time, or ignore it completely. Currently the build service project page is the only place where such information is put, but users never read that. Otherwise you have to resort to the mailing lists, but most users aren't subscribed there until they have a problem. The NEWS file would be used to pass on information including: * Significant changes to the purpose or content of the repository (e.g. KDE:Distro:Factory switching from KDE SC 4.5 to 4.6) * Repository renames, obsoletions, deletions (e.g. KDE:KDE4:Community -> KDE:Extra) Obviously this can't be done too frequently as it would annoy the user, but it is clear that there needs to be some communications channel to let them know what's going on. 3) Improved software search - software.opensuse.org and webpin could become a lot more new-user friendly. Some of my suggestions * Exclude HOME and UNSTABLE projects * Exclude debuginfo and debugsource packages by default * Exclude devel packages by default * Default to only searching for the current, released version of openSUSE. * Display repository status as detailed above I think this could make an absolutely huge difference to how users use the OBS, and most of all, make it a lot more safe - reducing complaints. I know that repository stability attributes have been mentioned by many people many times - but now the infrastructure is there - lets take it one step further... (BTW Forgive my KDE examples, it's just what I am familiar with) -- openSUSE Feature: https://features.opensuse.org/310604

1 7

[New: openFATE 315083] samba 4 support for AD DC
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Bruno Friedmann (bruno_friedmann) Feature #315083, revision 1 Title: samba 4 support for AD DC Buildservice: Unconfirmed Priority Requester: Important Requested by: Bruno Friedmann (bruno_friedmann) Partner organization: openSUSE.org Description: One of the long awaiting feature of samba 4 was the support and drop in replacement of any AD/DC made by proprietary company. Actually the next samba package developed in network:samba:TESTING on obs need a full cleanup. (source4 is totally obfuscated, the mention about the lack of support for AD/AC role is missing etc...) Decisions about the MIT/HEIMDAL krb5 lib has to be taken. Benefit : offer an open implementation of AD/DC to companies and customers. Be the first to do it? Having it integrated quickly in openSUSE, will benefit also SUSE for SLES12 time. ref : bugs https://bugzilla.novell.com/show_bug.cgi?id=821826 https://bugzilla.novell.com/show_bug.cgi?id=794744 obs https://build.opensuse.org/project/show?project=network%3Asamba%3ATESTING -- openSUSE Feature: https://features.opensuse.org/315083

1 3

[New: openFATE 312277] Include GNOME Tweak
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Anomyous Anomyous (jcat123) Feature #312277, revision 1 Title: Include GNOME Tweak openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Anomyous Anomyous (jcat123) Partner organization: openSUSE.org Description: Recently I have tried GNOME 3. There are several settings that you once could customize in GNOME 2 that you can't do in GNOME 3. There is a package called gnome-tweak-tool, that lets you customize things like the Theme again. This should be included on the distribution DVD (and perhaps Live CD too) for openSUSE 12.1. -- openSUSE Feature: https://features.opensuse.org/312277

1 4

[New: openFATE 312209] GTK+ client for Smolt
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Vaibhav Mathur (trojanware) Feature #312209, revision 1 Title: GTK+ client for Smolt openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Vaibhav Mathur (trojanware) Partner organization: openSUSE.org Description: A gtk client for smolt would enable it it to be bundled with the default distribution of openSUSE. -- openSUSE Feature: https://features.opensuse.org/312209

1 2

[New: openFATE 310490] Develop and add a GTK smolt client to openSUSE
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Luis Medinas (lmedinas) Feature #310490, revision 1 Title: Develop and add a GTK smolt client to openSUSE openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Luis Medinas (lmedinas) Partner organization: openSUSE.org Description: Smolt is a project that is picking stats about openSUSE installs. Currently smolt-gui developed upstream is written in Qt and it difficult to add this client to GNOME installation of openSUSE. So it's required to have a GNOME integration to ship on the default install. It's important to have a GTK client similar to smolt-gui and ksmolt (which is the notification service launched on KDE). Use Case: User installs openSUSE GNOME and in the first run it shows a notification asking for the user to submit the hardware data to smolt. If necessary launch a smolt GTK client to send the data. Business case (Partner benefit): openSUSE.org: Most of GNOME users aren't submitting openSUSE stats to smolt database because smolt gui isn't integrated with GNOME. -- openSUSE Feature: https://features.opensuse.org/310490

1 2

[New: openFATE 318432] FUSE filesystem to keep /etc/ valid
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Sławomir Lach (Lachu) Feature #318432, revision 1 Title: FUSE filesystem to keep /etc/ valid openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Editing files is road of pain. User can destroy file, so system can be broken. I suggest to add fuse-based file system with BFS(language to describing file structure) to keep file validated, while closed. It buffer or write in /tmp every write operation and check consistency on file close. If file is good, filesystem will replace file placed in /etc. -- openSUSE Feature: https://features.opensuse.org/318432

1 4

[New: openFATE 311136] Use the community repos list to remove repos
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Sven Burmeister (rabauke) Feature #311136, revision 1 Title: Use the community repos list to remove repos openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Sven Burmeister (rabauke) Partner organization: openSUSE.org Description: If the user adds a repo via the community repos list he should be able to remove them via the same way, i.e. have a list where he can de-select and thus remove the repos. That way if he e.g. added some repo which messed-up his system he could just bring up that same list de-select the repo and yast would "update" all installed packages from that repo to the original state and remove the repo afterwards. In YaST's software management it's the same, you add/remove/refresh from within the same list. -- openSUSE Feature: https://features.opensuse.org/311136

1 1

[New: openFATE 312962] Include acpi_osi=Linux pcie_aspm=force by default for Grub boot parameters
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Roger Luedecke (Shadowolf7) Feature #312962, revision 1 Title: Include acpi_osi=Linux pcie_aspm=force by default for Grub boot parameters openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Roger Luedecke (shadowolf7) Partner organization: openSUSE.org Description: acpi_osi=Linux identifies the OS to the BIOS helping fix power and other issues. pcie_aspm=force fixes power regression issue shown here; http://www.phoronix.com/scan.php?page=article&item=linux_2638_aspm&num=1 -- openSUSE Feature: https://features.opensuse.org/312962

1 8

[New: openFATE 314585] Reinstate KNode
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Christopher Yeleighton (yecril71pl) Feature #314585, revision 1 Title: Reinstate KNode openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Christopher Yeleighton (yecril71pl) Partner organization: openSUSE.org Description: KNode has been removed from the KDE pattern in openSUSE; it is not installed by default in 12.2. The results: 1. The news URL scheme is not recognized. 2. The nntp URL scheme is handled by Dolphin, which is basically unable to handle it. Test Case: { xdg-open 'news:news.answers'; } Business case (Partner benefit): openSUSE.org: News is one of the basic protocols of the Internet, and failing to support it is a shame. -- openSUSE Feature: https://features.opensuse.org/314585

1 2

[openFATE 307746] Yast2-UI to mount remote Samba/CIFS-shares
by fate_noreply＠suse.de 08 Dec '16

08 Dec '16

Feature added by: Alex Müller (Larx) Feature #307746, revision 1 Title: Yast2-UI to mount remote Samba/CIFS-shares openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Alex Müller (larx) Description: At the moment there is no working Yast2-module to simply mount remote SAMBA/CIFS shares the "unix way" (i.e. with a directory entry in the filesystem a la "/network/sharename/"). (yast2-samba-client seems to offer this as "expert option", however I don't get it to work.) The different desktop environments offer access with the "smb:/"-protocol, however this doesn't work really consistently. E.g. it doesn't help with consoles and scripts, and even some desktop apps, namely KDE's own Amarok, refuse to use the smb:/-protocol. So I think a Yast2-module - which should be simple to do, as it would only be a frontend to /etc/fstab or /etc/samba/smbfstab - to mount SAMBA shares should be implemented. -- openSUSE Feature: https://features.opensuse.org/307746

1 5

[New: openFATE 321763] Add option to install to not add proprietary repos
by fate_noreply＠suse.de 07 Dec '16

07 Dec '16

Feature added by: Aleksa Sarai (cyphar) Feature #321763, revision 1 Title: Add option to install to not add proprietary repos Requested by: Aleksa Sarai (cyphar) Partner organization: openSUSE.org Description: Currently the openSUSE installer will, by default, add proprietary repositories (openSUSE:Factory:NonFree) to zypper without giving the user an option of disabling it. In the package selection screen, you can only blacklist the repo (not remove it entirely). To allow users to make the decision whether they want to allow a proprietary repo to be added to their system we should have a checkbox like: [ ] Enable proprietary repositories. During the repository selection screen in yast2-installation (when users can select add-on media for the repos). By default we can make it selected, but the main point is that now there's a switch to convert openSUSE into a completely free software distribution. Business case (Partner benefit): openSUSE.org: This would be a first step toward being an FSF-compliant distribution (or at least, more acceptable toward the FSF). While not everyone cares about FSF compliance, I personally would like to make sure that on my own computers (and the computers of people I install GNU/Linux for) contain no proprietary software packages. And while the kernel Linux contains non-free blobs (which I don't think we remove) this would be a nice first step toward that goal. -- openSUSE Feature: https://features.opensuse.org/321763

1 6