Ubuntu
pidgin package

Changing status using indicator-me applet causes pidgin to sign out, and signs in empathy instead

Bug #572760 reported by Pepe Maglutac on 2010-05-01

This bug report is a duplicate of: Bug #465034: Set status via me menu logs in empathy even if the user is using Pidgin. Edit Remove

This bug affects 3 people

	Status	Importance	Assigned to
Pidgin	Unknown	Unknown	pidgin-bugs #11935
The Me Menu	Confirmed	Undecided	Unassigned
pidgin (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: pidgin

Changing status using indicator-me applet causes pidgin to sign out, and signs in empathy instead.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pidgin 1:2.6.6-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Sat May 1 10:42:37 2010
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcEnviron:
LANG=en_PH.utf8
SHELL=/bin/bash
SourcePackage: pidgin

Tags:

Revision history for this message

Pepe Maglutac (jmaglutac) wrote on 2010-05-01:

Dependencies.txt Edit (5.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Dr. Kenobi (drkenobi) wrote on 2011-01-20:

This Bug is still present on Pidgin 2.7.9 and indicator-me 0.2.6. I solved this problem by removing Empathy.

Changed in pidgin (Ubuntu):
status:	New → Confirmed

Revision history for this message

Dr. Kenobi (drkenobi) wrote on 2011-01-20:

This is a problem with The Me Menu and not Pidgin (http://developer.pidgin.im/ticket/11935)

Changed in pidgin:
importance:	Undecided → Unknown
status:	New → Unknown
Changed in pidgin (Ubuntu):
status:	Confirmed → Invalid
Changed in indicator-me:
status:	New → Confirmed

Revision history for this message

Dr. Kenobi (drkenobi) wrote on 2011-01-21:

This particular bug has already been reported and is a duplicate of bug 465034, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.