Attempting to file a bug using the crash handler's crash reporting assistant now appears to be broken. It fails at the "Login to the KDE Bugtracking System" step with "Error when trying to login: /Unknown response from the server./" It pops up a window displaying what appears to be the front page of Bugzilla, and is logged in.
Unfortunately Dr Konqi will need to adapt to the new Bugzilla i'm afraid.
Same error here KDE 4.6.5 Mageia 1
Please do not report "me too's" in case of this bug. All currently released versions of KDE, including the pending 4.8.1 will be affected by this.
*** Bug 295364 has been marked as a duplicate of this bug. ***
*** Bug 295401 has been marked as a duplicate of this bug. ***
*** Bug 295453 has been marked as a duplicate of this bug. ***
*** Bug 295470 has been marked as a duplicate of this bug. ***
*** Bug 295485 has been marked as a duplicate of this bug. ***
*** Bug 295510 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > Unfortunately Dr Konqi will need to adapt to the new Bugzilla i'm afraid. Observe that it is a gazillion times easier to fix the server than to fix all clients. Such API changes should expose a compatible interface for at least 2 years after server upgrade. It definitely looks like a bug in Bugzilla.
(In reply to comment #10) > (In reply to comment #1) > > Unfortunately Dr Konqi will need to adapt to the new Bugzilla i'm afraid. > Observe that it is a gazillion times easier to fix the server than to fix > all clients. Such API changes should expose a compatible interface for at > least 2 years after server upgrade. It definitely looks like a bug in > Bugzilla. Not really, Drkonqi is to blame here, because it parses html and tries to behave like a user clicking on forms on the website. The correct and more compatible way is to use xml-rpc.
(In reply to comment #10) > Such API changes should expose a compatible interface for at > least 2 years after server upgrade. It definitely looks like a bug in > Bugzilla. DrKonqi was never using an "API" with any compatibility promise at all; it was scraping the HTML. It's a bug in DrKonqi for using an unreliable way to talk to Bugzilla.
doesn't change the fact that changing bugzilla "on the fly" like this shows a lack of planning. you guys should have told the drkonqi developers way ahead what's coming, and then waited until they release an updated drkonqi that works with bugzilla independend of theme and html.
Created attachment 69408 [details] drkonqi-unhandled-bugzilla-error Same problem here, openSUSE 12.1, KDE 4.7.4. I tried to report bug to Akonadi Google, but Drkonqui failed to login to Bugzilla ("unknown, invalid response from the server") and produced output in attachment.
(In reply to comment #14) > Same problem here, openSUSE 12.1, KDE 4.7.4. As Ben said, "same here" reports are pointless; it's known that it fails for every released KDE version. By the way, we're researching ways to make changes in the server to let the old DrKonqi work again.
*** Bug 295359 has been marked as a duplicate of this bug. ***
It should not be hard to fix this bug on the server side. If you look here: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/kde-runtime/oneiric/view/head:/drkonqi/bugzillalib.cpp on line 250 you will see that what DrKonqi is looking for is the words "Managing Your Account" somewhere on the screen that responds to the login. All that needs to happen to fix this issue quickly is to add an HTML comment with this text in it somewhere on that page: <!-- Managing Your Account --> I agree that for future versions of DrKonqi using a well-formed API is preferable, but you want to fix the site for all the code that is already deployed, something like this will need to be done on the server side.
happens in the ppa complied 4.8 ALL THE TIME.
We have now asked twice to not post "me to's". Do not do it. We are aware of the problem. KDE Sysadmin
*** Bug 295637 has been marked as a duplicate of this bug. ***
*** Bug 295662 has been marked as a duplicate of this bug. ***
Thanks to some work by George and myself, pre-4.9 and unpatched Dr Konqi installs should now be able to communicate with KDE Bugzilla again.
Thanks a lot for your effort in solving this issue which doesn't seem to be very easy to solve so gracefully. I can confirm DrKonqui is able to cope with bugzilla again. KDE 4.7.4 here.
(In reply to comment #3) > Please do not report "me too's" in case of this bug. All currently released > versions of KDE, including the pending 4.8.1 will be affected by this. I'm posting a "Me Too" anyway. This is not RESOLVED. It is an active bug. By bug standards this should be marked as Critical because it affects all users. Why do you expect us to follow the rules when you don't.
This particular problem has been resolved. If you have any issues at this moment, feel free to file a new bug. Best, Tom Albers KDE Sysadmin
reporting broke when Vivaldi browser broke, neither report or Vivaldi operated correctly. Major flashes of 'lightning' strike objects across screen. Inability to report faults
elonmac: whatever you are seeing is not this bug. This bug wasn't about KDE's DrKonqi, and it really was fixed years ago.