Ubuntu
apport package

wifiradar doesn't start

Bug #458842 reported by freddy on 2009-10-23

This bug report is a duplicate of: Bug #424965: apport-gtk crashed with KeyError in __getitem__(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	apport (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: apport

wifiradar doesnt start

ProblemType: Crash
Architecture: i386
CrashReports:
600:0:0:30121:2009-10-23 09:33:59.000000000 +0200:2009-10-23 09:34:09.000000000 +0200:/var/crash/_usr_share_apport_apport-gtk.0.crash
600:1000:1000:30984:2009-10-23 09:12:04.000000000 +0200:2009-10-23 09:25:35.000000000 +0200:/var/crash/_usr_bin_desktop-effects-kde4.1000.crash
600:0:0:22217:2009-10-23 09:32:53.000000000 +0200:2009-10-23 09:33:51.000000000 +0200:/var/crash/_usr_sbin_wifi-radar.0.crash
Date: Fri Oct 23 09:34:00 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.6
Package: apport-gtk 1.9.3-0ubuntu3
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
PATH=(custom, no user)
LANG=nl_BE.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/share/apport/apport-gtk']
SourcePackage: apport
Title: apport-gtk crashed with KeyError in __getitem__()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

Tags:

Revision history for this message

freddy (dekinderfreddy) wrote on 2009-10-23:

ApportLog.txt Edit (557 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (1.1 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (704 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-10-24: 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 #424965, 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.