Ubuntu
awn-extras-applets package

battery-applet.py crashed with DBusException in call_blocking()

Bug #468783 reported by rezap on 2009-11-01

This bug report is a duplicate of: Bug #325925: battery-applet.py crashed with DBusException in call_blocking(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	awn-extras-applets (Ubuntu)	New	Undecided	Unassigned

Bug Description

idk what to put here

ProblemType: Crash
Architecture: i386
Date: Sat Oct 31 18:06:29 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/avant-window-navigator/applets/battery-applet/battery-applet.py
InterpreterPath: /usr/bin/python2.6
Package: awn-applets-python-core 0.3.2.2-2ubuntu1
PackageArchitecture: all
ProcCmdline: python /usr/share/avant-window-navigator/applets/battery-applet/battery-applet.py --uid=1255934899 --window=48234549 --orient=0 --height=29
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/share/avant-window-navigator/applets/battery-applet/battery-applet.py', '--uid=1255934899', '--window=48234549', '--orient=0', '--height=29']
SourcePackage: awn-extras-applets
Title: battery-applet.py crashed with DBusException in call_blocking()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev root sambashare scanner tape video

Tags:

Revision history for this message

rezap (rezapiri) wrote on 2009-11-01:

Traceback.txt Edit (772 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (731 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-06: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #325925, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.