Bug 639057

Summary: [Arrandale] display switching fails with desktop effects enabled
Product: [Fedora] Fedora Reporter: Alex Williamson <alex.williamson>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 15CC: ajax, awilliam, mcepl, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 19:25:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
dmesg anotated
messages anotated
Xorg.0.log anotated none

Description Alex Williamson 2010-09-30 17:30:26 UTC
Description of problem:
Using the graphics test day CD on a Lenovo X201 Core i5 system, when desktop effects are enabled (compiz), I get wobbly windows and workspaces correctly on either the laptop display or the external monitor, but if I use the hotkey to switch the display, I get a black screen.  The only way back seems to switch to a VT (which works) and kill X.

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

How reproducible:

Steps to Reproduce:
1. switch to exclusively the internal or external display
2. enable desktop effects
3. switch to the other display
Actual results:
black screen

Expected results:

Additional info:

Comment 1 Matěj Cepl 2010-10-01 11:13:02 UTC
Well, YOU should know what to expect:

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Alex Williamson 2010-10-01 14:28:02 UTC
Created attachment 451026 [details]

Comment 3 Alex Williamson 2010-10-01 14:28:30 UTC
Created attachment 451027 [details]

Comment 4 Alex Williamson 2010-10-01 14:28:56 UTC
Created attachment 451028 [details]

Comment 5 Alex Williamson 2010-10-01 14:33:20 UTC
Requested logs attached.  I don't have an xorg.conf.  Also, I failed to note in the original report that when the screen goes black, I still have the cursor and can move it around the screen.  Also, my comment about exclusively using the internal or external display is probably a red herring.  I had to switch a couple times before it triggered this morning, and I think it finally triggered on a mode with both displays active.  Also potentially triggers when I use the laptop undocked, then return it to the dock, adding the external display.

Comment 6 Adam Williamson 2010-10-06 22:36:14 UTC
matej: I think you got Alex confused with me :)

Thanks for the report, Alex. If you switch to a VT and back when you're in the 'black screen with cursor visible' state, does the desktop show up? That happens on my laptop after resuming from suspend (though that's a nouveau system).

Comment 7 Alex Williamson 2010-10-06 22:45:14 UTC
(In reply to comment #6)
> Thanks for the report, Alex. If you switch to a VT and back when you're in the
> 'black screen with cursor visible' state, does the desktop show up? That
> happens on my laptop after resuming from suspend (though that's a nouveau
> system).

Nope, switching to a VT and back to X doesn't recover the display.

Comment 8 Adam Williamson 2010-10-07 18:36:15 UTC
could you let us know the time, in /var/log/messages, when you switched displays and hit the bug?

Comment 9 Alex Williamson 2010-10-07 21:14:07 UTC
Created attachment 452201 [details]
dmesg anotated

Comment 10 Alex Williamson 2010-10-07 21:14:44 UTC
Created attachment 452202 [details]
messages anotated

Comment 11 Alex Williamson 2010-10-07 21:15:18 UTC
Created attachment 452203 [details]
Xorg.0.log anotated

Comment 12 Alex Williamson 2010-10-07 21:16:38 UTC
New logs uploaded with annotations of when I did what.  This time it happened on the first switch.  Tried several things to recover, none successful other than killing X.

Comment 13 Adam Williamson 2010-10-08 15:33:30 UTC
excellent, thanks.

Comment 14 Alex Williamson 2010-12-10 01:48:45 UTC
Please fix this

Comment 15 Alex Williamson 2011-02-25 05:38:07 UTC
Still present in f15 test day iso :(

Comment 16 Alex Williamson 2011-04-19 19:39:55 UTC
Updating to Fedora 15 based on previous comment before this gets auto closed.

Comment 17 Matěj Cepl 2011-04-20 06:10:50 UTC
(In reply to comment #16)
> Updating to Fedora 15 based on previous comment before this gets auto closed.

Sure, just that you don't have to worry THAT much … a month after release of F15 we’ll be auto-closing F13 bugs, not the F14 ones.

Comment 18 Fedora End Of Life 2012-08-07 19:25:39 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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: