You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

ilkant

Beginner

  • "ilkant" started this thread

Posts: 3

Location: Helsinki, Finland

  • Send private message

1

Sunday, April 3rd 2005, 4:31pm

More automation to bug reporter

Many KDE-applications have bug report system. I think it would be better if that would know users account on bugs.kde.org and use it. So you need not first log in bugs.kde.org as pre-action after crash when reporting bug.

Furhermore stack trace would be good automatic included information after crashes.

It would be fine, if bug reporter would have anonymous mode. Many users are too shy to use own name or data reporting bug. With this feature KDE bug system gets much more bugreports and ideas to make bugfixes and new features when KDE-machines all over the world reports crashes if they are connected to Internet. If anonymous reports are a flood, it could be placed to special account on bugs.kde.org (which may be able to set hidden optionally). Maybe it could be configured if it sends reports with user data or anonymously.

Many applications for example like FireFox or Microsoft's are sending bug reports automatically even user don't do anything more than push one button (that is configurable too!) or do nothing.

2

Tuesday, April 5th 2005, 7:09am

RE: More automation to bug reporter

Quoted

Originally posted by ilkant
Many KDE-applications have bug report system. I think it would be better if that would know users account on bugs.kde.org and use it. So you need not first log in bugs.kde.org as pre-action after crash when reporting bug.
AFAIK, if you don't logout in the KDE bugsystem, the username is remembered for next usage.

Quoted

Furhermore stack trace would be good automatic included information after crashes.
It must be possible to file a bugreport for this, espessially because (almost) every program uses the same classes for this (maybe kdelibs/kbugreport; possible problem is that some information isn't available after the program has crashed).

Quoted

It would be fine, if bug reporter would have anonymous mode. Many users are too shy to use own name or data reporting bug. With this feature KDE bug system gets much more bugreports and ideas to make bugfixes and new features when KDE-machines all over the world reports crashes if they are connected to Internet. If anonymous reports are a flood, it could be placed to special account on bugs.kde.org (which may be able to set hidden optionally). Maybe it could be configured if it sends reports with user data or anonymously.
Stack traces alone aren't always usefull: there are usefull in combination with actions of the user. With an anonymous user, it is impossible to debate about a bug. For example, if it is unclear or some data isn't given.

Quoted

Many applications for example like FireFox or Microsoft's are sending bug reports automatically even user don't do anything more than push one button (that is configurable too!) or do nothing.