Twitter no longer works in version 3.0.5

Bug #1190507 reported by Rena Kunisaki
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bitlbee (Debian)
Fix Released
Unknown
bitlbee (Ubuntu)
Fix Released
Undecided
Unassigned
Lucid
Won't Fix
Undecided
Unassigned
Precise
Won't Fix
Undecided
Unassigned
Quantal
Won't Fix
Undecided
Unassigned

Bug Description

Version 3.0.5 uses an old Twitter API which is no longer functional, but this version is still the default in Quantal and earlier. These distros need to be updated to a working version.

[Impact]
This bug renders Twitter services unusable from Bitlbee on 12.04 and previous Ubuntu releases. The proposed fix is to upgrade them to Bitlbee 3.2 or newer which use the new (now mandatory) Twitter API.

[Test Case]
Anyone who already has Bitlbee linked to a Twitter account on these releases will find it not working since the API change, without doing anything themselves.
Those who don't already have it set up should be able to install the 'bitlbee' package and follow the instructions on http://wiki.bitlbee.org/HowtoTwitter to link it to a Twitter account, although those steps will likely fail as well.

[Regression Potential]
Updating to version 3.2 shouldn't break anything, although the Twitter UI is slightly different from previous versions (IDs shown in hex, more frequent updates, able to receive DMs).

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in bitlbee (Ubuntu):
status: New → Confirmed
Revision history for this message
Logan Rosen (logan) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Saucy Salamander.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

Changed in bitlbee (Ubuntu):
status: Confirmed → Fix Released
Changed in bitlbee (Debian):
status: Unknown → Confirmed
Revision history for this message
Rena Kunisaki (i-am-inuyasha) wrote :

Uh yes, a fix for previous Ubuntu versions was the entire point of this report. It looks like this report already complies with steps 1 and 2 (it's public and marked "fix released"), and fits the "severe regressions" case (significant functionality of the application is no longer usable because it depends on a web API which is no longer active) and the "safe patch for non-critical application" case (bitlbee is not a critical application, and the newer, working versions are already in use on newer Ubuntu releases). Is there anything else I need to do?

Revision history for this message
Logan Rosen (logan) wrote :

Could you please follow the third step as well? I'll have to update that response.

Revision history for this message
Rena Kunisaki (i-am-inuyasha) wrote :

Alright, how does that look?

description: updated
Revision history for this message
Rolf Leggewie (r0lf) wrote :

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Changed in bitlbee (Ubuntu Quantal):
status: New → Won't Fix
Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in bitlbee (Ubuntu Lucid):
status: New → Won't Fix
Changed in bitlbee (Debian):
status: Confirmed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in bitlbee (Ubuntu Precise):
status: New → Won't Fix
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.