sushi-start crashed with SIGSEGV in std::_Rb_tree_rebalance_for_erase()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-sushi (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
https:/
---
Sushi crashed when first summed on a text file. It did show the preview, though. And it didn't crashed after that.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-sushi 3.24.0-1
ProcVersionSign
Uname: Linux 4.11.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Aug 11 12:42:33 2017
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-07-27 (15 days ago)
InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7fb5057f7ea9 <_ZSt28_
PC (0x7fb5057f7ea9) ok
source "(%r9)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%r10d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-sushi
StacktraceTop:
std::_
std::_
() at /usr/lib/
() at /usr/lib/
g_object_unref () at /usr/lib/
Title: sushi-start crashed with SIGSEGV in std::_Rb_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
information type: | Private → Public |
Changed in gnome-sushi (Ubuntu): | |
status: | Confirmed → Fix Committed |
status: | Fix Committed → Incomplete |
Status changed to 'Confirmed' because the bug affects multiple users.