| 2011-01-05 18:38:13 |
Marius Gedminas |
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?). |
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
|
|
