Note that theese same drivers are already in use with same x11 server and kernel so it has already seen some testing....

*** Bug 22260 has been marked as a duplicate of this bug. ***

CC: (none) => micheelsen

And since this is low-level... it should be tested on both 32bit and 64bit installs

Starting on this for 64 bits.

CC: (none) => tarazed25

(In reply to Len Lawrence from comment #4)
> Starting on this for 64 bits.

Same here, on my Probook for now, but others to follow. This one sounds like it needs a wide variety of hardware tested.

CC: (none) => andrewsfarm

Prep for M6/64 real EFI hardware AMD/ATI/Radeon video

The updates available to me are (installing same), while I have the list:
- lib64dri-drivers-17.3.2-1.mga6.x86_64
- lib64drm2-2.4.89-1.mga6.x86_64
- lib64drm_amdgpu1-2.4.89-1.mga6.x86_64
- lib64drm_intel1-2.4.89-1.mga6.x86_64
- lib64drm_nouveau2-2.4.89-1.mga6.x86_64
- lib64drm_radeon1-2.4.89-1.mga6.x86_64
- lib64gbm1-17.3.2-1.mga6.x86_64
- lib64glapi0-17.3.2-1.mga6.x86_64
- lib64kms1-2.4.89-1.mga6.x86_64
- lib64mesaegl1-17.3.2-1.mga6.x86_64
- lib64mesagl1-17.3.2-1.mga6.x86_64
- lib64mesaglesv2_2-17.3.2-1.mga6.x86_64
- lib64wayland-egl1-17.3.2-1.mga6.x86_64
- lib64xatracker2-17.3.2-1.mga6.x86_64
- libdrm-common-2.4.89-1.mga6.x86_64
- mesa-17.3.2-1.mga6.x86_64

Mageia 6 :: x86_64 
All packages installed or updated cleanly.

Ran glxgears in normal and fullscreen modes - comes from mesa-demos.
glxspheres from virtualgl worked.
Video graphics with vlc, mplayer and Youtube working OK.
Image display with gqview, eom, gwenview, ristretto and ImageMagick worked fine.
glmark2 ran to completion.  Manipulated an image in the Gimp.  Used eom to run an animated gif.  Changed the desktop background image and traversed workspaces OK.  
Terminals behaving themselves and window stacking is fine.  No mouse pointer problems.  Desktop icon replacement works as always.  Logged out - Plymouth screen appeared and login was uneventful.

Good enough for this Mate system.  

@ Lewis: agree about more hardware and a range of desktops.  GNOME for the Wayland stuff I guess.

Re comment 7 : that was nvidia.
Card-2: NVIDIA GK104 [GeForce GTX 770]
GLX Renderer: GeForce GTX 770/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 384.111

HP Probook 6550b, Intel i3, 8GB RAM, integrated Intel graphics, Intel wifi.

64-bit Plasma install.

The following 26 packages are going to be installed:

- lib64dri-drivers-17.3.2-1.mga6.x86_64
- lib64drm2-2.4.89-1.mga6.x86_64
- lib64drm_amdgpu1-2.4.89-1.mga6.x86_64
- lib64drm_intel1-2.4.89-1.mga6.x86_64
- lib64drm_nouveau2-2.4.89-1.mga6.x86_64
- lib64drm_radeon1-2.4.89-1.mga6.x86_64
- lib64gbm1-17.3.2-1.mga6.x86_64
- lib64glapi0-17.3.2-1.mga6.x86_64
- lib64kms1-2.4.89-1.mga6.x86_64
- lib64mesaegl1-17.3.2-1.mga6.x86_64
- lib64mesagl1-17.3.2-1.mga6.x86_64
- libdri-drivers-17.3.2-1.mga6.i586
- libdrm-common-2.4.89-1.mga6.x86_64
- libdrm2-2.4.89-1.mga6.i586
- libdrm_amdgpu1-2.4.89-1.mga6.i586
- libdrm_intel1-2.4.89-1.mga6.i586
- libdrm_nouveau2-2.4.89-1.mga6.i586
- libdrm_radeon1-2.4.89-1.mga6.i586
- libgbm1-17.3.2-1.mga6.i586
- libglapi0-17.3.2-1.mga6.i586
- libmesaegl1-17.3.2-1.mga6.i586
- libmesagl1-17.3.2-1.mga6.i586
- mesa-17.3.2-1.mga6.x86_64
- x11-driver-video-amdgpu-1.4.0-1.mga6.x86_64
- x11-driver-video-ati-7.10.0-1.mga6.x86_64
- x11-driver-video-intel-2.99.917-42.mga6.x86_64

6.6MB of additional disk space will be used.

16MB of packages will be retrieved.

Is it ok to continue?

Tainted repositories were activated, so those packages were used. I assume the 32-bit packages were presented because 32-bit Google Earth is installed on this system. To my knowledge it is the only 32-bit app installed.

Packages installed cleanly. I was not advised to restart the system, but after rendering the Testing repositories inactive, I rebooted anyway.

The reboot looks normal, but finished up to a black screen. Mouse, touchpad, keyboard all show no reaction. Every once in a while the wifi and hard drive LEDs flash, but nothing shows on the screen. If I let it sit long enough for Power Management to dim the screen, then hit a key, I get a brief flash of the desktop and then it goes black again. Hitting the power button shows a flash of the desktop, then shows the Plasma logout, which works normally to shut down, but clicking on Cancel takes me back to the black screen. A complete shutdown and restart is no different than a reboot.

Did I miss something on the list? I double-checked everything presented, but it's a long list.

I am not a happy camper. While this isn't my production computer, I'd really like to have it back soon. Please let me know what I can do to help diagnose this and fix it ASAP, and if we can't, what I can do to revert to a working system.

Can you get as far as a run level 3 login and run drakx11 to choose say the nouveau driver or vesa?  That is the sort of thing I would be inclined to try.  Then there are those other things we tried while testing isos, like specifying a different xdriver on the kernel boot line, even nomodeset.  Just shooting in the dark really.  In runlevel 3 you could examine log files and configs.

Comparing our manifests there are a few differences: -devel packages installed here, drm-utils, ...  The full list contains 43 packages.  Doubtless some of these are irrelevant on this machine.

Away to try a reboot.

No problems with a reboot.
It is a long list, agreed.  My technique with these long lists is to cut and paste and edit then feed the edited list to a small script which tries to install everything before the update.  If run from the command line you can give any required responses as they come up.  Any packages which are irrelevant should do no harm.  After the testing repositories are enabled you can rely on MageiaUpdate cherry-picking or run the script again.

Run level 3 worked. Intel 810 and later graphics, so nouveau wouldn't help much. I used drakx11 to set the vesa driver, then rebooted. That wouldn't work either, until I added nomodeset to the kernel options. 

That got me back to a working graphical system, so it would seem the problem may have something to do with one of the Intel packages. My bet is on the x11 driver that was installed.

Going back again now to check the package list for something I missed. drm-utils wasn't presented the first time, I looked for it when other drm packages were there. I don't know anything of what these packages do, just shooting in the dark, too. Or maybe in the blinding light.

Looks like I missed two - lib64wayland-egi1 and lib64xatracker2. Installed them, changed graphics back to Intel810 or later, rebooted.

No change. Still has the black screen. Sigh.

Went back to the vesa driver, and it still works.

Awaiting further advice...

I would imagine that several of the packages are not really relevant on your system, as on mine, but installing them all should do no harm.  I do note that here all the tainted versions have been overwritten so if you still have some there might be a conflict.  Running out of ideas here but we must get you back on track.

I can use the "shotgun" approach if nothing else works, but I'd rather wait for someone to suggest a better way to track the problem down. "Test, don't guess," and all that. 

I've gone far enough for this evening. The laptop is functional with the vesa driver, if not fully at least enough to use it if I need to. And I have other computers to play with.

Time for a break.

Just to eliminate one of the variables at this end I tried Plasma - no problems until logout - the kms-server-greeter error popped up and went round in a loop so the only way to go was a reboot.  That went normally and GNOME came up when selected.  Logging out from that was normal as well.  Now back in Mate.

So, do you have GNOME or any other desktop available to try?

If you suspect the Intel side it might be worth my trying to use Intel graphics.  Not something I can remember using.  Already tomorrow so I have to take a break also.

Just tested some Steam games (Aragami, Bioshock Infinte, Counter Strike 1.6, Dreamfall Chapters, Layers of Fear, Warlock of Firetop Mountain, Wasteland 2 : DC) on my x86_64 system, but only started it, loaded a level and played 2-5 minutes because of lack of time yet.

- No problems found. Works good.
Tested under LXDE desktop environment


OpenGL vendor string: X.Org
OpenGL renderer string: AMD CAPE VERDE (DRM 2.50.0 / 4.14.13-desktop-1.mga6, LLVM 3.9.1)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.2
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 17.3.2
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.3.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:

CC: (none) => linux

(In reply to Thomas Andrews from comment #14)
> Went back to the vesa driver, and it still works.
> 
> Awaiting further advice...

With testing repos *disabled*, do:

urpmi --downgrade x11-driver-video-intel

and it should roll back to previous driver

@TJ, comment #16:

Yes the "shotgun approach" is not to be recommended in general but when there is no paper trail in the way of journal and dmesg output and other logs it is difficult to know how else to approach your problem.  My efforts have led nowhere but trying to use the Intel driver under Plasma led to an unresponsive black screen after reboot.  That was pre-update.  There was a brief message at some point about the intel driver needing to be rebuilt with the gdx? driver.  Meant nothing to me.

on mga6-64

I installed all of the packages listed

On re-booting, after logging in to plasma, the screen went blank 

I downgraded the intel driver as suggested, but on re-booting got the same blank screen on logging into plasma

In order to have a working system, I've downgraded all the testing packages

I've now noticed that there are other intel packages. Perhaps I should have  downgraded those as well as the intel driver. I'll try to test again without any of the intel packages. Later today possibly.

Dell product: Precision Tower 3620
Mobo: Dell model: 09WH54 
Card: Intel HD Graphics 530
CPU: Quad core Intel Core i7-6700 (-HT-MCP-)
PC-BIOS (legacy) boot
GPT partitions

CC: (none) => jim

Also installed on my system is vaapi-driver-intel-1.7.3-1.mga6.x86_64

Is it possible that there should be an update for that?

(In reply to James Kerr from comment #21)
> on mga6-64
> 
> I installed all of the packages listed
> 
> On re-booting, after logging in to plasma, the screen went blank 
> 

anything interesting in the logs ?

 
> I've now noticed that there are other intel packages. Perhaps I should have 
> downgraded those as well as the intel driver. I'll try to test again without
> any of the intel packages. Later today possibly.
> 

No, they better stay in sync with their counterparts...
but you can try one package set at a time like I've grouped them in comment 0 ...

so first block is libdrm, second is the mesa block, and third the x11-driver-video-* matching your hw.

and you can ignore wayland-protocols-devel, it is only needed to build libdrm.

if mesa block fails, try to downgrade that, and install x11-driver-video-*
to see if that one still works

(In reply to James Kerr from comment #22)
> Also installed on my system is vaapi-driver-intel-1.7.3-1.mga6.x86_64
> 
> Is it possible that there should be an update for that?

could be useful, but it should not affect the blank screen

Intel graphics here (Thinkpad X260) & Plasm5 desktop.

Also got black screen when updated the following packages:

- lib64drm2-2.4.89-1.mga6.x86_64
- lib64drm_amdgpu1-2.4.89-1.mga6.x86_64
- lib64drm_intel1-2.4.89-1.mga6.x86_64
- lib64drm_nouveau2-2.4.89-1.mga6.x86_64
- lib64drm_radeon1-2.4.89-1.mga6.x86_64
- lib64kms1-2.4.89-1.mga6.x86_64
- libdrm-common-2.4.89-1.mga6.x86_64

- lib64dri-drivers-17.3.2-1.mga6.x86_64
- lib64gbm1-17.3.2-1.mga6.x86_64
- lib64glapi0-17.3.2-1.mga6.x86_64
- lib64mesaegl1-17.3.2-1.mga6.x86_64
- lib64mesagl1-17.3.2-1.mga6.x86_64
- lib64wayland-egl1-17.3.2-1.mga6.x86_64
- mesa-17.3.2-1.mga6.x86_64

- x11-driver-video-intel-2.99.917-42.mga6.x86_64

Fortunately - pressing ctr+alt+del brings up Plasma logout screen.

Here helps when I downgraded the mesa block.

libdrm block + x11-driver-video-intel upgrade seems to be OK.

CC: (none) => jyri2000

Ok, so mesa still have some issues for some :/

Can any of you try to get some logs of what fails...

(In reply to Len Lawrence from comment #20)
> @TJ, comment #16:
> 
> Yes the "shotgun approach" is not to be recommended in general but when
> there is no paper trail in the way of journal and dmesg output and other
> logs it is difficult to know how else to approach your problem.  My efforts
> have led nowhere but trying to use the Intel driver under Plasma led to an
> unresponsive black screen after reboot.  That was pre-update.  There was a
> brief message at some point about the intel driver needing to be rebuilt
> with the gdx? driver.  Meant nothing to me.

Mostly I was thinking of the average user when I was avoiding installing everything - which, as James has determined wouldn't have helped anyway. Users are going to install the packages presented, and no more. They are trusting us to present all of the correct ones. Better to track down the one or two or three packages that are really at fault.

You guys have no idea how reassuring it is not to be alone in seeing this problem. Being the first to report something this important without knowing a thing about how to proceed is a scary thing indeed.

Thomas, I'm still under the vesa driver. That was the last boot. Next to last was run level three, where I returned to the vesa driver and "permanently" added "nomodeset" to the kernel options. The one before that was the last one with the Intel driver and all the packages updated. I don't know why I couldn't boot again this morning and get the logs you need, if you just remind me which ones they are and how to get them. 

If I have to do this enough times, another scary thought, maybe someday I'll remember how without asking.

Installing blocks of packages, I get the same result as reported in comment#25.

The "black screen" only occurs with the mesa block is updated.

The xorg logs suggest that it failed to load the EDID

I can't find anything helpful in the journal

Created attachment 9899 [details]
xorg.log with updated mesa

xorg log when plasma login ends in blank screen

Created attachment 9900 [details]
xorg log without updating mesa

xorg.log when plasma desktop launches successfully

Created attachment 9901 [details]
journal -b with updated mesa

journal -b with updated mesa

Created attachment 9902 [details]
journal -b without updating mesa

journal when plasma desktop launches successfully

I just updated Mesa to 17.3.2, and now tooltips no longer appear in Firefox. They were working fine a few minutes ago before the upgrade. :( Am I the only one to see this problem?

CC: (none) => LpSolit

MGA6-32 on Dell Latitude D600 MATE
Installed whole bunch except devel packages and rebooted.
Usual bunch of text, music, picture, video and web content, all OK.
You have my blessing.

CC: (none) => herman.viaene

Things are even worse than expected. Not only are tooltips no longer displayed in Firefox, but clicking the "start menu" (à la Windows) in Plasma gives me a black screen. Pressing ESC brings the UI back. It looks like the menu is incorrectly drawn.

I use Skylake: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz

Reverting updates fixes all problems described in comment 34 and comment 36.

So use a real DE :)

are any of you that have the problems using the qt/plasma stuff currently in testing or are you running a clean release/updates install ?

I've pushed a new mesa set to the buildsystem, please test with it:

the new rpms are:

SRPMS:
mesa-17.3.2-1.1.mga6.src.rpm

i586:
libd3d1-17.3.2-1.1.mga6.i586.rpm
libd3d1-devel-17.3.2-1.1.mga6.i586.rpm
libdri-drivers-17.3.2-1.1.mga6.i586.rpm
libgbm1-17.3.2-1.1.mga6.i586.rpm
libgbm1-devel-17.3.2-1.1.mga6.i586.rpm
libglapi0-17.3.2-1.1.mga6.i586.rpm
libglapi0-devel-17.3.2-1.1.mga6.i586.rpm
libmesaegl1-17.3.2-1.1.mga6.i586.rpm
libmesaegl1-devel-17.3.2-1.1.mga6.i586.rpm
libmesagl1-17.3.2-1.1.mga6.i586.rpm
libmesagl1-devel-17.3.2-1.1.mga6.i586.rpm
libmesaglesv1_1-17.3.2-1.1.mga6.i586.rpm
libmesaglesv1_1-devel-17.3.2-1.1.mga6.i586.rpm
libmesaglesv2_2-17.3.2-1.1.mga6.i586.rpm
libmesaglesv2_2-devel-17.3.2-1.1.mga6.i586.rpm
libosmesa8-17.3.2-1.1.mga6.i586.rpm
libosmesa-devel-17.3.2-1.1.mga6.i586.rpm
libvdpau-driver-nouveau-17.3.2-1.1.mga6.i586.rpm
libvdpau-driver-r300-17.3.2-1.1.mga6.i586.rpm
libvdpau-driver-r600-17.3.2-1.1.mga6.i586.rpm
libvdpau-driver-radeonsi-17.3.2-1.1.mga6.i586.rpm
libvulkan-devel-17.3.2-1.1.mga6.i586.rpm
libvulkan_intel-17.3.2-1.1.mga6.i586.rpm
libvulkan_radeon-17.3.2-1.1.mga6.i586.rpm
libwayland-egl1-17.3.2-1.1.mga6.i586.rpm
libwayland-egl1-devel-17.3.2-1.1.mga6.i586.rpm
libxatracker2-17.3.2-1.1.mga6.i586.rpm
libxatracker2-devel-17.3.2-1.1.mga6.i586.rpm
mesa-17.3.2-1.1.mga6.i586.rpm
mesa-common-devel-17.3.2-1.1.mga6.i586.rpm


x86_64:
lib64d3d1-17.3.2-1.1.mga6.x86_64.rpm
lib64d3d1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64dri-drivers-17.3.2-1.1.mga6.x86_64.rpm
lib64gbm1-17.3.2-1.1.mga6.x86_64.rpm
lib64gbm1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64glapi0-17.3.2-1.1.mga6.x86_64.rpm
lib64glapi0-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaegl1-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaegl1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64mesagl1-17.3.2-1.1.mga6.x86_64.rpm
lib64mesagl1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaglesv1_1-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaglesv1_1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaglesv2_2-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaglesv2_2-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64osmesa8-17.3.2-1.1.mga6.x86_64.rpm
lib64osmesa-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64vdpau-driver-nouveau-17.3.2-1.1.mga6.x86_64.rpm
lib64vdpau-driver-r300-17.3.2-1.1.mga6.x86_64.rpm
lib64vdpau-driver-r600-17.3.2-1.1.mga6.x86_64.rpm
lib64vdpau-driver-radeonsi-17.3.2-1.1.mga6.x86_64.rpm
lib64vulkan-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64vulkan_intel-17.3.2-1.1.mga6.x86_64.rpm
lib64vulkan_radeon-17.3.2-1.1.mga6.x86_64.rpm
lib64wayland-egl1-17.3.2-1.1.mga6.x86_64.rpm
lib64wayland-egl1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64xatracker2-17.3.2-1.1.mga6.x86_64.rpm
lib64xatracker2-devel-17.3.2-1.1.mga6.x86_64.rpm
mesa-17.3.2-1.1.mga6.x86_64.rpm
mesa-common-devel-17.3.2-1.1.mga6.x86_64.rpm

(In reply to Thomas Backlund from comment #38)
> So use a real DE :)
> 
> are any of you that have the problems using the qt/plasma stuff currently in
> testing or are you running a clean release/updates install ?

None of the testing stuff here, unless it somehow slipped in by mistake when testing another update. 

Off now to try the new packages...

(In reply to Thomas Andrews from comment #40)

> 
> Off now to try the new packages...

Not so fast - have to wait for them to get to my mirror first.

The following 13 packages are going to be installed:

- lib64dri-drivers-17.3.2-1.1.mga6.x86_64
- lib64gbm1-17.3.2-1.1.mga6.x86_64
- lib64glapi0-17.3.2-1.1.mga6.x86_64
- lib64mesaegl1-17.3.2-1.1.mga6.x86_64
- lib64mesagl1-17.3.2-1.1.mga6.x86_64
- lib64wayland-egl1-17.3.2-1.1.mga6.x86_64
- lib64xatracker2-17.3.2-1.1.mga6.x86_64
- libdri-drivers-17.3.2-1.1.mga6.i586
- libgbm1-17.3.2-1.1.mga6.i586
- libglapi0-17.3.2-1.1.mga6.i586
- libmesaegl1-17.3.2-1.1.mga6.i586
- libmesagl1-17.3.2-1.1.mga6.i586
- mesa-17.3.2-1.1.mga6.x86_64

48B of additional disk space will be used.

16MB of packages will be retrieved.

Is it ok to continue?

After installing the above packages, I switched back to using the "Intel 810 and higher" driver, and rebooted.

Success! I played two videos with vlc, used Firefox, played with Google Earth to check out the i586 packages. Everything looked good.

OK for me on the Probook 6550b, now.

(In reply to Thomas Backlund from comment #39)
> I've pushed a new mesa set to the buildsystem, please test with it:

Problems reported in comment 34 and comment 36 are gone with this new mesa release. Thanks a lot, Thomas! :)

Real hardware, ASRock motherboard, Athlon X2 7750 processor, 8GB, Geforce 9800GT (nvidia340) graphics, Atheros wifi, 64-bit Plasma install.

The following 25 packages are going to be installed:

- lib64dri-drivers-17.3.2-1.1.mga6.x86_64
- lib64drm2-2.4.89-1.mga6.x86_64
- lib64drm_amdgpu1-2.4.89-1.mga6.x86_64
- lib64drm_intel1-2.4.89-1.mga6.x86_64
- lib64drm_nouveau2-2.4.89-1.mga6.x86_64
- lib64drm_radeon1-2.4.89-1.mga6.x86_64
- lib64gbm1-17.3.2-1.1.mga6.x86_64
- lib64glapi0-17.3.2-1.1.mga6.x86_64
- lib64mesaegl1-17.3.2-1.1.mga6.x86_64
- lib64mesagl1-17.3.2-1.1.mga6.x86_64
- lib64wayland-egl1-17.3.2-1.1.mga6.x86_64
- lib64xatracker2-17.3.2-1.1.mga6.x86_64
- libdri-drivers-17.3.2-1.1.mga6.i586
- libdrm-common-2.4.89-1.mga6.x86_64
- libdrm2-2.4.89-1.mga6.i586
- libdrm_amdgpu1-2.4.89-1.mga6.i586
- libdrm_intel1-2.4.89-1.mga6.i586
- libdrm_nouveau2-2.4.89-1.mga6.i586
- libdrm_radeon1-2.4.89-1.mga6.i586
- libglapi0-17.3.2-1.1.mga6.i586
- libmesagl1-17.3.2-1.1.mga6.i586
- mesa-17.3.2-1.1.mga6.x86_64
- x11-driver-video-amdgpu-1.4.0-1.mga6.x86_64
- x11-driver-video-ati-7.10.0-1.mga6.x86_64
- x11-driver-video-intel-2.99.917-42.mga6.x86_64

6.6MB of additional disk space will be used.

17MB of packages will be retrieved.

Is it ok to continue?

As with the Probook, I'm assuming the i586 packages are presented because 32-bit Google earth is installed. Also, tainted repositories are activated, so those packages are the ones that are installed.

The packages installed cleanly, after which I triple-checked to make sure I hadn't missed any. I then rebooted, because that's what made the above problem show up on the other hardware.

The Plasma desktop came up normally. I watched a couple of videos, used Firefox, played with Google Earth. All looks good.

OK for me on this hardware. Will try a couple of 32-bit installs tomorrow.

Real x64 hardware with AMD/ATI/Radeon HD7310 graphics

See C6 for original packages. I have been running under Mate with those updates from C0 without issues.
But I see that a new lot are issued in C39. Will apply them and report back.
- lib64dri-drivers-17.3.2-1.1.mga6.x86_64
- lib64gbm1-17.3.2-1.1.mga6.x86_64
- lib64glapi0-17.3.2-1.1.mga6.x86_64
- lib64mesaegl1-17.3.2-1.1.mga6.x86_64
- lib64mesagl1-17.3.2-1.1.mga6.x86_64
- lib64mesaglesv2_2-17.3.2-1.1.mga6.x86_64
- lib64wayland-egl1-17.3.2-1.1.mga6.x86_64
- lib64xatracker2-17.3.2-1.1.mga6.x86_64
- mesa-17.3.2-1.1.mga6.x86_64
Perhaps more demanding to use Plasma.

I've been using all of this since 2018-01-10 on a Gnome x86_64 on intel i7-7500u  system without issues

Installed the packages listed in comment#39

Rebooted to a working plasma desktop

Looks OK on this system

Graphics:  Card: Intel HD Graphics 530
           Display Server: Mageia X.org 119.5 drivers: v4l,intel 
           Resolution: 1920x1080@60.00hz
           GLX Renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) 
           GLX Version: 3.0 Mesa 17.3.2
CPU: Quad core Intel Core i7-6700 (-HT-MCP-)

Follow-up to comment 25.
Thinkpad X260 & Plasm5 desktop
VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07)

Updated following packages:

- lib64dri-drivers-17.3.2-1.1.mga6.x86_64
- lib64gbm1-17.3.2-1.1.mga6.x86_64
- lib64glapi0-17.3.2-1.1.mga6.x86_64
- lib64mesaegl1-17.3.2-1.1.mga6.x86_64
- lib64mesagl1-17.3.2-1.1.mga6.x86_64
- lib64wayland-egl1-17.3.2-1.1.mga6.x86_64
- mesa-17.3.2-1.1.mga6.x86_64

Plasma desktop started OK and so far no anomalies - seems to be OK

MGA6-32 on Dell Latitude D600 MATE
Installed whole bunch except devel packages and rebooted.
Usual bunch of text, music, picture, video and web content, all OK.
You have my blessing.

MGA6-32 on an HP Probook 6550b, i3, 8GB RAM, integrated Intel graphics, Intel wifi. This is the same hardware that had the problem with the 64-bit install in Comment 9.

The following 17 packages are going to be installed:

- libdri-drivers-17.3.2-1.1.mga6.i586
- libdrm-common-2.4.89-1.mga6.i586
- libdrm2-2.4.89-1.mga6.i586
- libdrm_amdgpu1-2.4.89-1.mga6.i586
- libdrm_intel1-2.4.89-1.mga6.i586
- libdrm_nouveau2-2.4.89-1.mga6.i586
- libdrm_radeon1-2.4.89-1.mga6.i586
- libgbm1-17.3.2-1.1.mga6.i586
- libglapi0-17.3.2-1.1.mga6.i586
- libmesaegl1-17.3.2-1.1.mga6.i586
- libmesagl1-17.3.2-1.1.mga6.i586
- libwayland-egl1-17.3.2-1.1.mga6.i586
- libxatracker2-17.3.2-1.1.mga6.i586
- mesa-17.3.2-1.1.mga6.i586
- x11-driver-video-amdgpu-1.4.0-1.mga6.i586
- x11-driver-video-ati-7.10.0-1.mga6.i586
- x11-driver-video-intel-2.99.917-42.mga6.i586

3.4MB of additional disk space will be used.

10MB of packages will be retrieved.

Is it ok to continue?

The more of these I do, the easier it is to pick out the right packages to test.

Packages installed cleanly. Rebooted after the install, successfully. The usual apps work fine.

OK for me for 32-bit on this hardware.

Same hardware as Comment 44, 32-bit Xfce install.

The following 17 packages are going to be installed:

- libdri-drivers-17.3.2-1.1.mga6.i586
- libdrm-common-2.4.89-1.mga6.i586
- libdrm2-2.4.89-1.mga6.i586
- libdrm_amdgpu1-2.4.89-1.mga6.i586
- libdrm_intel1-2.4.89-1.mga6.i586
- libdrm_nouveau2-2.4.89-1.mga6.i586
- libdrm_radeon1-2.4.89-1.mga6.i586
- libgbm1-17.3.2-1.1.mga6.i586
- libglapi0-17.3.2-1.1.mga6.i586
- libmesaegl1-17.3.2-1.1.mga6.i586
- libmesagl1-17.3.2-1.1.mga6.i586
- libwayland-egl1-17.3.2-1.1.mga6.i586
- libxatracker2-17.3.2-1.1.mga6.i586
- mesa-17.3.2-1.1.mga6.i586
- x11-driver-video-amdgpu-1.4.0-1.mga6.i586
- x11-driver-video-ati-7.10.0-1.mga6.i586
- x11-driver-video-intel-2.99.917-42.mga6.i586

3.4MB of additional disk space will be used.

10MB of packages will be retrieved.

Is it ok to continue?

Packages installed cleanly. After a successful reboot, the usual apps were tried, with no problems noted. 

Looking good for 32-bit on this hardware.

Tested on i7-3630QM with hybrid Intel/NVIDIA graphics configured to use Intel only.

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel Open Source Technology Center (0x8086)
    Device: Mesa DRI Intel(R) Ivybridge Mobile  (0x166)
    Version: 17.3.2
    Accelerated: yes

Running Cinnamon DE. Tested glxgears, vlcplayer playing DVD, BBC iPlayer and YouTube videos in SeaMonkey, eog displaying JPEG images, suspend/resume, LCD brightness control, VirtualBox server. No new issues observed.

CC: (none) => mageia

And same tests repeated on i5-3550 with Radeon 7850 graphics.

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org (0x1002)
    Device: AMD PITCAIRN (DRM 2.50.0 / 4.14.13-desktop-1.mga6, LLVM 3.9.1) (0x6819)
    Version: 17.3.2
    Accelerated: yes

No issues to report.

Real hardware, Intel motherboard, Intel Core2Duo, 8GB RAM, Intel graphics, wired Internet. 64-bit Plasma install, with 32-bit Google Earth installed.

The following 27 packages are going to be installed:

- lib64dri-drivers-17.3.2-1.1.mga6.x86_64
- lib64drm2-2.4.89-1.mga6.x86_64
- lib64drm_amdgpu1-2.4.89-1.mga6.x86_64
- lib64drm_intel1-2.4.89-1.mga6.x86_64
- lib64drm_nouveau2-2.4.89-1.mga6.x86_64
- lib64drm_radeon1-2.4.89-1.mga6.x86_64
- lib64gbm1-17.3.2-1.1.mga6.x86_64
- lib64glapi0-17.3.2-1.1.mga6.x86_64
- lib64mesaegl1-17.3.2-1.1.mga6.x86_64
- lib64mesagl1-17.3.2-1.1.mga6.x86_64
- lib64wayland-egl1-17.3.2-1.1.mga6.x86_64
- lib64xatracker2-17.3.2-1.1.mga6.x86_64
- libdri-drivers-17.3.2-1.1.mga6.i586
- libdrm-common-2.4.89-1.mga6.x86_64
- libdrm2-2.4.89-1.mga6.i586
- libdrm_amdgpu1-2.4.89-1.mga6.i586
- libdrm_intel1-2.4.89-1.mga6.i586
- libdrm_nouveau2-2.4.89-1.mga6.i586
- libdrm_radeon1-2.4.89-1.mga6.i586
- libgbm1-17.3.2-1.1.mga6.i586
- libglapi0-17.3.2-1.1.mga6.i586
- libmesaegl1-17.3.2-1.1.mga6.i586
- libmesagl1-17.3.2-1.1.mga6.i586
- mesa-17.3.2-1.1.mga6.x86_64
- x11-driver-video-amdgpu-1.4.0-1.mga6.x86_64
- x11-driver-video-ati-7.10.0-1.mga6.x86_64
- x11-driver-video-intel-2.99.917-42.mga6.x86_64

6.6MB of additional disk space will be used.

17MB of packages will be retrieved.

Is it ok to continue?

Packages installed cleanly. After a successful reboot, played with several apps. No problems noted.

OK for 64-bit on this hardware.

As part of a test of VirtualBox 5.2.6 (Bug #22408), I created a 32-bit Mageia 6 Plasma guest. After getting updates, and further updating to the 5.2.6 guest additions, I installed the usual suspects from this update, and rebooted.

Looks good in the guest, too.

on mga6-32 in a vbox VM 

installed all of the latest versions of the "graphical stack" packages

VM re-booted to a working plasma desktop

looks OK for mga6-32 in a vbox VM

Tested on a Sony Vaio E Series notebook - Intel i5 4Core
host 4.14.13-desktop-1.mga6, x84_64
kernel driver radeon, Radeon HD 7550M/7570M/7650M
guest Mageia 6 on qemu/kvm, 4.14.13-server-1.mga6, x84_64
kernel driver virtio-pci

$ rpm -qa | grep mesa
lib64mesaegl1-17.3.2-1.1.mga6
lib64mesaglu1-9.0.0-6.mga6
lib64mesagl1-17.3.2-1.1.mga6
mesa-17.3.2-1.1.mga6

Direct rendering: yes on both sides.
Test case transparency in konsole works fine on both sides.
No regression found.

Real x64 hardware with AMD/ATI/Radeon HD7310 graphics
See coment 45 for packages.
Having forgotten a

CC: (none) => lewyssmith

[continued]
Having forgotten about using Plasma, I will try it. But so far, using Mate, all seems OK for me.
4.14.13-tmb-desktop-1.mga6
kernel-firmware-20170531-1.mga6
kernel-firmware-nonfree-20171220-1.mga6.nonfree
radeon-firmware-20171205-1.mga6.nonfree

Same host hardware as Comment 44, 64-bit Mageia 6 Plasma guest in VirtualBox 5.2.6, on a 64-bit Plasma host system. Guest was fully updated before the test, including 5.2.6 guest additions.

As part of the test of VirtualBox 5.2.6, I used several apps in the guest, including Klondike in KPatience, running in demo mode. All seemed well.

Then I installed the appropriate updates from this bug, and after a reboot once again ran Klondike in demo mode. This time, movement of the cards was slightly, though noticeably, jerkier than it had been before the updates. Not enough to make things unusable, but enough to notice.

My guess is that this is being caused by the performance hits we were warned about with the Meltdown/Spectre mitigation, made double by being run as a virtual machine, and that there is little that can be done other than obtaining newer, faster hardware than I am using. 

I do not believe it is serious enough to hold back these updates.

advisory added to svn

Keywords: (none) => advisory

Note that I've also added:

ldetect-lst-0.3.7.6-1.mga6
radeon-firmware-20180118-1.mga6.nonfree

rpms to this update.

ldetect-lst adds missing pci ids for in-kernel gpu drivers in 4.14 series kernels so drakxtools can detec/configure them...

radeon-firmware does update some amdgpus for Video Encode/Decode
- amdgpu: update vce firmware for Fiji
- amdgpu: update vcn firmware for raven
- amdgpu: update uvd firmware for polaris asics
- amdgpu: update vce and uvd firmware for Vega10

To recapitulate the latest list of packages to test:

From Comment 0:
---------------
i586:
drm-utils-2.4.89-1.mga6.i586.rpm
libdrm2-2.4.89-1.mga6.i586.rpm
libdrm_amdgpu1-2.4.89-1.mga6.i586.rpm
libdrm-common-2.4.89-1.mga6.i586.rpm
libdrm-devel-2.4.89-1.mga6.i586.rpm
libdrm_intel1-2.4.89-1.mga6.i586.rpm
libdrm_nouveau2-2.4.89-1.mga6.i586.rpm
libdrm_radeon1-2.4.89-1.mga6.i586.rpm
libkms1-2.4.89-1.mga6.i586.rpm

wayland-protocols-devel-1.10-1.mga6.noarch.rpm

x11-driver-video-amdgpu-1.4.0-1.mga6.i586.rpm
x11-driver-video-ati-7.10.0-1.mga6.i586.rpm
x11-driver-video-intel-2.99.917-42.mga6.i586.rpm

x86_64:
drm-utils-2.4.89-1.mga6.x86_64.rpm
lib64drm2-2.4.89-1.mga6.x86_64.rpm
lib64drm_amdgpu1-2.4.89-1.mga6.x86_64.rpm
lib64drm-devel-2.4.89-1.mga6.x86_64.rpm
lib64drm_intel1-2.4.89-1.mga6.x86_64.rpm
lib64drm_nouveau2-2.4.89-1.mga6.x86_64.rpm
lib64drm_radeon1-2.4.89-1.mga6.x86_64.rpm
lib64kms1-2.4.89-1.mga6.x86_64.rpm
libdrm-common-2.4.89-1.mga6.x86_64.rpm

wayland-protocols-devel-1.10-1.mga6.noarch.rpm

x11-driver-video-amdgpu-1.4.0-1.mga6.x86_64.rpm
x11-driver-video-ati-7.10.0-1.mga6.x86_64.rpm
x11-driver-video-intel-2.99.917-42.mga6.x86_64.rpm

From comment 39
---------------
i586:
libd3d1-17.3.2-1.1.mga6.i586.rpm
libd3d1-devel-17.3.2-1.1.mga6.i586.rpm
libdri-drivers-17.3.2-1.1.mga6.i586.rpm
libgbm1-17.3.2-1.1.mga6.i586.rpm
libgbm1-devel-17.3.2-1.1.mga6.i586.rpm
libglapi0-17.3.2-1.1.mga6.i586.rpm
libglapi0-devel-17.3.2-1.1.mga6.i586.rpm
libmesaegl1-17.3.2-1.1.mga6.i586.rpm
libmesaegl1-devel-17.3.2-1.1.mga6.i586.rpm
libmesagl1-17.3.2-1.1.mga6.i586.rpm
libmesagl1-devel-17.3.2-1.1.mga6.i586.rpm
libmesaglesv1_1-17.3.2-1.1.mga6.i586.rpm
libmesaglesv1_1-devel-17.3.2-1.1.mga6.i586.rpm
libmesaglesv2_2-17.3.2-1.1.mga6.i586.rpm
libmesaglesv2_2-devel-17.3.2-1.1.mga6.i586.rpm
libosmesa8-17.3.2-1.1.mga6.i586.rpm
libosmesa-devel-17.3.2-1.1.mga6.i586.rpm
libvdpau-driver-nouveau-17.3.2-1.1.mga6.i586.rpm
libvdpau-driver-r300-17.3.2-1.1.mga6.i586.rpm
libvdpau-driver-r600-17.3.2-1.1.mga6.i586.rpm
libvdpau-driver-radeonsi-17.3.2-1.1.mga6.i586.rpm
libvulkan-devel-17.3.2-1.1.mga6.i586.rpm
libvulkan_intel-17.3.2-1.1.mga6.i586.rpm
libvulkan_radeon-17.3.2-1.1.mga6.i586.rpm
libwayland-egl1-17.3.2-1.1.mga6.i586.rpm
libwayland-egl1-devel-17.3.2-1.1.mga6.i586.rpm
libxatracker2-17.3.2-1.1.mga6.i586.rpm
libxatracker2-devel-17.3.2-1.1.mga6.i586.rpm
mesa-17.3.2-1.1.mga6.i586.rpm
mesa-common-devel-17.3.2-1.1.mga6.i586.rpm

x86_64:
lib64d3d1-17.3.2-1.1.mga6.x86_64.rpm
lib64d3d1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64dri-drivers-17.3.2-1.1.mga6.x86_64.rpm
lib64gbm1-17.3.2-1.1.mga6.x86_64.rpm
lib64gbm1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64glapi0-17.3.2-1.1.mga6.x86_64.rpm
lib64glapi0-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaegl1-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaegl1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64mesagl1-17.3.2-1.1.mga6.x86_64.rpm
lib64mesagl1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaglesv1_1-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaglesv1_1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaglesv2_2-17.3.2-1.1.mga6.x86_64.rpm
lib64mesaglesv2_2-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64osmesa8-17.3.2-1.1.mga6.x86_64.rpm
lib64osmesa-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64vdpau-driver-nouveau-17.3.2-1.1.mga6.x86_64.rpm
lib64vdpau-driver-r300-17.3.2-1.1.mga6.x86_64.rpm
lib64vdpau-driver-r600-17.3.2-1.1.mga6.x86_64.rpm
lib64vdpau-driver-radeonsi-17.3.2-1.1.mga6.x86_64.rpm
lib64vulkan-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64vulkan_intel-17.3.2-1.1.mga6.x86_64.rpm
lib64vulkan_radeon-17.3.2-1.1.mga6.x86_64.rpm
lib64wayland-egl1-17.3.2-1.1.mga6.x86_64.rpm
lib64wayland-egl1-devel-17.3.2-1.1.mga6.x86_64.rpm
lib64xatracker2-17.3.2-1.1.mga6.x86_64.rpm
lib64xatracker2-devel-17.3.2-1.1.mga6.x86_64.rpm
mesa-17.3.2-1.1.mga6.x86_64.rpm
mesa-common-devel-17.3.2-1.1.mga6.x86_64.rpm

From comment 62
---------------
ldetect-lst-0.3.7.6-1.mga6
radeon-firmware-20180118-1.mga6.nonfree

CC: lewyssmith => (none)

Hm. Found out that "Hand of Fate" ( store.steampowered.com/app/266510/Hand_of_Fate/ ) has display errors with my Radeon 7770 (radeon driver) and the testing updates.
Somehow its the only game i found with problems in my list yet. Maybe something with the game.

validating as per QA meeting

CC: (none) => sysadmin-bugs
Whiteboard: (none) => MGA6-64-OK, MGA6-32-OK
Keywords: (none) => validated_update

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2018-0022.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED