| Summary: | Amarok: creates a kmail rather than creating a normal backtrace | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Darrell <darrella> |
| Component: | non-core programs | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bugwatch, darrella, kb9vqf |
| Priority: | P5 | ||
| Version: | R14.0.0 [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Darrell
2013-01-02 12:07:48 CST
One thing the Amarok crash handler does correctly is to generate a backtrace for all threads. The standard TDE crash handler needs to be updated to do the same, then the Amarok-specific crash handler can be removed. That is fine. My focus with this report is amarok starts kmail. I don't use any other mail client, but I presume amarok starts the client configured by the user in kcontrol. If amarok is hard-coded to use kmail then that will be doubly frustrating to non kmail users. Fixed in GIT hashes 1fbdb78 (tdebase) and 534ba7f (amarok). Thanks for reporting! By fixed you mean that 1) the standard crashhandler has been updated and 2) amarok should no longer open kmail but instead open the crashhandler dialog? Amarok is pretty stable. We might wait a long time to actually test this. :-) (In reply to comment #4) > By fixed you mean that 1) the standard crashhandler has been updated and 2) > amarok should no longer open kmail but instead open the crashhandler dialog? Yes > Amarok is pretty stable. We might wait a long time to actually test this. :-) This is a good thing. :-) |