Assigning to the registered maintainer.

Assignee: bugsquad => tmb
CC: (none) => marja11

Similar (probably the same) issue here, also shortly after the Mesa upgrade (to mesa-18.0.0-0.rc3.2.mga7.x86_64, with not much else upgraded at that same time, IIRC).

In my case, I haven't even logged out.

Trying to launch plasmashell from a Konsole window results in Plasma's panel trying to appear a couple of times, then plasmashell crashing, with these last messages:

QSGSimpleMaterialShader does not implement 'uniform highp mat4 qt_Matrix;' in its vertex shader
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: Application 'plasmashell' crashing...


This is using the Nouveau driver on a "NVIDIA Corporation GF119 [GeForce GT 610]". Other OpenGL-using programs like mpv or the PPSSPP emulator (heavy 3D use) work just fine. KWin's effects like transparency or Present Windows work fine.


In addition to the faults reported by the OP, launching Spectacle (the screen capture program), setting it to "Rectangular region" and making it take a new screenshot, also results in an all-white screen, until either ESC is pressed to cancel, or a region is selected blindly (which is then captured correctly).

CC: (none) => jan-bugs

Jüri, can you tell us what the output is of:

  lspcidrake -v | grep Card

and please attach your 

  /etc/X11/xorg.conf


also, can you run (as root)

  journalctl -b -N

where you replace N by the number of boots ago that you saw this bug.

 (or just run:
  journalctl -b -1
  journalctl -b -2
  journalctl -b -3
  etc, until you find the correct logs.)

Then please run the command again, with "> log.txt" appended to it, so e.g.:

  journalctl -b -2 > log.txt

and attach log.txt to this bug report.

I can confirm the Plasma crash with the QSGSimpleMaterialShader error message (the one in the dev mailing list). My graphics are Intel (Sandy Bridge) manually set to use DRI3. I can also add that krunner still works for launching applications, but it's shown as an empty grey panel

CC: (none) => ita84

Created attachment 9950 [details]
Packages updated just before this issue appeared.

I had been using  mesa-18.0.0-0.rc3.1.mga7 for a week however it's rebuild may have done something.
My video is Intel not Nvidia but the symptoms are exactly as the OP except that I have yet to try downgrading mesa.
I have tried the earlier kernel that was also updated in the same batch but there is no change.

CC: (none) => zen25000

I re-built mesa-17.3.3 and bumped rel to 3 locally in iurt.
I installed it as follows:

[root@localhost /]# urpmi --search-media extra --downgrade mesa
The following packages have to be removed for others to be upgraded:
lib64dri-drivers-18.0.0-0.rc3.2.mga7.x86_64
 (due to unsatisfied mesa == 18.0.0)
lib64mesagl1-18.0.0-0.rc3.2.mga7.x86_64
 (due to unsatisfied lib64dri-drivers >= 18.0.0-0.rc3.2.mga7)
lib64mesagl1-devel-18.0.0-0.rc3.2.mga7.x86_64
 (in order to install lib64mesagl1-devel-17.3.3-3.mga7.x86_64)
mesa-18.0.0-0.rc3.2.mga7.x86_64
 (due to unsatisfied lib64mesagl1 == 18.0.0-0.rc3.2.mga7) (y/N) y
To satisfy dependencies, the following packages are going to be installed:
  Package                        Version      Release       Arch    
(medium "Extra Release")
  lib64dri-drivers               17.3.3       3.mga7        x86_64  
  lib64mesagl1                   17.3.3       3.mga7        x86_64  
  lib64mesagl1-devel             17.3.3       3.mga7        x86_64  
  mesa                           17.3.3       3.mga7        x86_64  
824KB of disk space will be freed.
6.7MB of packages will be retrieved.
Proceed with the installation of the 4 packages? (Y/n) y
-----snip-----

Rebooted and just like the OP all is now working again. \o/

For anyone who is not trying to debug this, but just wants to fix a system by downgrading mesa to this version then my rebuild of mesa-17.3.3-3 for x86_64 can be installed as follows:
(Note ONLY use for mesa downgrade and remove repo afterwards!)

su
urpmi.addmedia extra "http://mtf.duckdns.org/pub/linux/barjac/distrib/cauldron/x86_64/media/extra/release/"
urpmi --search-media extra --downgrade mesa
urpmi.removemedia extra

For i586 just replace 'x86_64' with 'i586' in URL above.

Maybe add mesa to skip.list temporarily to stop it happening again.

Created attachment 9953 [details]
journalctl log just after installing updates and reboot

(In reply to Marja van Waes from comment #3)
>   lspcidrake -v | grep Card

Card:Intel 810 and later: Intel Corporation|Skylake GT2 [HD Graphics 520] [DISPLAY_VGA] (vendor:8086 device:1916 subv:17aa subd:504a) (rev: 07)

> and please attach your /etc/X11/xorg.conf

See the attachments. The result is the same if I use either intel or modesetting driver.

>   journalctl -b -2 > log.txt

See attached log. Just installed today all the updates once more with the same results. Again downgraded 8 installed mesa packages to get sddm and plasma desktop back.

Created attachment 9954 [details]
xorg.conf (intel driver)

Created attachment 9955 [details]
when booted with modesetting driver - attached file in /etc/X11/xorg.conf.d

(In reply to Jüri Ivask from comment #7)
> Created attachment 9953 [details]
> journalctl log just after installing updates and reboot

Yeah, you have the QSGSimpleMaterialShader error, too, so it looks like we won't need to ask some other commenters to file a separate bug report.

> veebr 06 09:48:25 tpkrom plasmashell[1100]: QSGSimpleMaterialShader does not
> implement 'uniform highp mat4 qt_Matrix;' in its vertex shader

(In reply to Barry Jackson from comment #6)

> 
> For anyone who is not trying to debug this, but just wants to fix a system
> by downgrading mesa to this version then my rebuild of mesa-17.3.3-3 for
> x86_64 can be installed as follows:
> (Note ONLY use for mesa downgrade and remove repo afterwards!)
> 
> su
> urpmi.addmedia extra
> "http://mtf.duckdns.org/pub/linux/barjac/distrib/cauldron/x86_64/media/extra/
> release/"
> urpmi --search-media extra --downgrade mesa
> urpmi.removemedia extra
> 
> For i586 just replace 'x86_64' with 'i586' in URL above.
> 
> Maybe add mesa to skip.list temporarily to stop it happening again.

Thanks, Barry :-)

For DNF there's no skip list (like for URPMI), but one can add 
"--exclude *mesa*" to the "dnf upgrade" command

(In reply to Barry Jackson from comment #5)
> Created attachment 9950 [details]
> Packages updated just before this issue appeared.
> 
> I had been using  mesa-18.0.0-0.rc3.1.mga7 for a week however it's rebuild
> may have done something.

Thx for mentioning that.

CC'ing tv, who pushed the "good" mesa-18. I'll try to ping the 18.0.0-0.rc3.2 pusher on IRC, because afaik he currently doesn't want to CC'ed in bug reports against packages he doesn't maintain.

Keywords: NEEDINFO => (none)
Summary: mesa-18.0.0-0.rc3.2.mga7 update causes sddm and plasma desktop to fail => mesa-18.0.0-0.rc3.2.mga7 update causes sddm and plasma desktop to fail, downgrading the mesa packages to v. 17.3.3 fixes them
Source RPM: mesa-18.0.0-0.rc3.2.mga7.src.rpm => mesa-18.0.0-0.rc3.2.mga7, sddm,
CC: (none) => thierry.vignaud

Created attachment 9957 [details]
updates that cause the sddm problem with previous mesa-18.0.0-0.rc3.1.mga7

Using the _previous_ mesa-18.0.0-0.rc3.1.mga7 packages, after running some updates from a not fully up to date local mirror, while excluding/skipping all of *mesa*, sddm doesn't show anything but an arrow. Blindly typing my password, like Jüri did, makes me end up in a working Xfce.

Attaching the terminal output of the update (so the list of updated packages is in it). I don't run Plasma5 atm, and didn't see the QSGSimpleMaterialShader error on reboot, only hit the problem with invisible sddm with visible cursor. However, a lot of KDE libs were updated/installed. 

I'll update (while still excluding latest mesa release) from a fully updated mirror asap.

sddm seems to be very unstable...
(sddm in mga6 updates_testing got borked by a qt update...)

Has anyone of you tried to rebuild sddm locally with the new mesa ? does it help ?

(In reply to Thomas Backlund from comment #13)
> sddm seems to be very unstable...
> (sddm in mga6 updates_testing got borked by a qt update...)
> 
> Has anyone of you tried to rebuild sddm locally with the new mesa ? does it
> help ?

Yes, I just did that, and no, it does not make any difference at all.

Besides what's in the title, Spectacle has issues, as I said in https://bugs.mageia.org/show_bug.cgi?id=22510#c2 and now I've seen that the KCM's in System Settings that are based on QML, also fail to display anything at all, or display very little things.

"Desktop Effects" for instance is all white. "Window Decorations" is mostly white, except for the part where the "demo" of the Plastik theme is supposed to be, the words "Plastik" are the only thing visible :p

So no, it doesn't look like a SDDM rebuild issue.

Cheers!

Problem was solved for me by deleting the ~/.cache/qtshadercache directory for my user and rebooting (I suppose relogin would work as well), as mentioned on this OpenSuSE mailing list

https://lists.opensuse.org/opensuse-factory/2018-02/msg00256.html

(In reply to Davide Nifosi from comment #16)
> Problem was solved for me by deleting the ~/.cache/qtshadercache directory
> for my user and rebooting (I suppose relogin would work as well), as
> mentioned on this OpenSuSE mailing list
> 
> https://lists.opensuse.org/opensuse-factory/2018-02/msg00256.html

Confirmed - Plasma desktop starts now OK.
SDDM still displays grey screen - fortunately I can log in blindly (I'm using sddm breeze theme and only one user here).

With fresh mesa-18.0.0-0.rc4.1.mga7 update also sddm now works OK here :)
Thanks Thomas!

(In reply to Jüri Ivask from comment #18)
> With fresh mesa-18.0.0-0.rc4.1.mga7 update also sddm now works OK here :)
> Thanks Thomas!

that's great!

I had just noticed, when comparing the packages that barjac had installed when hitting this issue with mine, that I had forgotten to exclude 

lib64dri-drivers
lib64gbm1*
lib64glapi0
lib64wayland-egl1*
lib64xatracker2-18.0.0-0.rc3.2.mga7.x86_64
 
when skipping/excluding the *mesa* packages so they'd stay on v. 18.0.0-0.rc3.1.mga7

:-(((

So it looks like mesa was the culprit, after all!

Confirmed, plasmashell starts here once again after upgrading Mesa to 18.0 rc4 =)

Thanks!!

Closing as fixed then

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

Oh, and just for the record, the other issues I found due to this, with Spectacle and the QML-based KCM's are also *GONE*, BOOM, DESTROYED =)

Cheers!!

Informational, for possible future reference:

https://bugreports.qt.io/browse/QTBUG-66348

(since this might bite again)