[Fix available] Window manager xfwm 4.13.0 broken after last mesa update

[pcspecialistpdx]

mesa 19.0.2 did not fix the issue. I've been tempted to try mesa 19.2 but have not got around to it yet.

https://launchpad.net/~oibaf/+archive/u ... ter=bionic

[karlchen]

I had never mentioned any Launchpad PPA in this context, but the official mesa 19.0.2 -1ubuntu1.1~18.04.2, available through the official Ubuntu "bionic" repositories.

Launchpad PPA is not the same as Launchpad bug report. Repeating what had been posted only 3 days ago.

According to this Launchpad bug report, Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04, the underlying bug should have been fixed in a recent update for Mesa 19.0.2.

This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.2

---------------
mesa (19.0.2-1ubuntu1.1~18.04.2) bionic; urgency=medium

* i965-revert-enabling-softpin.diff: Don't enable softpin, causes
issues on 32bit installs. (LP: #1836721)

-- Timo Aaltonen <email address hidden> Thu, 18 Jul 2019 18:44:14 +0300
Changed in mesa (Ubuntu Bionic):
status: Fix Committed → Fix Released

[pcspecialistpdx]

I had never mentioned any Launchpad PPA in this context, but the official mesa 19.0.2 -1ubuntu1.1~18.04.2, available through the official Ubuntu "bionic" repositories.

mesa 19.0.2 -1ubuntu1.1~18.04.2 doesn't fix anything

[pcspecialistpdx]

I finally got around to trying mesa 19.2 from https://launchpad.net/~oibaf/+archive/u ... ter=bionic

xfwm 4.13.4 works fine with it (compositing on) and I suspect 4.13.0 would too.

(as with xfwm 4.13.0, xfwm 4.13.4 does not work with mesa 19.0.2)

Just to be clear, mesa 19.2 works with xfwm 4.13.x with composting on, mesa 19.0.2 does not.

I also checked for screen tearing and as I expected, there is none.

[MrEen]

Hi pcspecialistpdx.

Would you mind posting the output from running inxi -G in the terminal? I'm suspecting the PPA gave you LLVM9 and I'd just like to see if that's the case.

[pcspecialistpdx]

Hi pcspecialistpdx.

Would you mind posting the output from running inxi -G in the terminal? I'm suspecting the PPA gave you LLVM9 and I'd just like to see if that's the case.

Code: Select all

Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
  driver: i915 v: kernel 
  Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1200~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel Haswell Desktop 
  v: 4.5 Mesa 19.2.0-devel (git-1f8b653 2019-08-05 bionic-oibaf-ppa)

[MrEen]

Code: Select all

Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
  driver: i915 v: kernel 
  Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1200~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel Haswell Desktop 
  v: 4.5 Mesa 19.2.0-devel (git-1f8b653 2019-08-05 bionic-oibaf-ppa)

Thanks. It didn't show what I was hoping to see. I don't know if inxi -Gxx would help or not.

[karlchen]

Hi, MrEen.

Below is an example illustrating the output of inxi -G vs inxi -Gxxx.

Code: Select all

karl@unimatrix0:~$ inxi -G
Graphics:  Device-1: NVIDIA C79 [ION] driver: nouveau v: kernel 
           Display: x11 server: X.Org 1.19.6 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1280x1024~60Hz 
           OpenGL: renderer: NVAC v: 3.3 Mesa 19.0.2 
karl@unimatrix0:~$ inxi -Gxxx
Graphics:  Device-1: NVIDIA C79 [ION] vendor: ZOTAC driver: nouveau v: kernel bus ID: 03:00.0 chip ID: 10de:087d 
           Display: x11 server: X.Org 1.19.6 driver: nouveau unloaded: fbdev,modesetting,vesa compositor: compton 
           v: 0.1~beta2+20150922 resolution: 1280x1024~60Hz 
           OpenGL: renderer: NVAC v: 3.3 Mesa 19.0.2 direct render: Yes 

I am aware that you are interested in pcspecialistpdx's output, not in mine. Maybe he can be persuaded to post the inxi -Gxxx output.

Cheers,
Karl

[pcspecialistpdx]

Thanks. It didn't show what I was hoping to see. I don't know if inxi -Gxx would help or not.

Code: Select all

Graphics:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
  vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0412 
  Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1200~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel Haswell Desktop 
  v: 4.5 Mesa 19.2.0-devel (git-1f8b653 2019-08-05 bionic-oibaf-ppa) 
  compat-v: 3.0 direct render: Yes 

[MrEen]

Thank you both!

The output still didn't have what I was hoping to see (neither of either!)

On some systems, there's a piece that can look like this from mine:

Code: Select all

GLX Renderer: AMD ARUBA (DRM 2.50.0 / 4.15.0-50-generic, LLVM 6.0.0)

I believe the main issue stems from the way mesa uses LLVM 8. In that PPA, there are both LLVM 8 and LLVM 9, so I was wondering if the newer mesa worked because it was using the higher LLVM. But I'm not smart enough to figure out how to find out what it's using in this case.

Thanks for trying to assist.

[gm10]

On some systems, there's a piece that can look like this from mine:

Code: Select all

GLX Renderer: AMD ARUBA (DRM 2.50.0 / 4.15.0-50-generic, LLVM 6.0.0)

I believe the main issue stems from the way mesa uses LLVM 8. In that PPA, there are both LLVM 8 and LLVM 9, so I was wondering if the newer mesa worked because it was using the higher LLVM. But I'm not smart enough to figure out how to find out what it's using in this case.

LLVM is the fallback software rasterizer though, and as far as the Mesa guys communicated regarding the issue in this thread it was a problem with Intel's DRI Mesa drivers.

[MrEen]

Gotcha. Knew I shoulda stayed out of it!

[linxmintq]

Again the same thing happens with Linux Mint 19.2 Tina in xfce.

[pcspecialistpdx]

Again the same thing happens with Linux Mint 19.2 Tina in xfce.

No, it doesn't, Linux Mint 19.2 Tina ships with xfwm4 4.12.5 and has no upgrade to 4.13. xfwm4 4.12.5 plays nicely with all mesa versions.

That said, I have got Linux Mint 19.2 Tina working fine with xfwm4 4.13.4 (from https://launchpad.net/~xubuntu-dev/+arc ... ter=bionic) and mesa 19.2 (from https://launchpad.net/~oibaf/+archive/u ... ter=bionic)

[pcspecialistpdx]

In case anyone is wondering if the problem still exists with the latest mesa update ( 19.0.8 ), the answer is yes.