brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset()

Bug #1726281 reported by claudiononi@gmail.com
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brisk-menu (Ubuntu)
New
Undecided
Unassigned

Bug Description

sou leigo no sistema

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: mate-applet-brisk-menu 0.4.5-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Oct 23 05:23:38 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f676041a9df <g_slice_free_chain_with_offset+191>: mov (%rbx,%rax,1),%r12
 PC (0x7f676041a9df) ok
 source "(%rbx,%rax,1)" (0x0000000a) not located in a known VMA region (needed readable region)!
 destination "%r12" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: brisk-menu
StacktraceTop:
 g_slice_free_chain_with_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
claudiononi@gmail.com (claudiononi) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724262, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
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.