Pidgin 2.2.0 in Gutsy

Bug #139686 reported by Cosimo
42
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Pidgin is one of the most used applications in Ubuntu for almost all Users.
The new version 2.2.0 (already available) contains more than 130 bugfixes some of them marked as "critical" New Protocols available (MySpaceIM) etc..
We should include this version in Gutsy, I guess we're still on time to make an exception. I hope someone from the release team considers this important update.

Tags: upgrade

Related branches

CVE References

Revision history for this message
Murat Gunes (mgunes) wrote :

Upstream changelog:

Version 2.2.0 (09/13/2007):
 http://developer.pidgin.im/query?status=closed&milestone=2.2.0

 Libpurple:
 * New protocol plugin: MySpaceIM (Jeff Connelly, Google Summer of
   Code)
 * XMPP enhancements. See
    http://www.adiumx.com/blog/2007/07/soc-xmpp-update.php (Andreas
   Monitzer, Google Summer of Code for Adium)
 * Certificate management. Libpurple will validate certificates on
   SSL-encrypted protocols (William Ehlhardt, Google Summer of Code)
 * Some adjustments were made to fix sending messages when using
   the MSN HTTP method. (Laszlo Pandy)
 * Yahoo! Chat is fixed.
 * Some AIM file transfer issues between Pidgin and other clients
   have been fixed. (Kyryll A Mirnenko)
 * Properly restore idle status and time for AIM and ICQ accounts
   when they reconnect after being disconnected.

 Pidgin:
 * Insert Horizontal Rules and Strikethrough text from toolbar.
 * Option to show protocol icons in the buddy list, from the
   Buddies > Show menu. (Justin Heiner)
 * Ability to build with native, non-X11 GTK+ on OSX. (Anders
   Hasselqvist)
 * Remember the 'Enable Sounds' setting for a conversation.
 * Right-clicking the empty space in the formatting toolbar
   allows you to toggle back to the old "ungrouped" version.
 * Protocols supporting account registration via Pidgin now show
   a descriptive checkbox instead of a vague "Register" button.
 * Fixed a bug where a tab would be shown on single conversations
   when tabs were disabled.

 Finch:
 * Per-conversation mute and logging options (accessible from the menu).

Revision history for this message
Caspar Clemens Mierau (leitmedium) wrote :

+1 from for the request. Sadfully the Debian did not package 2.2.0 yet so we cannot just sync from there and need to package by or own. So this might get an issue as we already have Tribe5. On the other hand the mixture of fixes and new features should be a great benefit at all.

Revision history for this message
Rich (rmidwinter) wrote :

+1

Cosimo (kosimo)
description: updated
Revision history for this message
Achim (ach1m) wrote :

1+
I also think that Pidgin 2.2.0 should make it into gutsy.

Murat Gunes (mgunes)
Changed in pidgin:
status: New → Incomplete
Revision history for this message
Janek (thefoxx) wrote :

+1
The Jabber-Improvements sounds very great

Revision history for this message
Alec Wright (alecjw) wrote :

+1

Changed in pidgin:
status: Incomplete → Confirmed
Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

subscribing ubuntu release.

Or is this covered under the blanket GNOME exception?

Revision history for this message
Cosimo (kosimo) wrote :

No is not...

Revision history for this message
junk123 (junk123-deactivatedaccount-deactivatedaccount) wrote :

+1

Revision history for this message
Dan Bishop (danbishop) wrote :

+1 all these bug fixes and new protocols... it must be worth it :D

Revision history for this message
Nick B. (futurepilot) wrote :

+1 Please ;)

Revision history for this message
Hew (hew) wrote :

+1
These bugfixes are so important! Pidgin is, as the OP said, one of the most used applications. It should be the best it can be as it will be a primary feature of Ubuntu Gutsy.

Revision history for this message
KraetziChriZ (christian.b) wrote :

+1 :D

Revision history for this message
Sebastien Bacher (seb128) wrote :

could user stop adding "+"1 comment, that has no use and you are creating extra mail load for maintainers and slow the packaging of the new version

Revision history for this message
Martin Pitt (pitti) wrote :

Please provide a PPA with the new version, so that it can get some more widespread testing. I am willing to consider it, but for the same reason why so many of you want the new version, we cant risk major regressions due to it either.

Revision history for this message
Alec Wright (alecjw) wrote :

"... and slow the packaging of the next version..."
So it's happening then?

Revision history for this message
Sebastien Bacher (seb128) wrote :

no, it's not, today is sunday which is a non working day in Europe, I'll have a look next week rather

Revision history for this message
nclm (nclm) wrote :
Revision history for this message
Brett Alton (brett-alton-deactivatedaccount) wrote :

I'm doing this as per: https://wiki.ubuntu.com/FreezeExceptionProcess#head-9523bc4076ff011324d67cddc97969ec609618d6

code: diff -ruN pidgin-2.1.1/ pidgin-2.2.0/ | diffstat > diffstat.txt

Revision history for this message
Brett Alton (brett-alton-deactivatedaccount) wrote :

I'm doing this as per: https://wiki.ubuntu.com/FreezeExceptionProcess#head-9523bc4076ff011324d67cddc97969ec609618d6

code: diff -u pidgin-2.1.1/ChangeLog pidgin-2.2.0/ChangeLog > changelog.diff

Revision history for this message
Brett Alton (brett-alton-deactivatedaccount) wrote :

Then finally,

code: diff -u pidgin-2.1.1/ pidgin-2.2.0/ > changes_patch.diff

Revision history for this message
Brett Alton (brett-alton-deactivatedaccount) wrote :

TERRIBLY SORRY.

The last one didn't have the recursive function running. Here's the new patch.diff:

code: diff -ru pidgin-2.1.1/ pidgin-2.2.0/ > changes_patch2.diff

Revision history for this message
Alec Wright (alecjw) wrote :

Oops Ive realised that i shouldn't have marked it as confirmed, as confirmed in a freeze exception request means that it's been accepted. Marking as new,

Changed in pidgin:
status: Confirmed → New
Revision history for this message
Scott Kitterman (kitterman) wrote :

pidgin is in Main, not Universe, so I've unsubscribed MOTU-UVF. You need to follow the process for a Main UVFe, not a Universe one.

Revision history for this message
Brett Alton (brett-alton-deactivatedaccount) wrote :

Well, for UVFe, it states:

* An excerpt from the upstream changelog and/or release notes listing (only) the changes relative to the current version in Ubuntu
 -- which I did: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/139686/comments/20, and so did Murat: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/139686/comments/1

* If the upstream version contains changes which require exceptions to other freeze guidelines, additional information should be provided according to the instructions below:
** Exception requests must include the following additional details:
*** diffstat output showing the magnitude of code changes relative to the current version in Ubuntu
 -- which I did: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/139686/comments/19
*** An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
**** Builds
**** Installs
**** Does not break packages which depend on it, or that corresponding updates have been prepared
 -- which Nico has done and needs help testing here: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/139686/comments/18

So I think we should have everything underway.

Revision history for this message
Brett Alton (brett-alton-deactivatedaccount) wrote :

I added 'deb http://ppa.launchpad.net/zanglang/ubuntu gutsy main' via Software Sources and then ran the update in the terminal.

I've attached the log.

Revision history for this message
Brett Alton (brett-alton-deactivatedaccount) wrote :

As far as I can tell, everything is running swell, including Finch. Here's a screenshot.

Revision history for this message
Will Farrington (wcfarrington) wrote :

I've been using the above packages for the past several days.

There was one case of an isolated crash, but I've been unable to reproduce this crash since. Everything seems to work just fine - all very stable.

Revision history for this message
Martin Kaufmann (martin.kaufmann) wrote :

i got a Segmentation Fault by running Pidgin 2.2.0 from deb http://ppa.launchpad.net/zanglang/ubuntu gutsy main:

riot@tux:~$ pidgin
bad image index
bad image index
bad image index
bad image index
Segmentation fault (core dumped)

Anyone an idea what i did wrong or maybe has the same problem?

Revision history for this message
Martin Kaufmann (martin.kaufmann) wrote :

I tryed to run Pidgin as Root and it works without Root-Rights it crashs

Revision history for this message
Murat Gunes (mgunes) wrote :
Revision history for this message
Alec Wright (alecjw) wrote :

Excellent! So it's just a simple merge :)

Revision history for this message
Martin Pitt (pitti) wrote :

Upgrade from "deb http://ppa.launchpad.net/zanglang/ubuntu gutsy main" does not work at all for me.

Revision history for this message
Martin Pitt (pitti) wrote :

Sorry, that's because the PPA does not have amd64 packages (yet?).

Revision history for this message
Jerry Chong (zanglang) wrote :

Sorry, for some reason 2.2.0~ppa2 is still on "Pending Removal" status for my PPA and not starting the rebuild for both architectures yet. I'm not quite sure what's causing the delay... still getting the hang of these packaging stuff. :)

I hope my package is not what's causing the problems. Not sure about the bad image index errors (icon cache not updated/packaging error with pidgin-data perhaps?)... we should probably figure out the causes in a separate bug report if it keeps reoccuring.

For now, since 2.2.0 has just landed in sid should I merge from Debian onto the PPA?

Revision history for this message
Flávio Martins (flavioxmartins) wrote :

Please test the new packages of pidgin at

deb http://ppa.launchpad.net/xhaker/ubuntu gutsy main

(take in mind the repository also contains other software packages)

Attaching the proper debdiff for ubuntu1 here.

Revision history for this message
Martin Pitt (pitti) wrote :

I tested the new packages and also quickly reviewed the debdiff. I don't see a significant difference to 2.1.1, though (Jabber is still broken, see bug 116170, rest works as usual).

OK from my side if the desktop team wants to take this.

Revision history for this message
Caspar Clemens Mierau (leitmedium) wrote :

Thanks Flávio for providing the binary. Until now it runs without crashes for me. I will continue testing.

Can you please check #52801? In my eyes proxy settings is still an issue in pidgin under ubuntu.

In the windows version you have a global pidgin setting allowing you to set a proxy/noproxy setting for *all* procotolls and to override it with every account setting. In the ubuntu or maybe linux version you have to set it for each protocol - the global dialog boxes are just missing. You can try to mess around with the Gnome proxy settings but that is still buggy. So my question: Would it be possible to enable this dialogue in 2.2.0?

I will attach two screenshots showing the differences.

Revision history for this message
Caspar Clemens Mierau (leitmedium) wrote :
Revision history for this message
Caspar Clemens Mierau (leitmedium) wrote :

Please keep in mind while/if considering implementing this:

http://developer.pidgin.im/ticket/3092

Revision history for this message
Sebastien Bacher (seb128) wrote :

pidgin (1:2.2.0-1ubuntu1) gutsy; urgency=low

  * Sync with Debian (LP: #139686)
  * debian/control:
    - Build-Depends on liblaunchpad-integration-dev, intltool, libnm-glib-dev
    - don't Build-Depends on libsilc-1.1-2-dev | libsilc-dev (>= 1.1.1),
      the library is in universe
    - changed the transition version to use the ubuntu epoch number
    - list gaim transitionnal package for updates
    - pidgin-data Replaces gaim-data
    - updated the maintainer for Ubuntu
  * debian/copyright:
    - build in the source, that's a soyuz requirement to accept the upload
  * debian/gaim.links:
    - gaim compatibility symlinks
  * debian/patches/01_lpi.patch:
    - launchpad integration patch.
  * debian/patches/02_autoconf.patch:
    - configure update
  * debian/patches/04_let_crasher_for_apport.patch:
    - don't catch crashes, apport does that.
    - fixes apport having broken backtraces for gaim
  * debian/patches/14_xulrunner_nss.patch:
    - removed for Ubuntu, firefox nss is used
  * debian/patches/99_default_to_irc_ubuntu_com.patch:
    - set default irc server to irc.ubuntu.com
  * debian/pidgin-dbg.preinst, debian/pidgin-dev.preinst, debian/pidgin.preinst:
    - use the correct transition version
  * debian/prefs.xml:
    - set the notify by default (Ubuntu: #13389)
  * debian/rules:
    - add translation domain and update template
    - build with network-manager and without libsilc
    - don't remove the copyright on clean

 -- Sebastien Bacher <email address hidden> Wed, 19 Sep 2007 18:58:28 +0200

Changed in pidgin:
status: New → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

The previous debdiff dropped the Debian changes and the beta freeze is tomorrow so I've merged on Debian and uploaded 2.2.0, thanks everybody for the work and testing

Revision history for this message
Cosimo (kosimo) wrote :

Important Security Bug #

Pidgin Security Advisory
Title MSN Remote "Nudge" DoS
Date 27 September 2007
CVE Name CVE-2007-4996
Discovered By Evan Schoenberg
Summary MSN nudges sent from unknown buddies can cause libpurple to crash
Description A remote MSN user that is not on the buddy list can cause a denial of service (crash) by sending a nudge message. The protocol plugin attempts to look up the buddy's information and accesses an invalid memory location if the user is not on the buddy list.
Fixed in Version 2.2.1
Fix The nudge functionality in the MSN protocol has been rewritten to avoid an unnecessary lookup of buddy information.

Return to Security Advisory Index

New Pidgin version 2.2.1 fixes that:

Release notes:
Release Name: 2.2.1

Notes:
2.2.1 (9/28/2007):
        Richard: We have some new code in the pipeline, but it's not quite
        ready for a general release. Instead, this is basically a bug fix
        release.

        Luke: Unfortunately the necessity of this bug fix release means
        some of the tickets that have been closed as part of the 2.2.1
        milestone are not actually fixed yet. We have grabbed as many
        of the changes as we could while avoiding those that are as
        yet unstable though, and this should still be a marked
        improvement over 2.2.0. We have spent a lot of time since the
        last release looking at the tickets that have been submitted
        and many of them have been closed.

        Stu: I haven't NEWS'd in a while. I haven't actually done much for
        too long also, maybe I'll find some time soon. This release is
        basically what 2.2.0 should have been - it actually compiles this
        time.

Changes:
Version 2.2.1 (09/29/2007):
        http://developer.pidgin.im/query?status=closed&milestone=2.2.1
                NOTE: Due to the backporting that happened for the actual
                      release, it is possible bugs marked as fixed in 2.2.1
                      will not be fixed until 2.2.2.

        libpurple:
        * A few build issues on Solaris were fixed.
        * Cancelling the password prompt for an account will no longer leave
          it in an ambiguous state. (It will be disabled.)
        * Fixed an erroneous size display for MSN file transfers. (galt)
        * Fixed multiple memory leaks, particularly in XMPP and MySpace
          protocols
        * Fixed remembering proxy preferences and status scores
        * Gmail notifications are better tracked

        Pidgin:
        * Fixed keyboard tab reordering to move tabs one step instead of two.
        * You should no longer lose proxy settings when Pidgin is restarted.
        * Fixed detection of X11 when compiling

        Finch:
        * Pressing 'Insert' in the buddylist will bring up the 'Add Buddy' dialog.

Revision history for this message
Sebastien Bacher (seb128) wrote :

We know about new version, not need to copy the changes on a closed bug

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.