[Touch-packages] [Bug 1430888] Re: DRI_PRIME with radeon/intel windows do not draw

2015-04-08 Thread Wolfgang Wallner
In my case, starting steam causes the text 'reporting 9 5 33 271' to be added to /var/log/Xorg.0.log three times. It's always printed twice in a row and again a few seconds later. For example these are two starts of steam: [ 17002.853] reporting 9 5 33 271 [ 17002.878] reporting 9 5 33 271 [

[Touch-packages] [Bug 1430888] Re: DRI_PRIME with radeon/intel windows do not draw

2015-04-08 Thread Wolfgang Wallner
This bug is already present in 14.10. My system is a HP Pavilion laptop with a muxless Intel/AMD combination (Intel Sandybridge HD graphics and AMD Radeon HD6770). A Workaround that works most of the time is to press Win+D again and again to switch between desktop and game application. After a

[Touch-packages] [Bug 1430888] Re: DRI_PRIME with radeon/intel windows do not draw

2015-04-08 Thread Wolfgang Wallner
Additional note regarding compositing: *) The problem happens regardless if compositing is enabled or disabled. *) Enabling compositing fixes the problem (as far as I can tell always). If I start with compositing on, I need to toggle it for the problem to be gone. If I start with compositing

[Touch-packages] [Bug 1430888] Re: DRI_PRIME with radeon/intel windows do not draw

2015-04-08 Thread Wolfgang Wallner
The problem is also independent of multi-monitor configurations. I use a dual monitor setup, and it happens regardless if both monitors are activated or just one of them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg

[Touch-packages] [Bug 1430888] Re: DRI_PRIME with radeon/intel windows do not draw

2015-04-08 Thread Wolfgang Wallner
I tried to reproduce the problem with glxgears. It can happen, but it is harder to reproduce than with steam. For steam it happens every time, for glxgears it only happened twice out of ~15 tries. But when it happens in glxgears, no reporting 9 5 33 271 lines are added to Xorg.0.log, so I think