Version: unspecified OS: Linux See bug #252817 - it's a really nasty thing since we cannot really fix it (upstream, 4.7 will by default avoid it, though) and Martin keeps asking ppl. to not attach any more bugs - but i doubt they can see that comment through Dr.Konqui and even ifff..... Therefore it would be great to rather point ppl. to the bug, tell them it's been blocked against new reports (maybe with a custom message?), attach them to the recp. but NOT have them file a new bugreport. I'm aware that usually new reports might bring new information on how to reproduce/what's causing the bug, but in this example that's just not the case and while this bug reports will likely (hopefully, toctoctoc) come to an end soon, this might occur elsewhere or just again as well. Reproducible: Didn't try Expected Results: It would be great to rather point ppl. to the bug, tell them it's been blocked against new reports (maybe with a custom message?), attach them to the recp. but NOT have them file a new bugreport.
+1 for the idea
I think the prerequisite is some way for developers to mark one report as "not welcoming drkonqi/new comments anymore". It might be done through : * close the report as "CLOSED" instead of "RESOLVED" * set some keyword like "/dev/null", or "blocking-drkonqi", or whatever sounds more appropriate and less confusing.
(In reply to comment #2) > I think the prerequisite is some way for developers to mark one report as > "not welcoming drkonqi/new comments anymore". It might be done through : > > * close the report as "CLOSED" instead of "RESOLVED" > * set some keyword like "/dev/null", or "blocking-drkonqi", or whatever > sounds more appropriate and less confusing. I would add also: * a custom flag to mark the bug as "no need to add other information" * a custom field with the the description of the solution/workaround (which can be fetched by drkonqui and showed to the user).
A possibly relevant merge request was started @ https://invent.kde.org/plasma/drkonqi/-/merge_requests/204
Git commit a0bd2fa0cfbde80032cf45e657ad21da4df74a41 by Harald Sitter. Committed on 07/12/2023 at 18:02. Pushed by sitter into branch 'master'. duplicates detection: drop support with the advance of automatic crash reporting the duplicates detection isn't really necessary anymore. it also hasn't been all that great. the UI was terrible, the UX was terrible, the code was expansive, parsing random comments from bugzilla had potential of crashing drkonqi ... Related: bug 463223, bug 473408, bug 466919, bug 264146 M +0 -1 Testing.md M +0 -6 src/CMakeLists.txt M +4 -101 src/bugzillaintegration/bugzillalib.cpp M +2 -20 src/bugzillaintegration/bugzillalib.h D +0 -163 src/bugzillaintegration/duplicatefinderjob.cpp D +0 -83 src/bugzillaintegration/duplicatefinderjob.h D +0 -158 src/bugzillaintegration/parsebugbacktraces.cpp D +0 -52 src/bugzillaintegration/parsebugbacktraces.h M +35 -99 src/bugzillaintegration/reportinterface.cpp M +0 -17 src/bugzillaintegration/reportinterface.h M +1 -16 src/drkonqi_globals.h M +1 -4 src/drkonqidialog.cpp M +0 -35 src/parser/backtraceparser.cpp M +1 -6 src/parser/backtraceparser.h M +0 -1 src/parser/backtraceparser_p.h M +0 -1 src/qml/BacktracePage.qml D +0 -57 src/qml/DuplicatesLoadingPage.qml D +0 -135 src/qml/DuplicatesPage.qml M +1 -1 src/qml/LoginPage.qml D +0 -73 src/qml/PerfectDuplicatePage.qml M +0 -5 src/qml/ReportPage.qml M +0 -6 src/qml/main.qml M +0 -3 src/qml/qml.qrc D +0 -120 src/qmlextensions/duplicatemodel.cpp D +0 -57 src/qmlextensions/duplicatemodel.h M +1 -0 src/qmlextensions/platformmodel.cpp M +0 -21 src/tests/backtraceparsertest/backtraceparsertest.cpp M +0 -2 src/tests/backtraceparsertest/backtraceparsertest.h M +0 -10 src/tests/backtraceparsertest/backtraceparsertest_data/data.ini M +0 -1 src/tests/backtraceparsertest/backtraceparsertest_manual.cpp https://invent.kde.org/plasma/drkonqi/-/commit/a0bd2fa0cfbde80032cf45e657ad21da4df74a41