Bug 333044

Summary:	drkonqi uses non-existant version number for krunner, hence can't submit bug report.
Product:	[Applications] drkonqi	Reporter:	Thiago Jung Bauermann <thiago.bauermann>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	aanm90, jan_braun, kxenator, mail, okurz, olivier.delaune, sitter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	krunner crash information generated by drkonqi.

Description Thiago Jung Bauermann 2014-04-03 19:19:45 UTC

I just tried submitting a krunner crash report, but drkonqi fails at the last step with:

Der Fehlerbericht kann nicht gesendet werden: /Unerwarteter Fehlercode "32.000" von Bugzilla empfangen. Die Fehlermeldung lautet: The version value '4.12.2' is not active../

Which means roughly that it can't send the report to bugzilla because it gets the unexpected error code 32.000, with error message "The version value '4.12.2' is not active../"

In KUbuntu, krunner is part of the package kde-workspace-bin, which currently in my system i at version 4.11.6. In bugzilla, the krunner component version goes up to 4.11.8.

It looks like drkonqi doesn't know how to find out what is the version of krunner.



Reproducible: Didn't try

Steps to Reproduce:
I'd have to wait krunner to crash again to find out. I would think that the same error would happen again, though.
Actual Results:  
drkonqi is unable to submit the bug report to bugzilla.

Expected Results:  
Bug report submitted to bugzilla.

Comment 1 Thiago Jung Bauermann 2014-04-03 19:20:37 UTC

Created attachment 85945 [details]
krunner crash information generated by drkonqi.

Comment 2 Rodrigo Borges 2015-03-21 19:08:39 UTC

Similar issue happened to me while trying to send kdialog crash report with drkonqui.
'Non active' version reported of kdialog was 1.0 ;  I am running currently OpenSUSE 13.2 ; and in yast kdialog is reported as 14.12.3-16.5 version.

Comment 3 Harald Sitter 2019-07-02 14:09:45 UTC

Possibly related to bug #315073

Needs some investigation as to why exactly this went wrong though.

Comment 4 Harald Sitter 2019-07-03 12:28:37 UTC

*** Bug 351564 has been marked as a duplicate of this bug. ***

Comment 5 Harald Sitter 2019-07-03 12:30:47 UTC

*** Bug 353827 has been marked as a duplicate of this bug. ***

Comment 6 Harald Sitter 2019-07-03 12:31:41 UTC

*** Bug 354288 has been marked as a duplicate of this bug. ***

Comment 7 Olivier Delaune 2019-07-03 13:45:43 UTC

*** Bug 352139 has been marked as a duplicate of this bug. ***

Comment 8 Harald Sitter 2019-11-05 13:43:06 UTC

This is fixed at least as per 5.17 (probably even earlier). When drkonqi is given an unsuitable version it will now try its best to figure out a "generic" version to use instead.
I've just verified by filing a crash against dolphin 999 which correctly ended up in as version unspecified in bugzilla seeing as the version doesn't exist in bugzilla.