It crashed when I hit Apply button after tweaking tooltip foreground/background colours in gnome-color-chooser.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: xfwm4 4.11.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-30.40-lowlatency 3.16.7-ckt3
Uname: Linux 3.16.0-30-lowlatency x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Feb 1 11:02:14 2015
ExecutablePath: /usr/bin/xfwm4
InstallationDate: Installed on 2011-11-13 (1175 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/bin/xfwm4 --display :0.0 --sm-client-id 280cf5785-b8ae-4afb-ac48-a591eba41baf
SegvAnalysis:
Segfault happened at: 0x7f620cb26cb9 <client_event_cb+73>: movl $0x1,0x1c(%rdx)
PC (0x7f620cb26cb9) ok
source "$0x1" ok
destination "0x1c(%rdx)" (0x0000001c) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: xfwm4
StacktraceTop:
set_reload (data=0x0, ev=0x7f620df248b0, obj=<optimized out>) at events.c:2683
client_event_cb (widget=0x7f620ddf60c0, ev=0x7f620df248b0, data=<optimized out>) at events.c:2755
?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
g_closure_invoke (closure=0x7f620de9e9f0, return_value=0x7fffe0f703f0, n_param_values=2, param_values=0x7fffe0f704a0, invocation_hint=0x7fffe0f70440) at /build/buildd/glib2.0-2.42.1/./gobject/gclosure.c:768
signal_emit_unlocked_R (node=node@entry=0x7f620ddd1350, detail=detail@entry=0, instance=instance@entry=0x7f620ddf60c0, emission_return=emission_return@entry=0x7fffe0f70550, instance_and_params=instance_and_params@entry=0x7fffe0f704a0) at /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c:3553
Title: xfwm4 crashed with SIGSEGV in set_reload()
UpgradeStatus: Upgraded to utopic on 2014-10-25 (99 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lp lpadmin mythtv netdev plugdev sambashare scanner tape vboxusers video wireshark
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 #1054276, 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.