seahorse assert failure: ERROR:seahorse-object.c:419:seahorse_object_dispose: assertion failed: (self->pv->children == NULL)

[Matt Lavin]

Binary package hint: seahorse

I was trying to delete a large collection of entries from the 'default' keyring. I clicked 'Allow Always' when asked for access to the keyring, but in the end it told me that the access was denied and then it crashed.

ProblemType: Crash
Architecture: i386
AssertionMessage: ERROR:seahorse-object.c:419:seahorse_object_dispose: assertion failed: (self->pv->children == NULL)
CrashCounter: 1
Date: Wed Sep 23 16:04:37 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/seahorse
NonfreeKernelModules: nvidia
Package: seahorse 2.28.0-0ubuntu1
ProcCmdline: seahorse
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
Signal: 6
SourcePackage: seahorse
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 g_assertion_message () from /usr/lib/libglib-2.0.so.0
 g_assertion_message_expr () from /usr/lib/libglib-2.0.so.0
Title: seahorse assert failure: ERROR:seahorse-object.c:419:seahorse_object_dispose: assertion failed: (self->pv->children == NULL)
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom crontab dialout lpadmin plugdev sambashare

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance.

[Pedro Villavicencio (pedro)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.