Version: (using KDE 4.2.0)
Installed from: Fedora RPMs
I'm writing an application and KBugReport is not sending the bugs to the mail address I've configured.
It seems the problem is you are passing the arguments with extra spaces, like this: " --subject ", it should be: "--subject".
And when you finish writing data to the process you should close the channel, otherwise it will keep waiting forever.
The exit status of ksendbugmail is QProcess::NormalExit, but the exit status is 254, so you won't catch that with proc.exitCode() == 1, it's probably safer to do proc.exitCode() != 0.
Created attachment 30738 [details]
This patch should fix it.
This patch should fix the problem. However, it does nothing about the comparison proc.exitCode() == 1, I think you should have a good reason to make it that way.
Indeed things are broken in this area. I see a ksendbugmail crash, an smtp relay error not reported up to the dialog, and your patch looks correct too. Assigning to me, but I have to go so I'll look into all this next week or the week after.
SVN commit 1016321 by dfaure:
Fix error handling inside ksendbugmail; e.g. when no internet available. Incomplete qt3 porting.
M +8 -7 main.cpp
M +12 -14 smtp.cpp
M +1 -0 smtp.h
WebSVN link: http://websvn.kde.org/?view=rev&revision=1016321
SVN commit 1016338 by dfaure:
Commit patch by Ezequiel R. Aguerre to make kbugreport work again when sending bugs by email.
It was another qt3 porting bug: it was passing " --subject " instead of "--subject".
And closeWriteChannel is necessary otherwise it will keep waiting forever.
M +8 -4 kbugreport.cpp
WebSVN link: http://websvn.kde.org/?view=rev&revision=1016338
SVN commit 1016340 by dfaure:
The exitcode was 254 when passing wrong args to ksendbugmail indeed, so let's not just check for 1, but for != 0.
M +1 -1 kbugreport.cpp
WebSVN link: http://websvn.kde.org/?view=rev&revision=1016340