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

2017-03-05 Thread Timo Aaltonen
I'm going to assume this is fixed with mesa 12.0.6 and if you enable DRI3 or uninstall xserver-xorg-video-intel (which lets it fall back on -modeset which uses DRI3) ** Changed in: mesa (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a

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

2017-01-01 Thread Luigi R.
Same for me on Ubuntu 16.0.1. I get a black screen by using DRI_PRIME=1 glxgears but the frame is highen the Intel card. Is it normal that xrandr --listproviders returns 2 providers for the AMD/ATI card? Providers: number : 3 Provider 0: id: 0x6b cap: 0x9, Source Output, Sink Offload crtcs: 3

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

2016-08-24 Thread munbi
Don't know if it can help, but enabling DRI3 solves the problem for me. Just added this to /usr/share/X11/xorg.conf.d/20-intel.conf : Section "Device" Identifier "Card0" Driver "Intel" Option "DRI" "3" EndSection ad restarted X -- You received this bug notification

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

2016-08-23 Thread munbi
Same problem here: Dell Latitude E6540 with Intel HD4000 + AMD Radeon HD8790M (OLAND), Ubuntu 16.04 updated. Some OpenGL programs do not refresh the windows and shows only artifacts from background when using DRI_PRIME=1 to lunch (e.g. with kicad pcbnew) Followed comment #11 suggestion and

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

2016-08-23 Thread Alessandro Viprati
Tell me if you need any info or log file, this is a really critical bug and, for now, I can't use my dedicated GPU on Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu.

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

2016-08-23 Thread Alessandro Viprati
Similar problem in Ubuntu 16.04.1 (Unity), with AMD APU (AMD A4-7210 APU with AMD Radeon R3 Graphics "MULLINS") + AMD GPU (AMD Radeon R5 M330) on a Lenovo Yoga 500-14ACL. Everytime I launch a 3D game application with DRI_PRIME=1, the system hangs and returns to the lightdm login screen. I also

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

2016-08-03 Thread Timo Aaltonen
more probably candidate is mesa, please test yakkety which has 12.0.1 commit 9ee3f097b65398250e836785a7e87520eda8298d Author: Michel Dänzer Date: Thu Jun 9 15:15:19 2016 +0900 st/dri: Clear drawable texture_mask in dri2_invalidate_drawable This makes sure

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

2016-08-02 Thread Timo Aaltonen
I think this is a compiz bug ** Package changed: xorg (Ubuntu) => compiz (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1430888 Title: DRI_PRIME with radeon/intel

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

2015-09-06 Thread Christoph Buchner
I see this too with Steam, only for me the log string is " reporting 6 8 17 141". Ctrl-Win-D workaround seems to work. Any updates on this in the meantime? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

[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 Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu.

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

2015-04-08 Thread Simon K
Could you please check your /var/log/Xorg.0.log to see if it contains the following Text: reporting 7 6 5 37 For me it repeats very often if I've started an 3D program with DRI_PRIME where this Error appears. This Message will repeat very often like: [ 1033.178] reporting 7 6 5 37 [

[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