Bug 889929 - [abrt] xfwm4-4.10.0-5.fc18: _XAllocID: Process /usr/bin/xfwm4 was killed by signal 6 (SIGABRT)
Summary: [abrt] xfwm4-4.10.0-5.fc18: _XAllocID: Process /usr/bin/xfwm4 was killed by s...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xfwm4
Version: 18
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9d3c8d1f77f3678863c618d9acd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-24 03:59 UTC by Paul
Modified: 2014-02-05 22:55 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 22:55:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (21.95 KB, text/plain)
2012-12-24 03:59 UTC, Paul
no flags Details
File: cgroup (127 bytes, text/plain)
2012-12-24 03:59 UTC, Paul
no flags Details
File: core_backtrace (3.91 KB, text/plain)
2012-12-24 03:59 UTC, Paul
no flags Details
File: dso_list (6.54 KB, text/plain)
2012-12-24 03:59 UTC, Paul
no flags Details
File: environ (1.37 KB, text/plain)
2012-12-24 03:59 UTC, Paul
no flags Details
File: limits (1.29 KB, text/plain)
2012-12-24 03:59 UTC, Paul
no flags Details
File: maps (22.99 KB, text/plain)
2012-12-24 03:59 UTC, Paul
no flags Details
File: open_fds (276 bytes, text/plain)
2012-12-24 03:59 UTC, Paul
no flags Details
File: proc_pid_status (765 bytes, text/plain)
2012-12-24 03:59 UTC, Paul
no flags Details
File: var_log_messages (296 bytes, text/plain)
2012-12-24 03:59 UTC, Paul
no flags Details
Comment (174.04 KB, text/plain)
2013-04-05 13:30 UTC, Blazej
no flags Details

Description Paul 2012-12-24 03:59:07 UTC
Description of problem:
I logged into XFCE, the screen went black and I was brought back into the login screen. I logged in, the screen blanked and it did it again; I had to login three times in order to get to the desktop. Signal 6 was killing the XFCE Window Manager. This problem happened right after I changed the resolution to an HD size.

Version-Release number of selected component:
xfwm4-4.10.0-5.fc18

Additional info:
backtrace_rating: 4
cmdline:        xfwm4 --display :0.0 --sm-client-id 2221f6289-65ad-421e-ae41-43321f7e446a
crash_function: _XAllocID
executable:     /usr/bin/xfwm4
kernel:         3.6.11-3.fc18.i686
remote_result:  581380
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #5 _XAllocID at xcb_io.c:528
 #6 XRenderCreateCursor at Cursor.c:44
 #7 XcursorImageLoadCursor at cursor.c:590
 #8 XcursorImagesLoadCursors at cursor.c:686
 #9 XcursorImagesLoadCursor at cursor.c:705
 #10 XcursorLibraryLoadCursor at library.c:337
 #11 XcursorTryShapeBitmapCursor at xlib.c:417
 #12 _XTryShapeBitmapCursor at CrGlCur.c:220
 #13 XCreatePixmapCursor at CrCursor.c:57
 #14 cursorCreateSpinning at spinning_cursor.c:86

Comment 1 Paul 2012-12-24 03:59:10 UTC
Created attachment 668277 [details]
File: backtrace

Comment 2 Paul 2012-12-24 03:59:12 UTC
Created attachment 668279 [details]
File: cgroup

Comment 3 Paul 2012-12-24 03:59:14 UTC
Created attachment 668281 [details]
File: core_backtrace

Comment 4 Paul 2012-12-24 03:59:15 UTC
Created attachment 668283 [details]
File: dso_list

Comment 5 Paul 2012-12-24 03:59:17 UTC
Created attachment 668284 [details]
File: environ

Comment 6 Paul 2012-12-24 03:59:18 UTC
Created attachment 668286 [details]
File: limits

Comment 7 Paul 2012-12-24 03:59:20 UTC
Created attachment 668288 [details]
File: maps

Comment 8 Paul 2012-12-24 03:59:23 UTC
Created attachment 668289 [details]
File: open_fds

Comment 9 Paul 2012-12-24 03:59:25 UTC
Created attachment 668290 [details]
File: proc_pid_status

Comment 10 Paul 2012-12-24 03:59:27 UTC
Created attachment 668291 [details]
File: var_log_messages

Comment 11 Kevin Fenzi 2012-12-25 17:58:02 UTC
This looks like some deeper problem... 

Can you attach: 

dmesg

~/.xsession-errors

/var/log/Xorg.0.log 

Thanks!

Comment 12 Blazej 2013-04-05 13:30:51 UTC
Created attachment 915701 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).

Comment 13 Kevin Fenzi 2013-04-05 15:43:02 UTC
Its back to stable now? Or are you continuing to see the crashes?

Will dig through the logs... thanks!

Comment 14 Fedora End Of Life 2013-12-21 15:15:32 UTC
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.

Comment 15 Fedora End Of Life 2014-02-05 22:55:47 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.