Pidgin Helper not showing unread messages

Bug #740168 reported by MrVertigo
36
This bug affects 8 people
Affects Status Importance Assigned to Milestone
DockManager
New
Undecided
Unassigned

Bug Description

Hi! I'm using docky for some time and I want to report this bug:

A few weeks ago, docky ceased to show the unread messages count on pidgin's icon. In debug mode, it shows the information listed below. I did a search on google related to this problem, but I didn't find it. Sorry if it's not a real bug.

Docky version: 2.0.6 Release
Distro in use: Ubuntu 10.04, kernel 2.6.32-30-generic
X Version: X.Org X Server 1.7.6
Video card: nvidia quadro fx 580
GNOME Version: 2.30.2
Mono version: Mono JIT compiler version 2.6.7
Python: 2.6.5

Revision history for this message
MrVertigo (nahumet) wrote :
description: updated
Robert Dyer (psybers)
affects: docky → dockmanager
Revision history for this message
MrVertigo (nahumet) wrote :

Making a deeper research and having a look to the code, I've ended at this web page:

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

It seems that the method used in the helper, "PurpleConversationGetData" isn't exported through DBUS by pidgin anymore.

I'm working on a change to the helper to obtain the number of unread messages through the pidgin API. If I have success, I'll post it here.

Revision history for this message
MrVertigo (nahumet) wrote :

I found a workaround, that you can use if you're having the same problem and you miss the unread messages badge on pidgin 2.7.11 as I did:

- Go to Administration/System and open Synaptic Package Manager
- In the text box, search for "libpurple"
- You will find two packages, libpurple-bin and libpurple0. Select them, and go to the menu "Package-->Force version"
- In the dialog box that will appear, select version: 2.6.6-1ubuntu4, and click on "Force version"
- Click on the button "Apply", and restart Pidgin. The pidgin helper will behave now as usual, showing the number of unread messages in the badge.

Revision history for this message
Andreas (arabus) wrote :

The workaround mentioned above does not offer 2.6.6 any more to me on ubuntu maverick, all i get was 2.7.3, and this one is affected too:

Log see below:

[Error 09:32:43.647] [Helper] pidgin_control.py :: Traceback (most recent call last):
[Error 09:32:43.647] [Helper] pidgin_control.py :: File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 576, in msg_reply_handler
[Error 09:32:43.647] [Helper] pidgin_control.py :: reply_handler(*message.get_args_list(**get_args_opts))
[Error 09:32:43.647] [Helper] pidgin_control.py :: File "/usr/share/docky/helpers/pidgin_control.py", line 87, in list_names_handler
[Error 09:32:43.647] [Helper] pidgin_control.py :: self.update_badge()
[Error 09:32:43.647] [Helper] pidgin_control.py :: File "/usr/share/docky/helpers/pidgin_control.py", line 141, in update_badge
[Error 09:32:43.648] [Helper] pidgin_control.py :: count = count + self.pidgin.iface.PurpleConversationGetData(conv, "unseen-count")
[Error 09:32:43.648] [Helper] pidgin_control.py :: File "/usr/lib/pymodules/python2.6/dbus/proxies.py", line 140, in __call__
[Error 09:32:43.648] [Helper] pidgin_control.py :: **keywords)
[Error 09:32:43.648] [Helper] pidgin_control.py :: File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
[Error 09:32:43.648] [Helper] pidgin_control.py :: message, timeout)
[Error 09:32:43.648] [Helper] pidgin_control.py :: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "PurpleConversationGetData" with signature "is" on interface "im.pidgin.purple.PurpleInterface" doesn't exist

(Now google should find this report when somebody search for the message in google too... ;)

Revision history for this message
MrVertigo (nahumet) wrote :

Sure, I forgot to specify that my workaround was only tested on Ubuntu 10.04, Lucid Lynx. Maybe adding the purple repos for lucid to maverick you could get the 2.6 packages. Or if somebody wants them, I can upload to any host.

Revision history for this message
dpsk (idups1k) wrote :

Have exactly the same issue, with the same trace :( Is there some workaround with maverick?

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.