brisk-menu crashed with SIGSEGV in g_type_check_instance_cast()

Bug #1709501 reported by james rayl
82
This bug affects 12 people
Affects Status Importance Assigned to Milestone
brisk-menu (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

17.10 alpha 2 menu crash

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: mate-applet-brisk-menu 0.4.5-1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Aug 8 16:53:08 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
InstallationDate: Installed on 2017-08-07 (1 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f2dc507a196 <g_type_check_instance_cast+38>: mov (%r9),%rbp
 PC (0x7f2dc507a196) ok
 source "(%r9)" (0x613b6574616c706d) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: brisk-menu
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: brisk-menu crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
james rayl (ouj51) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=type_instance@entry=0x55a1bd13ea60, iface_type=94153151557488) at ../../../../gobject/gtype.c:4057
 brisk_apps_backend_reload (self=0x55a1bd13ea60, self@entry=<error reading variable: value has been optimized out>) at src/backend/apps/apps-backend.c:245
 g_timeout_dispatch (source=0x55a1bd4c1f00, callback=<optimized out>, user_data=<optimized out>) at ../../../../glib/gmain.c:4629
 g_main_dispatch (context=0x55a1bceedf20) at ../../../../glib/gmain.c:3148
 g_main_context_dispatch (context=context@entry=0x55a1bceedf20) at ../../../../glib/gmain.c:3813

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in brisk-menu (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in brisk-menu (Ubuntu):
status: New → Confirmed
tags: added: bionic
information type: Private → Public
Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :

This was fixed via brisk-menu 0.5.0-1 in Bionic.

Changed in brisk-menu (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Mike Glover (mikeglover) wrote :

Had this bug when playing around changing colours and desktop layouts on a fresh install daily image 2020-04-13 which should have this fix but I experienced the bug.

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.