seahorse crashed with SIGSEGV in seahorse_place_get_label()

Bug #2015697 reported by David Blankenship
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
seahorse (Ubuntu)
New
Medium
Unassigned

Bug Description

NA

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: seahorse 43.0-1build1
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 9 14:09:25 2023
ExecutablePath: /usr/bin/seahorse
InstallationDate: Installed on 2023-04-07 (2 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
ProcCmdline: /usr/bin/seahorse --gapplication-service
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x55e23ee570cd <seahorse_place_get_label+29>: mov 0x20(%rax),%rax
 PC (0x55e23ee570cd) ok
 source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: seahorse
StacktraceTop:
 seahorse_place_get_label ()
 ?? ()
 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: seahorse crashed with SIGSEGV in seahorse_place_get_label()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

Revision history for this message
David Blankenship (dtblank) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 seahorse_place_get_label (self=0x55e23f1d70c0) at common/libcommon.a.p/place.c:117
 seahorse_key_manager_on_sidebar_selected_rows_changed (sidebar=<optimized out>, self=0x55e23f4e9780) at src/seahorse.p/key-manager.c:1879
 _seahorse_key_manager_on_sidebar_selected_rows_changed_gtk_list_box_selected_rows_changed (_sender=<optimized out>, self=0x55e23f4e9780) at src/seahorse.p/key-manager.c:1630
 g_closure_invoke (closure=0x55e23f38eb90, return_value=0x0, n_param_values=1, param_values=0x7fffe1d42a10, invocation_hint=0x7fffe1d42990) at ../../../gobject/gclosure.c:832
 signal_emit_unlocked_R.isra.0 (node=node@entry=0x55e23f3621d0, detail=detail@entry=0, instance=instance@entry=0x55e23f38a190, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffe1d42a10) at ../../../gobject/gsignal.c:3802

tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 seahorse_place_get_label (self=0x55e23f1d70c0) at common/libcommon.a.p/place.c:117
 seahorse_key_manager_on_sidebar_selected_rows_changed (sidebar=<optimized out>, self=0x55e23f4e9780) at src/seahorse.p/key-manager.c:1879
 _seahorse_key_manager_on_sidebar_selected_rows_changed_gtk_list_box_selected_rows_changed (_sender=<optimized out>, self=0x55e23f4e9780) at src/seahorse.p/key-manager.c:1630
 g_closure_invoke (closure=0x55e23f38eb90, return_value=0x0, n_param_values=1, param_values=0x7fffe1d42a10, invocation_hint=0x7fffe1d42990) at ../../../gobject/gclosure.c:832
 signal_emit_unlocked_R.isra.0 (node=<optimized out>, detail=0, instance=0x55e23f38a190, emission_return=0x0, instance_and_params=0x7fffe1d42a10) at ../../../gobject/gsignal.c:3818

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
Revision history for this message
Steve Beattie (sbeattie) 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
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.