xfwm4 crashed with SIGSEGV in g_main_context_dispatch()

Bug #1293551 reported by Sergio Benjamim
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xfwm4 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Trying to test wxvbam from git: https://github.com/sergiobenrocha2/vbam/tree/bug-fixes

When you closes vbam window in the close button (x), sometimes the system crashes.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xfwm4 4.11.1-2ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Mar 17 13:26:16 2014
ExecutablePath: /usr/bin/xfwm4
InstallationDate: Installed on 2014-01-09 (66 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140109)
ProcCmdline: xfwm4 --replace
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f28fd438e46 <__strcmp_ssse3+22>: movlpd (%rdi),%xmm1
 PC (0x7f28fd438e46) 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 dialout dip lpadmin plugdev sambashare sudo

Revision history for this message
Sergio Benjamim (sergio-br2) 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
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.