Mailinglist Archive: opensuse-features (518 mails)

< Previous Next >
[openFATE 308138] Easy way to install corresponding debuginfo RPM for all existing packages
  • From: fate_noreply@xxxxxxx
  • Date: Wed, 11 Aug 2010 19:04:32 +0200 (CEST)
  • Message-id: <feature-308138-8@xxxxxxxxxxxxxx>
Feature changed by: jpxviii jpxviii (jpxviii)
Feature #308138, revision 8
Title: Easy way to install corresponding debuginfo RPM for all existing

openSUSE-11.3: Unconfirmed
Requester: Important

openSUSE-11.4: Unconfirmed
Requester: Mandatory

Requested by: Silviu Marin-Caea (silviumc)
Partner organization:

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.
Although the person who created this suggestion became more emphasis on
KDE, it would be ideal and very useful for all applications that can be
installed on openSUSE. This automated tool that all types of users can
use regardless of computer skills (end users, novices, managers,
developers, etc. that are used by Windows or Firefox to send errors
(bugs) greatly improve the quality of openSUSE. Since more people have
they can send error reports (failure) and classified automatically in a

Business case (Partner benefit): We want to get statistic data so we can focus on bugs
- that crash KDE applications
+ that crash all aplications.

openSUSE Feature:

< Previous Next >
This Thread