nm-applet crashes with assertion error in applet-device-gsm.c:769:gsm_get_secrets
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
This happens to both the nm-applet from Maverick and from the PPA on launch of nm-applet. Output from lsusb:
$ lsusb | grep "Mobile Broadband"
Bus 002 Device 002: ID 0bdb:1900 Ericsson Business Mobile Networks BV F3507g Mobile Broadband Module
A workaround is to stop NetworkManager, re-run nm-applet and start NetworkManager again.
Oh and of course, the full error message (with version 0.8.1.998 from PPA, will see later if the line number changed from the Maverick version)
ERROR:applet-
---
Architecture: amd64
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
DistroRelease: Ubuntu 10.10
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
IpRoute:
10.146.226.176/29 dev wwan0 proto kernel scope link src 10.146.226.179 metric 3
169.254.0.0/16 dev wwan0 scope link metric 1000
default via 10.146.226.178 dev wwan0 proto static
Keyfiles: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Package: network-
ProcEnviron:
LANG=de_DE.utf8
SHELL=/bin/bash
ProcVersionSign
Tags: ubuntu-une maverick
Uname: Linux 2.6.35-25-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
description: | updated |
description: | updated |
description: | updated |
Changed in network-manager-applet (Ubuntu): | |
status: | Invalid → New |
Changed in network-manager-applet (Ubuntu): | |
status: | Incomplete → New |
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. 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.
Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. _my_crash_ report. crash' where _my_crash_ report. crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/ _my_crash_ report. crash'.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/
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.