Ubuntu
brisk-menu package

brisk-menu crashed with SIGSEGV in brisk_menu_window_filter_section()

Bug #1750694 reported by BertN45 on 2018-02-21

This bug report is a duplicate of: Bug #1724115: brisk-menu crashed while looking at items while a app was currently being installed. Edit Remove

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	brisk-menu (Ubuntu)	New	Medium	Unassigned

Bug Description

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

Tags:

Revision history for this message

BertN45 (lammert-nijhof) wrote on 2018-02-21:

#1

Dependencies.txt Edit (9.5 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (2.7 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (872 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (305 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (64.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Registers.txt Edit (909 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (9.4 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (689 bytes, text/plain; charset="utf-8")

information type:

Private → Public

Revision history for this message

Apport retracing service (apport) wrote on 2018-02-21:

#2

StacktraceTop:
?? ()
brisk_menu_window_filter_section (item=<optimized out>, self=0x5555907762f0) at ../src/frontend/menu-search.c:74
brisk_menu_window_filter_apps (self=0x5555907762f0, child=0x55559093f770) at ../src/frontend/menu-search.c:150
gtk_flow_box_apply_filter (box=<optimized out>, child=0x55559093a140) at ../../../../gtk/gtkflowbox.c:925
g_cclosure_marshal_VOID__OBJECTv (closure=0x55559057e210, return_value=<optimized out>, instance=<optimized out>, args=<optimized out>, marshal_data=<optimized out>, n_params=<optimized out>, param_types=0x5555904cf390) at ../../../../gobject/gmarshal.c:2102

Revision history for this message

Apport retracing service (apport) wrote on 2018-02-21: Stacktrace.txt

#3

Stacktrace.txt Edit (10.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2018-02-21: StacktraceSource.txt

#4

StacktraceSource.txt Edit (9.7 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2018-02-21: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (19.6 KiB, text/plain)

Changed in brisk-menu (Ubuntu):
importance:	Undecided → Medium
summary:	- brisk-menu crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv() + brisk-menu crashed with SIGSEGV in brisk_menu_window_filter_section()
tags:	removed: need-amd64-retrace

Report a bug

This report contains Public information

Everyone can see this information.

Duplicate of bug #1724115 Remove

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.