brisk-menu crashed with SIGSEGV in gtk_list_box_insert()

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

Bug Description

Menu crashed when browsing items. I'm in the live session.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: mate-applet-brisk-menu 0.6.0-1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CasperVersion: 1.442
CurrentDesktop: MATE
Date: Mon Apr 6 16:00:02 2020
Disassembly: => 0x201: Cannot access memory at address 0x201
ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu//brisk-menu
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANG=C.UTF-8
SegvAnalysis:
 Segfault happened at: 0x201: Cannot access memory at address 0x201
 PC (0x00000201) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: brisk-menu
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_list_box_insert () from /lib/x86_64-linux-gnu/libgtk-3.so.0
 g_cclosure_marshal_VOID__OBJECTv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: brisk-menu crashed with SIGSEGV in gtk_list_box_insert()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Tabasc0 (tabasco) 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 #1724115, 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.