seahorse-agent crashed with SIGSEGV in g_closure_invoke()

Bug #784787 reported by Moritz Naumann
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
seahorse-plugins (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: seahorse-plugins

I right-clicked, then immediately left-clicked on the seahorse icon in the notification-area on this gnome-legacy desktop to trigger the crash.
This is likely a duplicate of #782392

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: seahorse-plugins 2.30.1-3ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed May 18 20:28:38 2011
ExecutablePath: /usr/bin/seahorse-agent
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/bin/seahorse-agent --execute gnome-session -- --session=2d-gnome
ProcEnviron:
 LANGUAGE=de_DE:en
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x40ce9e: mov 0x20(%r12),%rdi
 PC (0x0040ce9e) ok
 source "0x20(%r12)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: seahorse-plugins
StacktraceTop:
 ?? ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: seahorse-agent crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to natty on 2011-04-09 (39 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Moritz Naumann (mnaumann) wrote :
visibility: private → public
description: updated
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.