Gwibber doesn't honor refresh interval preference
Bug #487266 reported by
Ken VanDine
on 2009-11-23
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Gwibber |
Low
|
Ken VanDine | ||
| | gwibber (Ubuntu) |
Low
|
Ken VanDine | ||
Bug Description
The preferences dialog allows setting of the refresh interval, but regardless of the value gwibber always refreshes every 5 minutes.
Ken VanDine (ken-vandine)
on 2009-11-23
| Changed in gwibber: | |
| assignee: | nobody → Ken VanDine (ken-vandine) |
| importance: | Undecided → Low |
| status: | New → Confirmed |
| Changed in gwibber (Ubuntu): | |
| assignee: | nobody → Ken VanDine (ken-vandine) |
| importance: | Undecided → Low |
| status: | New → Confirmed |
Ken VanDine (ken-vandine)
on 2009-11-24
| Changed in gwibber: | |
| status: | Confirmed → Fix Committed |
| Omer Akram (om26er) wrote : | #1 |
| Changed in gwibber: | |
| status: | Fix Committed → Confirmed |
| Changed in gwibber (Ubuntu): | |
| status: | Confirmed → Triaged |
| Omer Akram (om26er) wrote : | #2 |
revision 707 fixes this
| Changed in gwibber: | |
| status: | Confirmed → Fix Committed |
| Launchpad Janitor (janitor) wrote : | #3 |
This bug was fixed in the package gwibber - 2.29.95-0ubuntu1
---------------
gwibber (2.29.95-0ubuntu1) lucid; urgency=low
* New upstream release
- Fixed threadlock in keyring call which made gwibber-service
utilize 100% of a CPU (LP: #554005)
- Handle parsing of bad message content better
- Fixed color handling regression in gwibber-accounts
- Respect full name preference in notification bubbles
- Reset refresh interval to pick up changes in settings (LP: #487266)
-- Ken VanDine <email address hidden> Thu, 08 Apr 2010 16:36:07 -0400
| Changed in gwibber (Ubuntu): | |
| status: | Triaged → Fix Released |
Omer Akram (om26er)
on 2010-04-09
| Changed in gwibber: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug still exist in 2.29.90.1