KDE bug reporter requires working Kmail config

[Removed by request]

Binary package hint: kde

I managed to crash Amarok a few minutes into my new Kubuntu install. This crash was nicely detected, but the handling didn't work for me:

1. It fired up a new Kmail message (nicely worded)
2. When I hit 'send' as suggested, I got a warning that no file was attached
3. When I continued sending, Kmail told me that it wasn't configured to send mail

So the end result was a bit messy.

Suggestions:

1. Don't rely on e-mail to send bug reports; send them directly over the Internet (maybe fall back to e-mail if offline).

2. Make sure there is an attachement, or that you don't refer to there being one (KDE's attachment detection is very handy but the end result here will confuse users).

[Sarah Kowalik (hobbsee-deactivatedaccount)]

It works in thunderbird, or whatever default client you set.

I expect that the other option is to set up a MTA - and that's likely to be even more painful, as not that many people know how to do it.

[DarkMageZ (darkmagez)]

this is even worse for gnome users (who use amarok). as amarok will crash and gdb will do alittle processing while the application looks like it has hung and then it'll spit out an error message about the mail client not being configured. this breaks what apport was designed to take care of and prevents a core-dump from being generated which could have been retraced. 3 crash reports lost so far.

[Yuriy Kozlov (yuriy-kozlov)]

Assigning to amarok since it's the only application I know of that does automatic bug reporting when it crashes.

[Myriam Schweingruber (myriam)]

Amarok doesn't use email notification anymore. This bug can be closed.

[Harald Sitter (apachelogger)]

Still does in Kubuntu.

[Jonathan Thomas (echidnaman)]

It won't in Jaunty with Amarok2.

[Jonathan Thomas (echidnaman)]

Fix released to Jaunty.