brisk-menu crashed with SIGSEGV: executing writable VMA [heap]

Bug #1869891 reported by Nathanael C. Higley
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
brisk-menu (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I right clicked on the brisk menu and selected 'Edit Menus' then I moved my mouse to 'System Tools' and selected it and then scrolled down to find 'Virtualbox' which Wasn't showing up in the menu, so I checked to verify it was checked and it was, so I closed out the 'Edit Menus' and then clicked the brisk 'Menu' scrolled down to 'System Tools' and scrolled down to where Virtualbox was then boom, the 'brisk menu' crashed on me.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: mate-applet-brisk-menu 0.6.0-1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Mar 31 08:46:27 2020
ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
InstallationDate: Installed on 2020-03-28 (2 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200328)
ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu//brisk-menu
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x5592f8941f10: add %al,(%rax)
 PC (0x5592f8941f10) in non-executable VMA region: 0x5592f82f9000-0x5592f8c35000 rw-p [heap]
 source "%al" ok
 destination "(%rax)" (0x5592f8941f10) ok
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: brisk-menu
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: brisk-menu crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Nathanael C. Higley (higleync2018) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 brisk_menu_window_sort (self=self@entry=0x5592f86ee290, itemA=0x5592f88ff0a0, itemB=0x5592f89d9830) at ../src/frontend/menu-sort.c:66
 brisk_classic_window_sort (row1=<optimized out>, row2=0x5592f8941c10, v=<optimized out>) at ../src/frontend/classic/classic-window.c:812
 node_find_closest () from /tmp/apport_sandbox_v8m79ws3/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 node_insert_sorted () from /tmp/apport_sandbox_v8m79ws3/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1

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 brisk-menu (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: brisk-menu crashed with SIGSEGV

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in brisk-menu (Ubuntu):
status: New → Confirmed
summary: - brisk-menu crashed with SIGSEGV
+ brisk-menu crashed with SIGSEGV: executing writable VMA [heap]
Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :

Fixed via brisk-menu (0.6.0-1ubuntu1)

Changed in brisk-menu (Ubuntu):
status: Confirmed → Fix Released
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.