apport-gtk crashed with AssertionError in return_value()

[sebbisubbu]

Binary package hint: apport

I have a problem with the router password.. Reset is not working. Someone is sniffing and controlling my connection and I WANT TO MANAGE my information..how can I solve the problem? NO CLOUDS ON MY HEAD...
WHAT ABOUT PLC?

Send private solution to> <email address hidden>

BEST REGARDS

ProblemType: Crash
ApportLog:
 apport (pid 3993) Tue May 25 21:07:10 2010: called for pid 1847, signal 11
 apport (pid 3993) Tue May 25 21:07:10 2010: executable: /usr/sbin/NetworkManager (command line "NetworkManager")
 apport (pid 3993) Tue May 25 21:07:10 2010: wrote report /var/crash/_usr_sbin_NetworkManager.0.crash
Architecture: i386
CrashReports:
 600:0:0:29426:2010-05-25 21:07:39.489177000 +0000:2010-05-25 21:07:40.489177000 +0000:/var/crash/_usr_share_apport_apport-gtk.0.crash
 600:0:0:472410:2010-05-25 21:07:34.905200000 +0000:2010-05-25 21:07:35.905200000 +0000:/var/crash/_usr_sbin_NetworkManager.0.crash
Date: Tue May 25 21:07:40 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.6
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: apport-gtk 1.9.3-0ubuntu4
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.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 AssertionError in return_value()
Uname: Linux 2.6.31-14-generic i686
UserGroups:

[Apport retracing service (apport)]

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 #469943, 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.