Ubuntu
brisk-menu package

  1. Bug #1714598
  2. Comment #0

Comment 0 for bug 1714598

Revision history for this message
Paul Tansom (aptanet) wrote : brisk-menu crashed with SIGSEGV in gtk_list_box_insert()

Just upgraded from 17.04 to the 17.10 beta and was adding some apps tot the Mutiny bar. The app icons disappeared up behind the Brisk menu and the menu crashed.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: mate-applet-brisk-menu 0.4.5-1
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Sep 1 22:22:18 2017
Disassembly: => 0x1: Cannot access memory at address 0x1
ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
InstallationDate: Installed on 2017-06-16 (76 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x1: Cannot access memory at address 0x1
 PC (0x00000001) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: brisk-menu
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_list_box_insert () 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
Title: brisk-menu crashed with SIGSEGV in gtk_list_box_insert()
UpgradeStatus: Upgraded to artful on 2017-09-01 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo