Bug 679867 - Can't switch back to original rotation
Summary: Can't switch back to original rotation
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 15
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-23 18:01 UTC by Stéphane Maniaci
Modified: 2011-03-19 09:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-19 09:06:55 UTC
Type: ---


Attachments (Terms of Use)
Xorg.0.log (99.01 KB, text/plain)
2011-02-23 18:01 UTC, Stéphane Maniaci
no flags Details
output of 'dmesg' (85.15 KB, text/plain)
2011-02-23 18:03 UTC, Stéphane Maniaci
no flags Details

Description Stéphane Maniaci 2011-02-23 18:01:54 UTC
Created attachment 480544 [details]
Xorg.0.log

Part of the Radeon test day;

Description of problem:
I ran gnome-control-center -> Displays, and rotated my screen anti-clockwise. It worked fine, so I kept the current configuration, then I selected normal again, and tried to apply my settings. The screen got corrupted, and the only way I found to get back to my desktop was to manually kill Xorg through tty2.

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


How reproducible:
Always

Steps to Reproduce:
1.gnome-control-center -> Displays
2. Rotate screen anti-clockwise and apply ;
3. Switch back to normal orientation and apply.

Actual results:
Screen image gets corrupted, it's just blue lines and randomness.

Expected results:
Gets back to normal orientation smoothly.


Additional info:
Smolt profile: http://www.smolts.org/client/show/pub_052c895c-e24b-4762-bbe3-164c463f0a9d

Comment 1 Stéphane Maniaci 2011-02-23 18:03:06 UTC
Created attachment 480546 [details]
output of 'dmesg'

Comment 2 Stéphane Maniaci 2011-02-23 18:06:11 UTC
Actually, I can't reproduce this anymore. I don't know what went wrong the first time.


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