nm-applet crashed with SIGSEGV

[Evgeniy Firsov]

nm-applet crashes everytime it tries to get a key from keyring...it tries to get password for "" from keyring {null)
It is start crash after update to 0.6.5,,,,,earlier it takes password from default keyring

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Jun 23 10:55:48 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/nm-applet
NonfreeKernelModules: nvidia cdrom
Package: network-manager-gnome 0.6.5-0ubuntu3
PackageArchitecture: i386
ProcCmdline: nm-applet --sm-disable
ProcCwd: /home/firs
ProcEnviron:
 LANGUAGE=ru_RU.UTF-8
 PATH=/home/firs/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: nm-applet crashed with SIGSEGV
Uname: Linux firs-laptop 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Sebastien Bacher (seb128)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Evgeniy Firsov (firs1978)]

On Thu, 28 Jun 2007 17:15:12 +0700, Sebastien Bacher <email address hidden>
wrote:

> Thanks for your bug report. Please try to obtain a backtrace
> http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
> bug report. This will greatly help us in tracking down your problem.
>
> ** Changed in: network-manager-applet (Ubuntu)
> Importance: Undecided => Medium
> Status: New => Incomplete
>

Hi, Sebastien!

After today update of network-manager-gnome it is not crashes any more.
But it is still tries to get network password from (null) keyring...do you
know how to appoint it to default keyring?

WBR, Evgeniy

[Alexander Sack (asac)]

apparently gnome-keyring upload fixed the crash.

[sriranga(79yrs) (withblessing-sriranga-1933)]

This is happened in ubuntu 13.10(daily build) - during when pressed the button "try ubuntu" and intend to install on hdd