"Error when sending message" warning should distinguish between cause of going offline

Bug #647002 reported by Jon Loldrup
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Empathy
Expired
Wishlist
One Hundred Papercuts
Triaged
Wishlist
Unassigned
empathy (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

When a user goes offline in Empathy, Empathy then states "error when sending message $user: offline".

This error message does not distinguish between the many causes of a user going offline. Ideally Empathy would say whether it is me, my buddy, or the transport layer (eg. the server in between me and my friend) that has gone offline causing the message(s) not to be delivered.

For example, it stating "Viktor has gone offline" would be more useful if the other user has gone offline (Viktor being the name of the person I /was/ chatted with).

Revision history for this message
Jon Loldrup (loldrup) wrote :
Changed in hundredpapercuts:
status: New → Confirmed
Paul Sladen (sladen)
description: updated
summary: - Empathy error message leaves users in the dark
+ Error when sending message should distinguish between cause of offline
summary: - Error when sending message should distinguish between cause of offline
+ "Error when sending message" warning should distinguish between cause of
+ going offline
Changed in empathy:
importance: Undecided → Unknown
status: New → Unknown
Changed in empathy:
importance: Unknown → Wishlist
status: Unknown → New
Revision history for this message
Martin Vysny (vyzivus) wrote :

In my case, I received the "Error sending message: offline" message while I was online and my chat partner suddenly went offline. This is a bit strange because Empathy should be able to deliver the message to the server at least.
Anyway, even if I am off-line, Empathy should remember the message and it should try to deliver it when a connection to the server is established. It should not require the user to manually try to re-deliver the message. Thanks!

Revision history for this message
Martin Vysny (vyzivus) wrote :

Also, GTalk often fails to deliver messages when the contact is offline. Pidgin reports the following error:
Message delivery to ... failed: (Code 503)

Vish (vish)
Changed in hundredpapercuts:
assignee: nobody → Papercuts Ninja (papercuts-ninja)
importance: Undecided → Low
milestone: none → nt2-social-networking
status: Confirmed → Triaged
Vish (vish)
Changed in hundredpapercuts:
assignee: Papercuts Ninja (papercuts-ninja) → nobody
assignee: nobody → Papercuts Ninja (papercuts-ninja)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in empathy (Ubuntu):
status: New → Confirmed
Changed in hundredpapercuts:
milestone: nt2-social-networking → precise-2-social-networking
Bilal Shahid (s9iper1)
Changed in empathy (Ubuntu):
importance: Undecided → Wishlist
status: Confirmed → Triaged
Changed in hundredpapercuts:
milestone: precise-2-social-networking → papercuts-s-empthy
Changed in hundredpapercuts:
assignee: Papercuts Ninjas (papercuts-ninja) → nobody
importance: Low → Wishlist
Changed in empathy:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.