sushi-start crashed with SIGSEGV in gtk_menu_popup_for_device()

Bug #1507182 reported by Валерий
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-sushi (Ubuntu)
New
Undecided
Unassigned

Bug Description

sushi-start crashed with SIGSEGV in gtk_menu_popup_for_device()

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: gnome-sushi 3.16.0-1build1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu2
Architecture: i386
CurrentDesktop: Unity
Date: Sat Oct 17 21:46:15 2015
ExecutablePath: /usr/lib/gnome-sushi/sushi-start
InstallationDate: Installed on 2015-10-15 (2 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha i386 (20150924)
ProcCmdline: /usr/lib/gnome-sushi/sushi-start
SegvAnalysis:
 Segfault happened at: 0xb67dcd6a <gtk_menu_popup_for_device+106>: mov 0x18(%edi),%eax
 PC (0xb67dcd6a) ok
 source "0x18(%edi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-sushi
StacktraceTop:
 gtk_menu_popup_for_device () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: sushi-start crashed with SIGSEGV in gtk_menu_popup_for_device()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Валерий (com-bvv) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1010375, 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.

information type: Private → Public
tags: removed: need-i386-retrace
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.