Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Dec 2008 21:29:05 GMT
From:      Lars Stokholm <lars.stokholm@gmail.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   ports/129350: purple-remote can't communicate with Pidgin
Message-ID:  <200812012129.mB1LT5d4085217@www.freebsd.org>
Resent-Message-ID: <200812012130.mB1LU8J1028736@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         129350
>Category:       ports
>Synopsis:       purple-remote can't communicate with Pidgin
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Dec 01 21:30:08 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Lars Stokholm
>Release:        FreeBSD 7-STABLE
>Organization:
>Environment:
FreeBSD eee 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Sun Sep 28 00:59:50 CEST 2008     root@eee:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
Controlling a running Pidgin with purple-remote doesn't work:

%purple-remote "setstatus?status=away&message=test"
No existing libpurple instance detected.

A similar (if not the same) problem has been discussed here: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/236813
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200812012129.mB1LT5d4085217>