| Summary: | [libpurple limitation] Emit SendError signals properly | ||
|---|---|---|---|
| Product: | Telepathy | Reporter: | Will Thompson <will> |
| Component: | haze | Assignee: | Will Thompson <will> |
| Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Will Thompson
2007-11-07 05:59:47 UTC
In <http://git.collabora.co.uk/?p=user/wjt/telepathy-haze;a=shortlog;h=refs/heads/send-error> (which I hope will be merged for 0.3.0) the error message from libpurple is placed into the delivery report's "delivery-error-message" header, and as the delivery report's body (which is supposed to be human-readable localized errors from the server, so this is not too far away from the spec). A side-effect is that SendError will now have an empty string as the text parameter. Protocols don't in general tell you which message failed; even for those that do, libpurple doesn't expose that information in any meaningful way. Fixed as best we can for now in 0.3.0. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.