Description of problem: On opening the screen drawn by Blender contains fragments of sometimes recognisable elements of other windows on the screen, sometimes not. It looks like fragments of arbitrary memory contents, or like parts of a crazy tile puzzle. The first mouse movement in this window will instantly cause the expected splash screen and window decorations to assert themselves and normal behaviour _seems_ to be restored until the mouse is moved over, for example, the recent files list on the splash screen. This can cause flashing re-appearance of elements of the initial corrupted screen as the mouse moves over different file options. Version-Release number of selected component (if applicable): 2.78c-3 How reproducible: I think it may be necessary to be using Blender on a system which configures the ati/radeon graphics driver. I have tested Blender on a comparable Cauldron installation on a machine which uses the nouveau driver and it behaves normally there. Blender appears to be the only program affected which is why I am not blaming this on ati/radeon (but I am open to persuasion:~) This behaviour first started two or three weeks ago and I have spent time experimenting with a range of versions of Blender. My Mageia 5 installation does not display the same problems with the same version of Blender installed from the Blender nightly builds. Steps to Reproduce: 1. Boot Cauldron on system with ati/radeon graphics 2. Start Blender 3. Move mouse on Blender screen
Created attachment 9241 [details] example splash screen 1
Created attachment 9242 [details] example splash screen 2
Assigning to the registered Blender maintainer.
Assignee: bugsquad => geiger.david68210CC: (none) => marja11
Platform information may be relevant. GPU: AMD A10-5800K APU with Radeon(tm) HD Graphics Desktop: LXDE Radeon driver: x11-driver-video-ati 7.9.0-1.mga6 Blender Versions Tested: default Cauldron install: results as above blender-2.78c-linux-glibc219-x86_64 (24 Feb 2017): results as above blender-2.78-af1e48e8ab-linux-glibc219-x86_64 (14 Feb 2017): OK blender-2.78-b60d4800c6-linux-glibc219-x86_64 (8 Apr 2017): OK
Should have checked this too, but here it is, current daily build performs just fine for me as far as the display is concerned: blender-2.78-a85f457195-linux-glibc219-x86_64 (27 Apr 2017): OK
In the absence of any interim requests for more information I thought it might be useful to offer this further progress report now that Cauldron has become Mageia 6. The Blender 2.78c upgrade due to the rebuild against an updated ffmpeg shows no significant improvement. However, the Blender nightly builds continue to perform correctly on my systems. I am currently using blender-2.78-5c30bc285c-linux-glibc219-x86_64 (16 Jul 2017). The installed blender 2.78c-4 continues to be unusable due to excessive flickering and screen-swapping. If there is absolutely ANYTHING I can do to provide more useful information or to run different tests then _please_ ask - I remain ready to respond to any requests, even if it is only to discover I am the only person in the Mageiaverse to suffer from this bug.
Ever confirmed: 1 => 0Status: NEW => UNCONFIRMED
You already have provided the needed information, Richard, but our blender maintainer is short on time. You informed us that blender-2.78c-linux-glibc219-x86_64 from upstream has the same bug as our blender-2.78c-?.mga6 versions, but that bunch of daily builds that you tried don't have the problem. So this problem is likely an upstream bug in their last stable version. I tried to search their bugs, but am not used to their bug tracker https://developer.blender.org/search/query/YC9DY1r0JKTX/#R (if that doesn't return 2.78c issues, then use this link: https://developer.blender.org/ ) I searched for 2.78c combined with ati/radeon or combined with mouse or with flicker, but only found this bug https://developer.blender.org/T51252 that seems a bit similar. Don't hesitate to search for yourself, I may have overlooked a better matching bug report Is your Window Draw Method set to full?
Whiteboard: (none) => MGA6TOOSource RPM: blender-2.78c-3.mga6.src.rpm => blender-2.78c-4.mga6.src.rpmKeywords: (none) => UPSTREAM
(In reply to Marja van Waes from comment #7) Is your Window Draw Method set to full? That threw me for a while but I found your reference in Blender's User Preferences->System. It makes a difference! The default setting is "Automatic" as mine was. The tooltip says "based on graphics card and driver". I tried each other setting in turn. Results below: Automatic: The default case displaying window corruption as illustrated in original submission Triple Buffer: Program starts with an uncorrupted display and mouse movement over the screen causes no flashing or unexpected model movement. Overlap: Most similar to original reported bug. Almost complete window corruption on program start with rapid swapping between corrupted screen decoration and the expected widgets displayed. Overlap Flip: Almost stable display with almost no visible problems. Some highlighting/dimming of parts of the display not being traversed by the mouse along with some vertical "jiggling" of parts of some control windows and some corruption when traversing, for example, Help menu entries. Full: This gives the correct behaviour, similar to the Triple Buffer option, and apparently the one to use if all else fails. So, it begins to look like a problem which only affects (some?) AMD/ATI graphics cards using open drivers in conjunction with the techniques use in THIS Blender release to manage window damage. The fact that this Blender version runs happily for me on systems using nouveau graphics drivers and on Mageia 5 with the fglrx driver would seem to make that point too. I'll have a trawl through the Blender bugs on https://developer.blender.org/ as you suggested and see what I can find,
https://developer.blender.org/T51252 That bug was reported 19 Apr 2017 and closed as "invalid" 4 July after this comment on 28 May: "If Blender works properly with Window Draw Method set to Full, then this is not a bug. That is simply the setting that plays nicely with your particular graphics card + driver..." The reporter described the same effects I am seeing, though he also had a problem with Wayland. His graphics hardware would, presumably, be using the open ati drive for his Radeon HD 5770. Fair enough. It seems churlish to point out that Blender 2.78 was working just fine for me prior to the 2.78c release, and perhaps quarrelsome to point out that "[playing nicely with] your particular graphics card + driver" is precisely the purpose of the "Automatic" selection, so I will say nothing and change the setting from Automatic to Full or Triple Buffer. May I suggest that we note this issue in the Errata for Mageia 6 since it is likely that Blender users with ATI graphics will be faced with this corruption "out of the box"? Otherwise, feel free to close this bug in whatever way you think most suitable.
Just tidying house.
Resolution: (none) => FIXEDStatus: UNCONFIRMED => RESOLVED