Bug 145492 - Reporting a bug via the gui fails
Summary: Reporting a bug via the gui fails
Status: RESOLVED FIXED
Alias: None
Product: knetworkmanager
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-16 11:48 UTC by Thomas Zander
Modified: 2008-04-23 13:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Patch A (622 bytes, patch)
2007-07-23 14:32 UTC, Pino Toscano 		Details
Patch B (948 bytes, patch)
2007-07-23 14:33 UTC, Pino Toscano 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Zander 2007-05-16 11:48:21 UTC 
Version:           0.1.3.5.6 kubuntu (feisty) (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages

KNetworkmanager has a weird bugreporting dialog that does not use the webbrowser but apparantly uses email.
After typing my bugreport I pressed 'send' only to get a dialog stating:

Unable to send the bug report.
Please submit a bug report manually...
See http://bugs.kde.org/ for instructions.
Server said: "553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)"


This makes the extra efforts of not using a default bugreport dialog entirely unhelpful.
Comment 1 Pino Toscano 2007-07-23 14:31:42 UTC 
This happens because the bug address specified in the about data of KNetworkManager is a web site, while it should be an email address[1].

[1] http://api.kde.org/3.5-api/kdelibs-apidocs/kdecore/html/classKAboutData.html
Comment 2 Pino Toscano 2007-07-23 14:32:56 UTC 
Created attachment 21229 [details]
Patch A

Patch A: change the bug address to the default email address of KDE's bugzilla
Comment 3 Pino Toscano 2007-07-23 14:33:46 UTC 
Created attachment 21230 [details]
Patch B

Patch B: removing the manual setting of the bug address in flavour of the
default email address of KDE's bugzilla.
Comment 4 Pino Toscano 2008-04-23 13:32:17 UTC 
This has been fixed for KNetworkManager 0.2.1, using patch B.