xfwm4 crashed with SIGSEGV in g_main_context_dispatch()

Bug #1277974 reported by Vav Vavrek
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xfwm4 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

well, this may be unhelpful, but this crash is of the file manager on Xubuntu 14.04 LTS its my fault for improperly ejecting an ipad {removal without eject, and then trying to eject the still "mounted" drive cause the file manager to lock and crash}

thanx -v

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xfwm4 4.11.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Feb 8 14:27:36 2014
ExecutablePath: /usr/bin/xfwm4
ProcCmdline: xfwm4 --replace --display :0.0 --sm-client-id 28a6ed1f3-fffa-4ce0-8d3f-d4d364ebd6fc
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ffa06fffa56 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1
 PC (0x7ffa06fffa56) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfwm4
StacktraceTop:
 ?? ()
 ?? ()
 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
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: xfwm4 crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Vav Vavrek (cvavrun) 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 #1233107, 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-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xfwm4 (Ubuntu):
status: New → Confirmed
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.