Bug 447157 - Enabling KDE thumbnail update effect freezes Mobility Radeon 9200 system
Summary: Enabling KDE thumbnail update effect freezes Mobility Radeon 9200 system
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 9
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-18 11:20 UTC by James
Modified: 2018-04-11 10:10 UTC (History)
2 users (show)

Fixed In Version: 2008-07-03
Clone Of:
Environment:
Last Closed: 2008-07-08 23:54:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Typical Xorg.0.log for this system (33.20 KB, text/plain)
2008-05-18 11:20 UTC, James
no flags Details
Output of lspci -nnvv. (12.56 KB, text/plain)
2008-05-18 11:21 UTC, James
no flags Details

Description James 2008-05-18 11:20:42 UTC
Description of problem:
Enabling the Update Thumbnails option in KDE Desktop Effects causes my Mobility
Radeon 9200 notebook to lock solid (no mouse or keyboard response, no response
to ping).

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.8.0-14.fc9.i386
kernel-2.6.25.3-18.fc9.i686

How reproducible:
Always.

Steps to Reproduce:
1. Open KDE desktop settings.
2. Under effects, navigate to advanced options.
3. Check the update thumbnails option.
4. Click apply.
  
Actual results:
System hangs.

Expected results:
No hang, option heeded. (And unprivileged user-space programs prevented from
taking down whole system!)

Additional info:
See attached.

Comment 1 James 2008-05-18 11:20:42 UTC
Created attachment 305840 [details]
Typical Xorg.0.log for this system

Comment 2 James 2008-05-18 11:21:18 UTC
Created attachment 305841 [details]
Output of lspci -nnvv.

Comment 3 James 2008-07-03 19:12:36 UTC
Appears to be fixed with all F9 updates applied as of 2008-07-03.

Comment 4 Matěj Cepl 2008-07-08 23:54:02 UTC
thanks for letting us know


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