Bug 291346

Summary:	kbugreport fails to fill the correct app version and distribution information.
Product:	[Frameworks and Libraries] kdelibs	Reporter:	karaluh <karaluh>
Component:	kbugreport	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	CONFIRMED ---
Severity:	normal	CC:	giecrilj, nantocsem
Priority:	NOR	Keywords:	reproducible
Version:	4.9.5
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description karaluh 2012-01-12 09:40:08 UTC

Version:           unspecified (using KDE 4.7.4) 
OS:                Linux

As in summary, when reporting bug using Helo->Report a bug the KDE and application version and the software distribution method aren't filled corectly.

Reproducible: Always

Steps to Reproduce:
.


Expected Results:  
.

Comment 1 Christopher Yeleighton 2012-03-30 01:57:24 UTC

Steps to Reproduce:

  1.  Tell Dolphin to report a bug.
  2.  Tell KBugReporter to report a bug against Konqueror instead.
  3.  Tell Konqueror to report a bug.

Actual Results: 

  1.  Version: 1.7
  2.  Version: unknown
  3.  Version: 4.7.2 (4.7.2) "release 5"

Expected Results: 

  2. Version: 4.7.2 (4.7.2) "release 5"

Of course, the example is silly; however, the problem becomes serious when you wish to report a bug against KIO for example because there is no stand-alone host for KIO.

Comment 2 Jekyll Wu 2013-01-21 23:32:32 UTC

The version problem is almost always due to the product on bugs.kde.org lacking the version you are just using. As a counter example,  I can guarantee to you if you use "Help -> Report bug" in Konsole to report a bug against konsole, the version information will always be correctly filled. Not much thing can be done from the side of kbugreport, at least with its current implementation. 

Distribution information is a different and valid problem . kbugreport just sends some platform information that bugs.kde.org doesn't understand. .

Comment 3 Jekyll Wu 2013-01-21 23:33:54 UTC

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

Comment 4 Jekyll Wu 2013-01-21 23:37:15 UTC

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