YAMA crashed with DBusException in call_blocking()

[LCID Fire]

Crashed in backgroud

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: awn-applets-python-extras 0.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Tue Apr 13 18:20:52 2010
ExecutablePath: /usr/share/avant-window-navigator/applets/yama/yama.py
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: python /usr/share/avant-window-navigator/applets/yama/yama.py --uid=1269339798 --window=35651625 --panel-id=1
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/share/avant-window-navigator/applets/yama/yama.py', '--uid=1269339798', '--window=35651625', '--panel-id=1']
SourcePackage: awn-extras-applets
Title: yama.py crashed with DBusException in call_blocking()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare scanner video

Traceback (most recent call last):
  File "/usr/share/avant-window-navigator/applets/yama/yama.py", line 247, in theme_changed_cb
    self.build_menu()
  File "/usr/share/avant-window-navigator/applets/yama/yama.py", line 136, in build_menu
    self.append_session_actions(self.menu)
  File "/usr/share/avant-window-navigator/applets/yama/yama.py", line 144, in append_session_actions
    dbus_services = self.session_bus.list_names()
  File "/usr/lib/pymodules/python2.6/dbus/bus.py", line 333, in list_names
    '', (), utf8_strings=True)
  File "/usr/lib/pymodules/python2.6/dbus/connection.py", line 620, in call_blocking
    message, timeout)
DBusException: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received

[Julien Lavergne (gilir)]

Thanks for your bug report. Forwarded upstream.

[onox (onox)]

When did this bug occur? When the applet was being loaded?

[onox (onox)]

Can you still reproduce this?

[onox (onox)]

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!

[Julien Lavergne (gilir)]

Following upstream, I'm closing the bug report.