xfwm4 crashed with SIGSEGV in XUnmapWindow()

Bug #1157311 reported by Kamil
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Xfwm4
New
Undecided
Unassigned
xfwm4 (Fedora)
Won't Fix
Undecided
xfwm4 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

When I come back from CS Source full screen to screen of Xubuntu by typing tab+alt, the apport said that xfwm4 crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xfwm4 4.10.0-4ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
Uname: Linux 3.8.0-13-generic i686
ApportVersion: 2.9.2-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Tue Mar 19 18:00:17 2013
ExecutablePath: /usr/bin/xfwm4
InstallationDate: Installed on 2013-03-15 (3 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130315)
MarkForUpload: True
ProcCmdline: xfwm4 --replace
ProcCwd: /home/lukasz
ProcEnviron:
 LANGUAGE=pl:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6ee2b94 <XUnmapWindow+20>: mov 0x4d0(%esi),%eax
 PC (0xb6ee2b94) ok
 source "0x4d0(%esi)" (0x000004d0) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfwm4
StacktraceTop:
 XUnmapWindow (dpy=0x0, w=w@entry=10497032) at ../../src/UnmapWin.c:39
 wireframeUpdate (c=c@entry=0xb8945fa0, xwindow=10497032) at wireframe.c:56
 clientCycleEventFilter (xevent=0xbfdb8cfc, data=0xbfdb8f28) at cycle.c:337
 eventXfwmFilter (gdk_xevent=0xbfdb8cfc, event=0xb88c4ed8, data=0xb892a098) at event_filter.c:158
 gdk_event_apply_filters (filters=<optimized out>, event=<optimized out>, xevent=<optimized out>) at /build/buildd/gtk+2.0-2.24.16/gdk/x11/gdkevents-x11.c:356
Title: xfwm4 crashed with SIGSEGV in XUnmapWindow()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Kamil (lampshade-t) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XUnmapWindow (dpy=0x0, w=w@entry=10497032) at ../../src/UnmapWin.c:39
 wireframeUpdate (c=c@entry=0xb8945fa0, xwindow=10497032) at wireframe.c:56
 clientCycleEventFilter (xevent=0xbfdb8cfc, data=0xbfdb8f28) at cycle.c:337
 eventXfwmFilter (gdk_xevent=0xbfdb8cfc, event=0xb88c4ed8, data=0xb892a098) at event_filter.c:158
 gdk_event_apply_filters (filters=<optimized out>, event=<optimized out>, xevent=<optimized out>) at /build/buildd/gtk+2.0-2.24.16/gdk/x11/gdkevents-x11.c:356

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 xfwm4 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Kamil (lampshade-t)
affects: xfwm4 (Ubuntu) → xubuntu-desktop
affects: xubuntu-desktop → xfwm4 (Ubuntu)
affects: xfwm4 → xubuntu-desktop
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
Revision history for this message
pqwoerituytrueiwoq (pqwoerituytrueiwoq) wrote :

relevant bug: Bug #1159778
i believe xfce4-session probally crashed taking xfwm4 down with it

Revision history for this message
In , aldebaran089 (aldebaran089-redhat-bugs) wrote :

Version-Release number of selected component:
xfwm4-4.10.1-1.fc18

Additional info:
reporter: libreport-2.1.4
backtrace_rating: 4
cmdline: xfwm4 --display :0.0 --sm-client-id 2d526a8c4-9c2b-4723-8640-4fc235a88c76
crash_function: XUnmapWindow
executable: /usr/bin/xfwm4
kernel: 3.9.4-200.fc18.i686
runlevel: N 5
uid: 1000
xsession_errors:

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 XUnmapWindow at UnmapWin.c:39
 #1 wireframeUpdate at wireframe.c:56
 #2 clientCycleEventFilter at cycle.c:337
 #3 eventXfwmFilter at event_filter.c:158
 #4 gdk_event_apply_filters at gdkevents-x11.c:356
 #5 gdk_event_translate at gdkevents-x11.c:946
 #6 _gdk_events_queue at gdkevents-x11.c:2336
 #12 gtk_main at gtkmain.c:1257
 #13 clientCycle at cycle.c:455
 #14 handleKeyPress at events.c:331

Potential duplicate: bug 814650

Revision history for this message
In , kevin (kevin-redhat-bugs-1) wrote :

What were you doing when this happened?

Can you duplicate it?

Revision history for this message
In , gps (gps-redhat-bugs) wrote :

Opened skype and hipchat right after login.

reporter: libreport-2.1.4
backtrace_rating: 4
cmdline: xfwm4 --display :0.0 --sm-client-id 2a8042087-b441-44bd-adcf-e2cf4ffb47ef
crash_function: XUnmapWindow
executable: /usr/bin/xfwm4
kernel: 3.9.6-200.fc18.x86_64
package: xfwm4-4.10.1-1.fc18
reason: Process /usr/bin/xfwm4 was killed by signal 11 (SIGSEGV)
runlevel: N 5
uid: 1000

Revision history for this message
In , bcotton (bcotton-redhat-bugs) wrote :

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Revision history for this message
In , bcotton (bcotton-redhat-bugs) wrote :

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

affects: xubuntu-desktop → xfwm4
Revision history for this message
In , arielnmz (arielnmz-redhat-bugs) wrote :

Happened to me after closing Eclipse on fedora 20 x86_64.

Revision history for this message
In , austinenglish (austinenglish-redhat-bugs) wrote :

Still an issue in f20, please reopen. (ABRT redirects here).

Revision history for this message
Sebou (radioscope-de) wrote :

I was able to reproduce this issue by plaing with grubs framebuffer settings in /etc/default/grub

When I change it from 640x480 to 1920x1080 for my system specs, this issue appears. When I revert the setting back and reinit everything... the error no longer appears.

Hope this helps.

tags: added: trusty
Revision history for this message
Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount) wrote :

Sebou, are you still able to reproduce this crash in Ubuntu 14.04 or up?

Changed in xfwm4 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount) wrote :

Also, please forward this bug to the Xfce bug tracker. Thanks in advance.

https://bugzilla.xfce.org/

Revision history for this message
In , bcotton (bcotton-redhat-bugs) wrote :

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Revision history for this message
In , bcotton (bcotton-redhat-bugs) wrote :

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Revision history for this message
Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount) wrote :

Please file a new report if you are able to reproduce this crash with one of the current supported versions.

Changed in xfwm4 (Ubuntu):
status: Incomplete → Invalid
Changed in xfwm4 (Fedora):
importance: Unknown → Undecided
status: Unknown → Won't Fix
Revision history for this message
Yousuf 'Jay' Philips (philipz85) wrote :
Revision history for this message
In , bugzilla (bugzilla-redhat-bugs) wrote :

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.