September 2011 - openSUSE Features - openSUSE Mailing Lists

[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

[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