Bug 314630 - DrKonqi didn't prevent creating report when it knew there was no backtrace available
Summary: DrKonqi didn't prevent creating report when it knew there was no backtrace av...
Status: RESOLVED WORKSFORME
Alias: None
Product: drkonqi
Classification: Applications
Component: general (show other bugs)
Version: 2.1.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-07 21:14 UTC by Meriuta Cornel
Modified: 2020-01-13 04:33 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Meriuta Cornel 2013-02-07 21:14:07 UTC
Application: plasma-desktop (0.4)
KDE Platform Version: 4.10.00
Qt Version: 4.8.2
Operating System: Linux 3.2.0-37-generic x86_64
Distribution: Ubuntu 12.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:După actualizarea la KDE-plasma 4.10 am dorit să deschid o nouă activitate, moment în care plasma s-a prăbușit pentru câteva secunde. revenindu-și apoi la normal.

-- Backtrace:
A useful backtrace could not be generated

Possible duplicates by query: bug 314527, bug 314234, bug 314110, bug 314074, bug 314000.

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-02-08 05:03:09 UTC
Sorry, but this crash report itself is really not useful :

* No backtrace available
* Not written in English

However, I'm surprised DrKonqi did't prevent you from reporting this crash even though it clearly knew there was no useful backtrace available. DrKonqi should just prevent that.

Sorry for wasting your time in creating a not useful crash report. Reassign it to DrKonqi.
Comment 2 Jekyll Wu 2013-09-15 02:43:27 UTC
Bug 323852 is another more recent example.
Comment 3 Andrew Crouthamel 2018-11-10 03:12:14 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-20 04:03:43 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Harald Sitter 2019-12-14 17:35:40 UTC
Change state as per earlier questions.
Comment 6 Bug Janitor Service 2019-12-29 04:33:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2020-01-13 04:33:11 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!