Take a look in $HOME/.dbus/session-bus/ to make sure you don't have any
extra session files. You can figure out which one to keep by matching
up the id on the first line of the file with the running process:
[EMAIL PROTECTED]:~$ ps -eaf | grep dbus-launc[h]
chin 6678 1 0 Jun19 ?
If I start pidgin like this, purple-remote works as expected:
#!/bin/sh
. .dbus/session-bus/*
export DBUS_SESSION_BUS_ADDRESS DBUS_SESSION_BUS_PID DBUS_SESSION_BUS_WINDOWID
exec /usr/bin/pidgin
--
purple-remote doesn't find libpurple instance
https://bugs.launchpad.net/bugs/236813
You received
Matthias, are there any other questions we can answer on this? After a
couple years of waiting for what seems to be just an administrative
decision, it would be really nice to see some progress.
--
Request for silc-toolkit Inclusion in Main
https://bugs.launchpad.net/bugs/211179
You received thi
Well now I know what that button does. Sorry for the clutter. This is
not an acpi related issue.
** Changed in: acpi-support (Ubuntu)
Status: New => Invalid
--
purple-remote doesn't find libpurple instance
https://bugs.launchpad.net/bugs/236813
You received this bug notification because
** Tags added: hardy pidgin
--
purple-remote doesn't find libpurple instance
https://bugs.launchpad.net/bugs/236813
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
Also having this issue. Changed status to Confirmed. It looks like
pidgin is registering on the DBus system bus, not the session bus. But
purple-remote looks like it is trying to find libpurple instances on the
session bus. I really don't know how this DBus stuff works but am more
than happy to
