gnome-shell crashed with SIGSEGV in meta_plugin_manager_xevent_filter()

Bug #1695168 reported by Arma1975
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Expired
Medium
Unassigned

Bug Description

~$ apt-cache policy pkgname
N: Unable to locate package pkgname

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic i686
ApportVersion: 2.20.5-0ubuntu4
Architecture: i386
CrashCounter: 1
CurrentDesktop: GNOME-Classic:GNOME
Date: Thu Jun 1 23:02:45 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0xb71bc317 <meta_plugin_manager_xevent_filter+23>: pushl 0x4(%eax)
 PC (0xb71bc317) ok
 source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "(%esp)" (0xbfe727a4) ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 meta_plugin_manager_xevent_filter () at /usr/lib/i386-linux-gnu/libmutter-0.so.0
 () at /usr/lib/i386-linux-gnu/libmutter-0.so.0
 g_main_context_dispatch () at /lib/i386-linux-gnu/libglib-2.0.so.0
 () at /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () at /lib/i386-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in meta_plugin_manager_xevent_filter()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

Revision history for this message
Arma1975 (arma1975) wrote :
Revision history for this message
Arma1975 (arma1975) wrote :

a

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

StacktraceTop:
 meta_plugin_manager_xevent_filter (plugin_mgr=0x0, xev=0xbfe727fc) at compositor/meta-plugin-manager.c:289
 handle_host_xevent (event=0xbfe727fc, backend=0x80e750a0) at backends/x11/meta-backend-x11.c:257
 x_event_source_dispatch (source=0x80e773a8, callback=0x0, user_data=0x0) at backends/x11/meta-backend-x11.c:345
 g_main_dispatch (context=0x80e72530) at ../../../../glib/gmain.c:3234
 g_main_context_dispatch (context=0x80e72530) at ../../../../glib/gmain.c:3899

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 gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
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.