Dr Konqi still misbehaving - advice needed

Ian Wadham iandw.au at gmail.com
Sat Nov 29 21:13:30 GMT 2014

Hi Thomas,

On 29/11/2014, at 11:56 PM, Thomas Lübking wrote:
> On Samstag, 29. November 2014 11:35:31 CEST, Ben Cooksley wrote:
>> Blahblahblah ;-)
> Reproducible here.


> Bugzilla version is 4.4.6, drkonqi uses token security.
> I need to log into bugs.kde.org (w/ my password ;-)
> And finally hit the 410 error.

Aha, so my hunch was correct… :-)  Also, as additional evidence, there was a
new crash reported on BKO yesterday which seemed to be successfully reported.
I am awaiting confirmation - https://bugs.kde.org/show_bug.cgi?id=341351#c2

A little "i" to dot: if you log OUT from the bugs.kde.org website, does Dr Konqi
then go back to working OK, without the 410 error?

IOW, can I offer that as a workaround until we can release your fix?  Or does BKO
leave stale cookies in the jar?  They can be tricky to remove in some browsers...

> Altering the conditions to make bugzilla require password security for 4.4.6
> - if (currentVersion >= KDE_MAKE_VERSION(4, 5, 0)) {
> + if (currentVersion >= KDE_MAKE_VERSION(4, 4, 6)) {

Thanks, Thomas.  This is a neat solution and avoids having to mess with kio_http.  Nice!

> "fixes" it for me (ie. the bug is nicely reported and probably some konsole dev now hates me ;-)

You mean you added a spurious report to the live BKO DB?  Tsk, tsk… :-)

All the best, Ian W.

More information about the kde-core-devel mailing list