nm-applet crashes with assertion error in applet-device-gsm.c:769:gsm_get_secrets

[Pedric]

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-device-gsm.c:769:gsm_get_secrets: assertion failed: (info)
---
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-manager-applet (not installed)
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Tags: ubuntu-une maverick
Uname: Linux 2.6.35-25-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Mathieu Trudel-Lapierre (cyphermox)]

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.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_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'.

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.

[Pedric (pedric)]

Reopening because the crash cannot be reported by ubuntu-bug, the message is (translated from german):

The problem can not be reported

The application was terminated by an error assertion, but the message could not be loaded. Apport cannot process this crash.

(Das Problem kann nicht gemeldet werden:

Die Anwendung wurde aufgrund einer fehlerhaften Assertion beendet, doch die Meldung konnte nicht geladen werden. Apport kann diesen Absturz nicht verarbeiten.)

I'll attach the .crash if that is of any use.

[Mathieu Trudel-Lapierre (cyphermox)]

Without a crash that can be retraced there is little we can do.

Please make sure to downgrade back to the version provided in Maverick; you can do this by running the following command:

sudo apt-get install network-manager-gnome/maverick network-manager/maverick libnm-glib2/maverick libnm-util1/maverick

Then reset this bug to New if you can reproduce the crash with the official Maverick version of networkmanager and nm-applet; running 'apport-collect 721106' once you have done so if the crash still cannot be retraced.

[Pedric (pedric)]

apport information

[Pedric (pedric)]

apport information

[Pedric (pedric)]

apport information

[Pedric (pedric)]

apport information

[Pedric (pedric)]

apport information

[Pedric (pedric)]

apport information

[Pedric (pedric)]

apport information

[Pedric (pedric)]

apport information

[Pedric (pedric)]

apport information

[Pedric (pedric)]

apport information

[Pedric (pedric)]

apport information

[Pedric (pedric)]

The maverick version crashes as well, I did the apport-collect thing, I hope it will be of use to you. If the report indicates that nm-applet is running happily, it's because I had to use the workaround to get online to report the crash, as it is currently my only option to get online.

[Mathieu Trudel-Lapierre (cyphermox)]

What version of modemmanager do you have running?

[Pedric (pedric)]

0.4+git.20100809t153145.be28089-0ubuntu1 from maverick

[Mathieu Trudel-Lapierre (cyphermox)]

Might this actually happen because you have your device PIN-locked and set to "Connect automatically" ?

[Pedric (pedric)]

Yes, without auto connect, the applet no longer crashes, which is of course a better solution than the workaround. Nevertheless, auto-connect with PIN-locked devices is a valid configuration option (and one that the UI exposes), so I'd still consider this a bug.

[Mathieu Trudel-Lapierre (cyphermox)]

Yup, it's still an issue, but it's also unclear what the benefit is for using PINs if it's to have it saved on the system that uses the device.

Setting this back to confirmed.

[Pedric (pedric)]

SIM cards come PIN-locked by default over here, and there is no out-of-the box way of unlocking it without inserting it into a phone that is capable of doing so. NetworkManager does not store the PIN in the keyring, so there's a PIN prompt at every login. Actually, there are currently two PIN unlock dialogues, a small one, a larger, more descriptive one, and a small, plain one. Without auto-connect, I get the larger PIN unlock dialogue at login, and the smaller one if I try to unlock the device later on. Sometimes, it appears to me that both are created at once and one tries to close the other, but that does not impair functionality.

The idea of setting the connection of auto-connect was to enter the PIN and have NM connect automatically afterwards, now it's two more clicks.

[Mathieu Trudel-Lapierre (cyphermox)]

I think we got enough information to fix this.. With some luck I can put time to look into the issue for it to be resolved for Natty.