Ubuntu
seahorse package

seahorse crashed with SIGSEGV in on_source_export_ready()

Bug #855940 reported by Rocksinboxes
44
This bug affects 6 people
Affects Status Importance Assigned to Milestone
seahorse (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I was attempting to import keys from keyserver.ubuntu.com

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: seahorse 3.1.92-0ubuntu1 [modified: usr/bin/seahorse usr/lib/seahorse/seahorse-ssh-askpass]
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: fglrx wl
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Wed Sep 21 14:36:53 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/seahorse
ProcCmdline: seahorse
SegvAnalysis:
 Segfault happened at: 0x43bcb9: mov (%rbx),%rdi
 PC (0x0043bcb9) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: seahorse
StacktraceTop:
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: seahorse crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Rocksinboxes (rocksinboxes) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 on_source_export_ready (object=<optimized out>, result=0x115c8c0, user_data=0x1058ea0) at seahorse-transfer.c:91
 g_simple_async_result_complete (simple=0x115c8c0) at /build/buildd/glib2.0-2.29.92/./gio/gsimpleasyncresult.c:749
 complete_in_idle_cb (data=0x115c8c0) at /build/buildd/glib2.0-2.29.92/./gio/gsimpleasyncresult.c:761
 g_main_dispatch (context=0xc2db60) at /build/buildd/glib2.0-2.29.92/./glib/gmain.c:2441
 g_main_context_dispatch (context=0xc2db60) at /build/buildd/glib2.0-2.29.92/./glib/gmain.c:3011

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in seahorse (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: seahorse crashed with SIGSEGV in g_simple_async_result_complete()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in seahorse (Ubuntu):
status: New → Confirmed
Revision history for this message
Andreas Moog (ampelbein) wrote : Steps to reproduce?

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

 status incomplete
 subscribe

visibility: private → public
Changed in seahorse (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jonas Schwabe (jonas-schwabe) wrote : Re: seahorse crashed with SIGSEGV in g_simple_async_result_complete()

I can reproduce this by starting the keyserver sync while having network connection issues (e.g. no working DNS or general connection issues). When an error message appears telling there are network problems dismiss it and cancel the sync process.

Try selecting multiple keys to sync as dismissing the error messages for one key will also close the sync window normally.

Revision history for this message
Karma Dorje (taaroa) wrote :

i can reproduce it too. see #954742.

steps to reproduce:

1 seahorse → remote → sync and publish keys…
2 If keyserver is unavailable (Couldn't communicate with server 'keyserver.ubuntu.com:11371': Cannot connect to destination (keyserver.ubuntu.com))→ crashed and closed.

Sebastien Bacher (seb128)
Changed in seahorse (Ubuntu):
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in seahorse (Ubuntu):
status: New → Confirmed
Sebastien Bacher (seb128)
summary: - seahorse crashed with SIGSEGV in g_simple_async_result_complete()
+ seahorse crashed with SIGSEGV in on_source_export_ready()
Ubuntu Foundations Team Bug Bot (crichton)
tags: added: precise
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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