brisk-menu crashed with SIGSEGV in gtk_list_box_insert()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
brisk-menu (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
stop and brick
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: mate-applet-
ProcVersionSign
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Apr 2 00:04:59 2020
Disassembly: => 0x557700000009: Cannot access memory at address 0x557700000009
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2020-04-02 (0 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
ProcCmdline: /usr/lib/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=en_US
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x557700000009: Cannot access memory at address 0x557700000009
PC (0x557700000009) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: brisk-menu
StacktraceTop:
?? ()
?? ()
?? () from /lib/x86_
gtk_list_
g_cclosure_
Title: brisk-menu crashed with SIGSEGV in gtk_list_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
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 #1869601, 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.