Right after login: purple-remote crashed with DBusException in call_blocking()

[Tarnay Kálmán]

Binary package hint: pidgin

I didn't really do anything... I just started Ubuntu up... Pidgin wasn't even running yet...
I guess that purple-remote was started by that new "logout menu"....

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/purple-remote
InterpreterPath: /usr/bin/python2.5
Package: libpurple-bin 1:2.5.1-0ubuntu3
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: python /usr/bin/purple-remote setstatus?status=offline
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LC_COLLATE=C
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
PythonArgs: ['/usr/bin/purple-remote', 'setstatus?status=offline']
SourcePackage: pidgin
Title: purple-remote crashed with DBusException in call_blocking()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse kqemu lpadmin plugdev vboxusers video

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.