Bug 143243 - Disable Backtrace window when application crash
Summary: Disable Backtrace window when application crash
Status: RESOLVED DUPLICATE of bug 58075
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
: 228546 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-03-20 00:01 UTC by Christian Schmitz
Modified: 2013-08-09 09:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Schmitz 2007-03-20 00:01:53 UTC 
Version:            (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs
OS:                Linux

Every time that one application crash or dead with the wrong signal, one window for report is opened.
I want disable and that never appear this window.
I think that this can be configurable. So i am a programmer i need it, if i am NOT a programmer i dont need.

Really this windows seem like blue screen into windows OS. Are really nasty for the users. But i understud that is necesary for programmers, so i think that the better is convert into a optional feature.

Thanks
Comment 1 Inge Wallin 2007-03-21 16:08:56 UTC 
This isn't really a kchart issue, is it?  Which module do you want me to move it to?
Comment 2 Christian Schmitz 2007-03-21 16:36:35 UTC 
NO, is not a kchart issue, i dont know how select kchart, i was selected "general kde BUG".
If you have a way of reasign please i preciate to do. If you can't, tell me and repost.

This happens when i close OOficce, some wine apps, kweather, kmail, Kopete
Thanks
Comment 3 Inge Wallin 2007-03-21 18:33:00 UTC 
Ok, done
Comment 4 Pino Toscano 2008-11-10 09:37:28 UTC 
export KDE_DEBUG=1 in your ~/.profile
Comment 5 Christian Schmitz 2008-11-18 21:22:16 UTC 
Thanks. So, only is missing a GUI way to fix.

Best regards
Comment 6 Dario Andres 2009-11-25 20:22:51 UTC 
As of KDE SC 4.3+, the crash handler is no longer that "terrible" (BSOD)... it only tells the user about the unexpected closed and it allows him/her to automatically report the crash to the KDE bugtracking database (if the information is useful enough).
So, it is a contact point between the users and the devs...

In any case I would revert what you said: "if you are an user, you need it; if you are a developer you don't".

Developers know already how to disable it, and I think they wont need a GUI for this.
Besides that, user needs some kind of feedback when things fails... otherwise they could think "it just closed itself magically without saying why..."

- What would you think ?
Regards
Comment 7 George Kiagiadakis 2010-02-25 23:31:35 UTC 
*** Bug 228546 has been marked as a duplicate of this bug. ***
Comment 8 Jekyll Wu 2013-08-09 09:32:57 UTC 
So here is the honest truth: within 10 years (see bug 58075), nobody has shown any interest in implementing a GUI for disabling Dr.Konqi completely. 

And I agree with previous Dr.Konqi contributors: the presence of Dr.Konqi after crashing is an very import feedback . At the minimum it informs users "application xyz has crashed, but that sometimes just happens, so don't panic. Nobody has hacked your computer!" . Providing a GUI for disabling Dr.Konqi completely only provides marginal benefit for some power users who do not bother with bug reporting.

*** This bug has been marked as a duplicate of bug 58075 ***