← Back to team overview

gwibber-bugs team mailing list archive

[Bug 696448] Re: no warning if a message cannot be sent; no way to recover the message

 

** Changed in: gwibber (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gwibber (Ubuntu)
       Status: Incomplete => Triaged

** Also affects: gwibber
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/696448

Title:
  no warning if a message cannot be sent; no way to recover the message

Status in Gwibber:
  New
Status in “gwibber” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gwibber

Sometimes gwibber finds itself unable to send a message (see e.g. bug 696445).  There's no warning shown to the user that that's the case, and the message itself is lost forever.

Gwibber should store outgoing messages in persistent storage somewhere, and allow the users to retrieve or attempt to resend them if those messages cannot be sent in a reasonable amount of time (say, 5 minutes?).
--- 
Architecture: i386
DistroRelease: Ubuntu 10.10
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: gwibber 2.32.2-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=lt_LT:lt:en_GB:en
 LC_CTYPE=lt_LT.UTF-8
 PATH=(custom, user)
 LANG=lt_LT.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8
Tags: maverick
Uname: Linux 2.6.35-24-generic i686
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare