Bug 551464

Summary: konqueror reliably triggers X lockup on comic site
Product: [Fedora] Fedora Reporter: Eli <elicarter>
Component: xorg-x11Assignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 11   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-28 15:35:30 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
Xorg.0.log with nomodeset, without causing a lockup
none
dmesg none

Description Eli 2009-12-30 21:01:21 UTC 
Description of problem:
If I browse to http://comics.com/rose_is_rose (or I believe any other comic on that site, or similarly image heavy site elsewhere) using konqueror under KDE on Fedora 11, X will, after a delay, lock up.  The mouse will move, but no keyboard input is recognized, and the screen does not react to the mouse passing over objects on screen.  I am able to ssh into the machine and issue `shutdown -r now` and have that work.

The machine is a Dell XPS M1330 with Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c), and Fedora 11 is fully updated.

Visiting the same site in Firefox does not cause a lockup.

I am booting with `nomodeset` since it won't boot into X otherwise.
I tried the other two accel options: `EXA` (still locks up) and `XAA` (X won't start).

Any suggestions on how I can debug this?

Version-Release number of selected component (if applicable):
Fully up-to-date Fedora11 as of 20091230

How reproducible:
Every time.

Steps to Reproduce:
1.  launch konqueror
2.  go to http://comics.com/rose_is_rose or similar site
3.  wait a minute for it to load, and see it lock up
  
Actual results:
X locks up

Expected results:
No lockup

Additional info:
Comment 1 Eli 2009-12-30 21:21:57 UTC 
Created attachment 381004 [details]
Xorg.0.log with nomodeset, without causing a lockup
Comment 2 Eli 2009-12-30 21:27:19 UTC 
Created attachment 381006 [details]
dmesg
Comment 3 Bug Zapper 2010-04-28 11:38:35 UTC 
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 4 Bug Zapper 2010-06-28 15:35:30 UTC 
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.
Comment 5 Eli 2010-06-30 00:34:23 UTC 
Testing on Fedora 13, I could not reproduce this problem.