brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset()

Bug #1762771 reported by Marcio Santos
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brisk-menu (Ubuntu)
New
Undecided
Unassigned

Bug Description

constantes reinícios .

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: mate-applet-brisk-menu 0.5.0-7ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Apr 10 12:55:42 2018
ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
InstallationDate: Installed on 2018-04-10 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
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:
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fcdac8b3f7e <g_slice_free_chain_with_offset+190>: mov (%r14,%rax,1),%rbp
 PC (0x7fcdac8b3f7e) ok
 source "(%r14,%rax,1)" (0x3fd333333333333b) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown 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
Marcio Santos (marcio-18santos) 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.