Bug 858821

Summary: [abrt] xorg-x11-server-Xorg-1.12.3-1.fc17: x86_fallback_frame_state: Process /usr/bin/Xorg was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Robin Axelsson <gu99roax>
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: christianvanbrauner, hk.stefansson, mruminski, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:7809a586293cd59db856f507fb2f93aef8b0d642
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 19:49:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: var_log_messages
none
File: open_fds none

Description Robin Axelsson 2012-09-19 18:06:07 UTC
Version-Release number of selected component:
xorg-x11-server-Xorg-1.12.3-1.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
backtrace_rating: 4
cmdline:        /usr/bin/X :0 vt1 -background none -nolisten tcp -auth /var/run/kdm/A:0-GPq9ab
crash_function: x86_fallback_frame_state
kernel:         3.5.2-3.fc17.i686

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 x86_fallback_frame_state at ./md-unwind-support.h
: #1 uw_frame_state_for at ../../../libgcc/unwind-dw2.c
: #2 _Unwind_Backtrace at ../../../libgcc/unwind.inc
: #3 __backtrace at ../sysdeps/i386/backtrace.c
: #4 xorg_backtrace at backtrace.c
: #5 OsSigHandler at osinit.c
: #8 x86_fallback_frame_state at ./md-unwind-support.h
: #9 uw_frame_state_for at ../../../libgcc/unwind-dw2.c
: #10 _Unwind_Backtrace at ../../../libgcc/unwind.inc
: #11 __backtrace at ../sysdeps/i386/backtrace.c

Comment 1 Robin Axelsson 2012-09-19 18:06:09 UTC
Created attachment 614510 [details]
File: core_backtrace

Comment 2 Robin Axelsson 2012-09-19 18:06:12 UTC
Created attachment 614511 [details]
File: environ

Comment 3 Robin Axelsson 2012-09-19 18:06:14 UTC
Created attachment 614512 [details]
File: backtrace

Comment 4 Robin Axelsson 2012-09-19 18:06:16 UTC
Created attachment 614513 [details]
File: limits

Comment 5 Robin Axelsson 2012-09-19 18:06:18 UTC
Created attachment 614514 [details]
File: cgroup

Comment 6 Robin Axelsson 2012-09-19 18:06:21 UTC
Created attachment 614515 [details]
File: maps

Comment 7 Robin Axelsson 2012-09-19 18:06:23 UTC
Created attachment 614516 [details]
File: dso_list

Comment 8 Robin Axelsson 2012-09-19 18:06:25 UTC
Created attachment 614517 [details]
File: var_log_messages

Comment 9 Robin Axelsson 2012-09-19 18:06:27 UTC
Created attachment 614518 [details]
File: open_fds

Comment 10 Adam Jackson 2012-10-18 21:48:47 UTC
Please update to at least xorg-x11-server-1.12.3-2.fc17 and reopen if this is still reproduceable.

Comment 11 Adam Jackson 2012-10-18 21:49:27 UTC
Please update to at least xorg-x11-server-1.12.3-2.fc17 and reopen if this is still reproduceable.

Comment 12 Robin Axelsson 2012-10-20 10:25:09 UTC
(In reply to comment #11)
> Please update to at least xorg-x11-server-1.12.3-2.fc17 and reopen if this
> is still reproduceable.

I have now updated the system and I don't seem to be able to reproduce this particular bug. But there are still issues with running multi-monitor setup:

When I run this laptop (with WUXGA screen) attached to an external SXGA screen I wish to extend my desktop estate to comprise these two screens. I also have 4 virtual desktops. Each of these two screens has a unique wallpaper. I mark the internal laptop screen as primary screen. That's what my configuration looks like.

So when I want to switch to another virtual desktop by using CTRL-F8, the panel overview isn't shown correctly on the internal screen, instead the image gets corrupted showing 4 fields of what looks like the lowest left 30x80 pixels of the main screen wallpaper that is distorted beyond recognition. The secondary screen show the 4 fields correctly but the upper left field is flickering with the distorted image described above.

Also, the screen looks mashed up briefly after login before the KDE desktop opens.

Comment 13 Fedora End Of Life 2013-07-04 07:33:54 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 17'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 14 Fedora End Of Life 2013-08-01 19:49:29 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

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