Bug 592434

Summary: Evince completely freezes whole desktop
Product: Red Hat Enterprise Linux 6 Reporter: Lubos Kocman <lkocman>
Component: evinceAssignee: Marek Kašík <mkasik>
Status: CLOSED DUPLICATE QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-20 20:10:34 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
problematic pdf
none
xorg log none

Description Lubos Kocman 2010-05-14 20:32:06 UTC
Created attachment 414164 [details]
problematic pdf

Description of problem:

System becomes completely frozen (no respond from desktop) during browsing of attached document in evince. 

I'm able to login to console mode via Ctrl+F* but even by using init 3 && init 5 gdm won't start up (Xorg is up and running, and I can see clock like mouse pointer). 

Version-Release number of selected component (if applicable):

RHEL 6.0 snapshot 2

evince-dvi-2.28.2-9.el6.i686
evince-libs-2.28.2-9.el6.i686
evince-2.28.2-9.el6.i686

How reproducible:


Steps to Reproduce:
1. Open attached pdf document in evince (full screen or maximized window mode)
2. Randomly go trough document via PgUP and PgDown
  
Actual results:

System becomes unusable in graphical mode


Expected results:

Document is browsable without any problems

Additional info:

happened 2times in 20 minutes, reboot was necessary

Comment 1 Lubos Kocman 2010-05-14 20:33:03 UTC
Created attachment 414165 [details]
xorg log

Comment 2 Lubos Kocman 2010-05-14 20:34:37 UTC
Harware is:

Thinkpad X60s (i686)
Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

Comment 4 Lubos Kocman 2010-05-20 20:10:34 UTC

*** This bug has been marked as a duplicate of bug 589470 ***