brisk-menu crashed with SIGSEGV in gtk_list_box_insert()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| brisk-menu (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
brisk menu crashed,immediate reload
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: mate-applet-
ProcVersionSign
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Apr 15 13:41:45 2018
Disassembly: => 0x181: Cannot access memory at address 0x181
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2018-04-14 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SegvAnalysis:
Segfault happened at: 0x181: Cannot access memory at address 0x181
PC (0x00000181) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: brisk-menu
StacktraceTop:
?? ()
?? ()
?? () from /usr/lib/
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 plugdev sambashare sudo
| mark arstall (mark-arstall) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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 #1763813, 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.