Ubuntu
kismet package

Kismet spontaneouly shut down on Toshiba Tecra M2V

Bug #88723 reported by Agent014
4
Affects Status Importance Assigned to Milestone
kismet (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kismet

Running Kismet normally on an Intel Pro/wireless 2200BG card. Source line is as follows in kismet.conf:

source=ipw2200,eth1,2200BG

ProblemType: Crash
Architecture: i386
Date: Wed Feb 28 09:53:13 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/kismet_client
Package: kismet 2006.04.R1-1.1
ProcCmdline: //usr/bin/kismet_client
ProcCwd: /home/agent014
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kismet
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Uname: Linux Bauer3 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
UserGroups:

Revision history for this message
Agent014 (pbauer007) wrote :
Revision history for this message
Martin Pitt (pitti) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Martin Pitt (pitti) wrote : Symbolic threaded stack trace
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file.

If this is still an issue, please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in kismet:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.