Public bug reported:
Happened directly after bug 1750690
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: mate-applet-brisk-menu 0.5.0-5ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Feb 20 20:01:02 2018
Disassembly: => 0x7f0600000000: Cannot access memory at address 0x7f0600000000
ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
InstallationDate: Installed on 2018-02-20 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64
(20180220)
ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu//brisk-menu
SegvAnalysis:
Segfault happened at: 0x7f0600000000: Cannot access memory at address
0x7f0600000000
PC (0x7f0600000000) not located in a known VMA region (needed executable
region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: brisk-menu
StacktraceTop:
?? ()
?? ()
?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
g_cclosure_marshal_VOID__OBJECTv () from
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: brisk-menu crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf
** Affects: brisk-menu (Ubuntu)
Importance: Medium
Status: New
** Tags: amd64 apport-crash bionic
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750694
Title:
brisk-menu crashed with SIGSEGV in brisk_menu_window_filter_section()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1750694/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
