mate-display-properties crashed with SIGSEGV in gdk_event_apply_filters()

Bug #1377376 reported by Eliah Kagan
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mate-control-center (Ubuntu)
New
Medium
Unassigned

Bug Description

On an Ubuntu MATE Utopic amd64 system in a VirtualBox VM with Guest Additions 4.3.16_95972 installed, mate-display-properties (provided by mate-control-center 1.8.2+dfsg1-1) crashed. I opened it up with System > Preferences > Monitors, the application window displayed momentarily, then disappeared. When I ran it again the same way, the crash did not occur.

Some updates were being installed at the time of the crash (I was running "sudo apt-get upgrade"), so perhaps that is related. mate-display-properties was not one of the packages being updated. I'm attaching possibly relevant information as term-veryshort.log (just some relevant text copied from the terminal) and the usual APT and dpkg-related log files.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: mate-control-center 1.8.2+dfsg1-1
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu3
Architecture: amd64
Date: Sat Oct 4 00:29:58 2014
Disassembly: => 0x4: Cannot access memory at address 0x4
ExecutablePath: /usr/bin/mate-display-properties
InstallationDate: Installed on 2014-10-02 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - beta2 amd64 (20140925)
ProcCmdline: mate-display-properties
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4: Cannot access memory at address 0x4
 PC (0x00000004) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: mate-control-center
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: mate-display-properties crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (mate-power-manager:4912): GLib-CRITICAL **: Source ID 90 was not found when attempting to remove it
 (mate-screensaver:4926): GLib-CRITICAL **: Source ID 23 was not found when attempting to remove it

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
information type: Private → Public
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 gdk_event_apply_filters (filters=0x300000000, event=<optimized out>, xevent=<optimized out>) at /build/buildd/gtk+2.0-2.24.24/gdk/x11/gdkevents-x11.c:356
 gdk_event_translate (display=0x1f8e020, event=0x2031600, xevent=0x7fff13073f70, return_exposes=return_exposes@entry=0) at /build/buildd/gtk+2.0-2.24.24/gdk/x11/gdkevents-x11.c:1052
 _gdk_events_queue (display=display@entry=0x1f8e020) at /build/buildd/gtk+2.0-2.24.24/gdk/x11/gdkevents-x11.c:2336
 gdk_event_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/gtk+2.0-2.24.24/gdk/x11/gdkevents-x11.c:2397

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 mate-control-center (Ubuntu):
importance: Undecided → Medium
summary: mate-display-properties crashed with SIGSEGV in
- g_main_context_dispatch()
+ gdk_event_apply_filters()
tags: removed: need-amd64-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.