should inform about errors if a message can't be send
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Gwibber |
New
|
Undecided
|
Unassigned | ||
| gwibber (Ubuntu) |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Binary package hint: gwibber
Using Gwibber 2.30.0.1 on Ubuntu 10.04.
I just wanted to send a dent to identi.ca. The message disappeared from the input box and the spinner in the menu bar appeared. But after a while, the spinner went away, but no message appeared in the message stream.
I then checked the log (~/.cache/
2010-05-17 09:40:37,112 - Gwibber Dispatcher - ERROR - Failed to communicate with https:/
2010-05-17 09:40:37,112 - Gwibber Dispatcher - ERROR - Failed to parse the response, error was: No JSON object could be decoded
2010-05-17 09:40:37,113 - Gwibber Dispatcher - ERROR - <identica:send> Operation failed
2010-05-17 09:40:37,121 - Gwibber Dispatcher - INFO - Loading complete: 4 - ['Failure']
I never received any notification about the error, and my message was lost. I would expect two things to happen in such a situation:
1. Gwibber should inform me that an error occurred and that the message could not be sent.
2. Ideally, my message would be saved and Gwibber would allow me to resend it later. E.g., Gwibber could add it back to the input box in case of a failure, or at least store it in some 'failed_
| Victor Vargas (kamus) wrote | #1 |
| Changed in gwibber (Ubuntu): | |
| importance: | Undecided → Low |
| Victor Vargas (kamus) wrote | #2 |
| summary: |
- Gwibber doesn’t inform user about errors + should inform about errors if a message can't be send |
| Changed in gwibber (Ubuntu): | |
| importance: | Low → Wishlist |
| status: | New → Triaged |
@Frederik, please fill a new report for you second requirement. BTW, I think there is another report for your first issue (getting a notification error when you are not be able to connect to a service).