seahorse crashed with SIGSEGV in g_variant_unref()

Bug #1796554 reported by Stephen Campbell
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
seahorse (Ubuntu)
Expired
Medium
Unassigned

Bug Description

crash after pw changed

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: seahorse 3.30-1
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 7 11:43:55 2018
ExecutablePath: /usr/bin/seahorse
InstallationDate: Installed on 2018-10-04 (2 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
ProcCmdline: /usr/bin/seahorse --gapplication-service
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f27b08238c5 <g_variant_unref+5>: mov 0x24(%rdi),%eax
 PC (0x7f27b08238c5) ok
 source "0x24(%rdi)" (0xffffffff983a3ef4) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: seahorse
StacktraceTop:
 g_variant_unref () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libsecret-1.so.0
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: seahorse crashed with SIGSEGV in g_variant_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Stephen Campbell (campbell-sh) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_variant_unref (value=0xffffffff983a3ed0) at ../../../../glib/gvariant-core.c:625
 ___lambda21_ (_data3_=0x55a163ac5aa0, _data3_=0x55a163ac5aa0, obj=<optimized out>, res=<optimized out>) at gkr/gkr@@seahorse-gkr@sta/gkr-keyring.c:1073
 ____lambda21__gasync_ready_callback (source_object=<optimized out>, res=<optimized out>, self=0x55a163ac5aa0) at gkr/gkr@@seahorse-gkr@sta/gkr-keyring.c:1115
 g_simple_async_result_complete (simple=0x55a163de1170) at ../../../../gio/gsimpleasyncresult.c:802
 on_real_prompt_completed (source=0x55a163afde20, result=0x55a163de11e0, user_data=<optimized out>) at libsecret/secret-service.c:322

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.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
Seth Arnold (seth-arnold) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :

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.

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

[Expired for seahorse (Ubuntu) because there has been no activity for 60 days.]

Changed in seahorse (Ubuntu):
status: Incomplete → Expired
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.