April 2012 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 309221] Simplify adding OBS repos
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Stefan Majewsky (majewsky) Feature #309221, revision 1 Title: Simplify adding OBS repos openSUSE-11.3: Unconfirmed Priority Requester: Desirable Requested by: Stefan Majewsky (majewsky) Partner organization: openSUSE.org Description: When I want to add a build service repository, I have to find a quite cryptic URL, such as http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openS…. Much of the information in this URL is redundant and error-prone, such as the domain and the distribution version. It would be much nicer if Zypper and YaST knew about the repo structure of the OBS, so I could type something like obs://KDE:KDE4:Factory:Desktop, and have Zypper/YaST figure out the rest. Extra points if browsers could figure out that "obs://" URLs should be handled by YaST. Business case (Partner benefit): openSUSE.org: This reduces error sources. For example, if I provided some repository that provides some closed-source drivers, I would currently have to provide a gigantic list of repository URLs for all supported openSUSE versions. With the proposed change, the description for how to use such a repository would boil down to: 1. Add the repository "obs://home:foobar:importantdrivers". 2. Do a system upgrade. With the browser integration, we could even have something like a one-click installation for repositories. -- openSUSE Feature: https://features.opensuse.org/309221

1 5

[New: openFATE 308424] Please port Light style revision 2 theme to KDE4
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Ilya Chernykh (Ansus) Feature #308424, revision 1 Title: Please port Light style revision 2 theme to KDE4 openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Ilya Chernykh (ansus) Description: Please port Light style revision 2 theme from KDE3 to KDE4. This is the best-looking widget theme ever in my opinion. This makes transition to KDE4 much easier and allows for better coexistence of KDE3 and KDE4 applications. -- openSUSE Feature: https://features.opensuse.org/308424

1 5

[New: openFATE 310987] Add Intel Atom as a specific architecture
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Jiri Dluhos (jdluhos) Feature #310987, revision 1 Title: Add Intel Atom as a specific architecture openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Jiri Dluhos (jdluhos) Partner organization: openSUSE.org Description: Atom processors, currently very popular in lightweight devices, behave very differently from common Intel/AMD processors; although they can execute code optimized for common x86 or x86-64, they don't run it much efficiently. Because they are not that fast, every cycle counts. I believe it would be useful to consider them a separate sub-architecture that deserves its own set of compilation options. -- openSUSE Feature: https://features.opensuse.org/310987

1 4

[New: openFATE 311038] Update to Eclipse 3.6.1
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: F S (fs92) Feature #311038, revision 1 Title: Update to Eclipse 3.6.1 openFATE: Unconfirmed Priority Requester: Desirable Requested by: F S (fs92) Partner organization: openSUSE.org Description: Update from Eclipse 3.4 from OpenSuse 11.3 to Eclipse 3.6.1 is desirable. -- openSUSE Feature: https://features.opensuse.org/311038

1 4

[openFATE 307842] Update eclipse to latest version
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Glenn Doig (doiggl) Feature #307842, revision 1 Title: Update eclipse to latest version openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Glenn Doig (doiggl) Description: Update eclipse to latest version as found in http://www.eclipse.org/downloads/ Thanks Glenn -- openSUSE Feature: https://features.opensuse.org/307842

1 29

[New: openFATE 311322] Add button to change color depth on Display Monitor
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Roman Bysh (Romanator) Feature #311322, revision 1 Title: Add button to change color depth on Display Monitor openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Roman Bysh (romanator) Partner organization: openSUSE.org Description: I'm proposing that we add an extra button to the Display and Monitor settings to change the color depth. Since sax2 was deprecated. We have been missing a way to dynamically change the color depth. Sax2 used to have a button to allow users to change the color depth. For example: * 8-bit * 15-bit * 16-bit * 24-bit * 32-bit Let's vote to add this feature to the Display and Monitor in KDE. -- openSUSE Feature: https://features.opensuse.org/311322

1 29

[New: openFATE 311365] Include biosdevname to rename network interfaces based on chassis labels
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Narendra K - (narendra_k) Feature #311365, revision 1 Title: Include biosdevname to rename network interfaces based on chassis labels openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Narendra K - (narendra_k) Partner organization: openSUSE.org Description: On a Dell PowerEdge server with multiple add-in cards, the naming of the network interfaces is non-deterministic. This results in 'eth0' not mapping to "Embedded NIC 1" as labeled on the server chassis. This issue is seen on Dell PowerEdge 10G above. This feature addresses this issue by renaming network interfaces based on their location on the system motherboard. The naming policy it suggests are as follows: Embedded devices: em<port> Add-in PCI cards: pci<slot>p<port>_<virtual function instance> Please refer to "Consistent Network device naming-Name network interfaces to match chassis labels" (https://features.opensuse.org/310896). Business case (Partner benefit): openSUSE.org: This allows system administrators to refer to the network interfaces by names based on their location on the motherboard. The naming becomes deterministic and there is no state such as HWADDR embedded into the configuration files. -- openSUSE Feature: https://features.opensuse.org/311365

1 8

[New: openFATE 310560] Future Download Options for 11.4<
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Jeremy Thornton (leebrad) Feature #310560, revision 1 Title: Future Download Options for 11.4< Buildservice: Unconfirmed Priority Requester: Important openFATE: Unconfirmed Priority Requester: Important openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Jeremy Thornton (leebrad) Description: I am sure this may have been proposed before, but just in case I think it is a good move if the SUSE project would consider the following... #Proposal Break 11.4+ distributions into the following downloadable images from the opensuse.org site... I know 1,2,5 are already options, but the others should also be considered. 1. Gnome Desktop Live CD (<700mb) 2. KDE Desktop Live CD (<700mb) 3. LXDE Desktop Live CD (<700mb) 4. Server and Virtualization CD (<700mb) 5. Complete DVD (4gb) 6. Meego/Netbook Live Image (for future netbook installs) Important:Options to install inside as Windows applications (like Ubuntu) Important:Options to install onto USB drive (with GUI application like Ubuntu/Fedora) #Benefits 1.More accessible download options 2.Less frustrating if download fails 3.Less bandwidth requirements to support the project 4.More flexibile installation capabilities 5.These can be built easier and maintained with the project since the intro of SUSE Studio. #Additional Considerations 1.Besides possible acquisition of the SUSE project by some company the community must remain innovative and competitive against Fedora and Ubuntu. 2.Ubuntu and Fedora already offer these download and convenience options. 3.I have read comments from users who either don't realize a server option is built in or hate the idea of download the DVD just for a light server install. -- openSUSE Feature: https://features.opensuse.org/310560

1 14

[openFate 305664] Server CD
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Martin Schlander (cb400f) Feature #305664, revision 1, last change by Title: Server CD openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Martin Schlander (cb400f) Description: Providing an official openSUSE server cd - with some often used server software - and perhaps a lightweight window manager like icewm or similar - would be a great thing for a number of reasons. - openSUSE is generally considered a desktop centric distribution, providing a server cd would do a heck of a lot to highligt the excellent (home-)server qualities of openSUSE. - The few people that realize that the openSUSE DVD/netinstall actually offers text mode/server installation, are often discouraged by needing to download a full DVD, or do troublesome and slow http/ftp installation. - Server users are generally more technical people, it would be beneficial to attract more of these to the openSUSE project. - More people using openSUSE on home servers would likely have spill-over effects on SLES sales. - An openSUSE server cd, would be an excellent response to Ubuntu server edition and Microsoft Home Server. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305664

1 32

[New: openFATE 312120] Make default KDE theme greenish, to match whole system
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Dino E (D_E) Feature #312120, revision 1 Title: Make default KDE theme greenish, to match whole system openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Package Wishlist: Unconfirmed Priority Requester: Mandatory Requested by: Dino E (d_e) Partner organization: openSUSE.org Description: We really need to make default KDE theme green, to match whole system greenish appearance. It's involves just to steps: make default green icon set (like http://gnome-look.org/content/show.php/Oxygen-Refit+2+-+Green+Version?conte…) and make default green colours (like http://kde-look.org/content/show.php/Ordinary+Green?content=107944) Business case (Partner benefit): openSUSE.org: It's kinda ugly when you have blue icons and colours in otherwise green system. Also blue is highly overused nowadays - remember default themes in windows xp-7, mac os x, and kde itself. -- openSUSE Feature: https://features.opensuse.org/312120

1 31

[New: openFATE 308314] better wine integration
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Sharque uddin Ahmed Farooqui (safknw) Feature #308314, revision 1 Title: better wine integration openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Sharque uddin Ahmed Farooqui (safknw) Description: There are times we need to use windows applications. Wine applications does not integrate well with with rest of desktop. There is no menu entry for wine settings. Also there should be menu for reboot wine. I use wine for Heidisql (Mysql admin tool) and some time for games. -- openSUSE Feature: https://features.opensuse.org/308314

1 22

[New: openFATE 310112] Desktop files with debuging feature
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Sławomir Lach (Lachu) Feature #310112, revision 1 Title: Desktop files with debuging feature openSUSE-11.4: Unconfirmed Priority Requester: Neutral Requested by: Sławomir Lach (lachu) Partner organization: openSUSE.org Description: Often users don't know how track problems and there's no simple sollutions for begginiers. I think, that adding additional fields to .desktop files will helps a lot. Thease fileds should been named DEBUG_MODE_ON and DEBUG_MODE_RUNNER. Once DEBUG_MODE_RUNNER is not present, there's should exist mechanism to debug(ex. running konsole and application on it ; or better redirecting stderr and stdout onto file and asks user to display it/send/etc. after application quits). Test Case: Test that dialog with question about displaying log file don't show before application quits. Use Case: Better can't run some application, because some libraries isn't present on the system. It will only right click on application runner and select debug mode. Business case (Partner benefit): openSUSE.org: * Developers of application could add custom debug mode with full featured information gathering and sending log file to vendor. It could make support better. * Better forums support. * A way to create automated tools, which reads logs and perform some tasks(if user accept) * Many user don't know how solving problems on Ubuntu. Running application in terminal don't always be pragmatic, because xterm have limited buffer for text. Also, running terminal isn't very simple. -- openSUSE Feature: https://features.opensuse.org/310112

1 3

[openFate 305582] Off-Line one click install (MSI for Linux)
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Duncan Mac-Vicar <dmacvicar(a)novell.com> Feature #305582, revision 1, last change by Title: Off-Line one click install (MSI for Linux) openSUSE-11.2: New Priority Requester: Important Requested by: Duncan Mac-Vicar <dmacvicar(a)novell.com> Partner organization: openSUSE.org Description: Idea from community member Raul Romero. Same concept as MSI packages for Windows but exploiting the One Click Install concept of openSUSE (and therefore inheriting the simplicity, code and security. Basically a compressed file which includes a repository inside, plus one click install information, and a script to trigger the oneclickinstall handler with the data as payload in the script. Therefore is a collection of rpms that can be installed detailed description is here http://en.opensuse.org/OSI There is already a prototype working. Example script: http://dl.getdropbox.com/u/363315/MozillaFirefox.osi This requires some extra features in one click install and other pieces * ability to force OneClick to add the repo (the one inside the compressed file) Additionally I see other features: * ability to suggest an update repo for the installed bundle * support from build service to generate bundles * easy way to generate them locally Out of scope but interesting: * Ablity to trigger a YaST workflow (its own control.xml?) Business case (Partner benefit): openSUSE.org: This solves the business case of distributing service packs, applications, codecs bundles by just downloading a big file, 100% offline, supporting dependencies and repo signatures. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305582

1 40

[openFATE 306907] Add support for Ksplice
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Stephan Kleine (bitshuffler) Feature #306907, revision 1 Title: Add support for Ksplice openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Stephan Kleine (bitshuffler) Description: KSplice allows it currently to apply most but not all kernel updates without the need to reboot which is especially great for servers. It's backed by a newly founded corporation that continually tries to improve it so hopefully sometime in the future a reboot wont be necessary for any kernel update. Fedora as well as Ubuntu already support it so openSUSE shouldn't stay behind. URL: http://www.ksplice.com/ -- openSUSE Feature: https://features.opensuse.org/306907

1 18

[New: openFATE 310164] Choose Better Wallpapers for SUSE
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Andres Silva (anditosan) Feature #310164, revision 1 Title: Choose Better Wallpapers for SUSE openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Andres Silva (anditosan) Description: I made a list of Wallpapers that could potentially be on the next version of KDE. http://anditosan.blogspot.com/2010/07/from-land-of-reptiles.html -- openSUSE Feature: https://features.opensuse.org/310164

1 4

[New: openFATE 310163] Remove Welcome Screen on OpenSUSE KDE
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Andres Silva (anditosan) Feature #310163, revision 1 Title: Remove Welcome Screen on OpenSUSE KDE openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Andres Silva (anditosan) Description: Hey you all. I would first like to thank all of you who have visited this website and looked at the ideas I have posted. I am deeply honored that many of you too have considered these ideas worthwhile and would like to see them implemented. Well, here comes a good one I think. As I was talking to some people on the KDE IRC channel yesterday, there was a comment made about a possible way to orient new KDE users on how to use the desktop. However, I believe that users should be left clues to discover their desktop on their own. There should not be an intro popup or anything like that. Ponder about this for a moment. What can you say, for example, about paintings. Paintings are not "explained" to anyone. You look at it and you get it in your own particular way. That is enough for you and you know what it means. The clues left by the artist are clear enough to your mind that you find meaning in the painting. You intuitively "know" what the purpose of the painting is. Reflect for a moment on this Cezanne and know what it means... REMOVE KDE WELCOME POPUP SCREEN anditosan.blogspot.com -- openSUSE Feature: https://features.opensuse.org/310163

1 8

[New: openFATE 312876] Deny individual users' access to screen-saver settings
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Per Jessen (pjessen) Feature #312876, revision 1 Title: Deny individual users' access to screen-saver settings openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Per Jessen (pjessen) Partner organization: openSUSE.org Description: This is an extension of feature#312871, but because it's a little more involved than changing a simple default, I thought it would be better to have a separate feature request. The screen-saver settings for time-out and "require password" are security settings that really should not be freely available to the individual user. I propose that we 1) set a reasonable default (60sec, 15sec, always require passwd) (see feature#312871) and 2) only let these settings be modified by someone with root-access. To a regular user, the timeout and "require password" settings should appear "greyed out", clearly indicating "not available". Use Case: Office user - the user is able to select a screen-saver, but the other settings cannot be accessed, accidentally or otherwise. The install or admin person need not change anything to get a sane security setup for the desktop. SOHO or home users - same as above, but the default screen-saver settings may be changed by switching to root access. Business case (Partner benefit): openSUSE.org: This is simply a reasonable security measure, fitting nicely into the overall security-conscious profile of openSUSE. Security measures (firewall, apparmor, encryption etc) are typically accessible only with root-access; it's only sensible that we apply this principle to the screen-saver settings too. -- openSUSE Feature: https://features.opensuse.org/312876

1 10

[New: openFATE 312337] clear /tmp-dir at bootup
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: M K (tux93) Feature #312337, revision 1 Title: clear /tmp-dir at bootup openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: M K (tux93) Partner organization: openSUSE.org Description: Please clear the /tmp-dir at boot-up per default. At the moment this has to be activated manually with every new installation, is there a reason for not doing this out of the box? -- openSUSE Feature: https://features.opensuse.org/312337

1 6

[New: openFATE 309487] Clean out X11 keyboard configuration in YaST
by fate_noreply＠suse.de 24 May '17

24 May '17

Feature added by: Jiří Suchomel (jsuchome) Feature #309487, revision 1 Title: Clean out X11 keyboard configuration in YaST Requested by: Jiří Suchomel (jsuchome) Developer: (Novell) Developer: (Novell) Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2-tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 -- openSUSE Feature: https://features.opensuse.org/309487

1 16

[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 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 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 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 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 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 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 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