Bug#956121: Fwd: Bug#956121: Blank screen on 2nd display using wayland

[Pierre Cheynier]

Le mar. 7 avr. 2020 à 21:27, Simon McVittie <smcv at debian.org> a écrit :

Sorry for being that late answering!

>
> Is this reproducible by upgrading/downgrading only libmutter-5-0 and
> closely-related packages, without altering anything else?

Yes absolutely, knowing that upgrading libmutter-5-0 also upgrade, by
dependency:
gir1.2-mutter-5 libmutter-5-0
(i.e. the only one not up-to-date here being mutter package itself).

> Are you able to test this with mutter and gnome-shell 3.36.x from
> experimental? We're close to uploading those to unstable.

Not right now, since I almost suceeded having an almost-operational
working environment :), but I can provide you some feedback soon (let
say 1 week?)

> You appear to have a dual-GPU system. Is the NVIDIA device completely
> disabled, or are they both active via some sort of dual-GPU arrangement
> like Bumblebee?
>
> Do you have the proprietary NVIDIA drivers installed? (I'm guessing you
> don't, because reportbug would have told us about the non-free module.)

Yes exactly, nvidia chip not-used, no proprietary, full nouveau. These
setups are terrible.

> systemd journal entries during GNOME Shell startup and around the time
> you reproduce a bug are usually useful, particularly for hardware-related
> things like this.

First, just to be clear on the symptoms, my second screen is fully
white, but I'm still able to move my mouse pointer and see it on this
area ..

Let me tell you that it's a mess if we consider all graphics +
gnome-shell + plugins related logs :)

All the logs seems to say that everything is living its life normaly
(gnome-* related logs), except on the kernel aspects, I noticed that I
observe this during a "working" boot:
```
avril 10 11:47:39 dell-m4700 kernel: DMAR: DRHD: handling fault status reg 2
avril 10 11:47:39 dell-m4700 kernel: DMAR: [DMA Read] Request device
[00:1f.2] PASID ffffffff fault addr c9827000 [fault reason 06] PTE
Read access is not set
```

But when having this non-working setup, I additionaly got this each
5s, following main screen blink, probably some kind of
reinitialization (let say it's a side-effect?):
```
avril 10 11:46:25 dell-m4700 kernel: dmar_fault: 191660 callbacks suppressed
avril 10 11:46:25 dell-m4700 kernel: DMAR: DRHD: handling fault status reg 3
avril 10 11:46:25 dell-m4700 kernel: DMAR: [DMA Read] Request device
[01:00.0] PASID ffffffff fault addr fc01e000 [fault reason 06] PTE
Read access is not set
avril 10 11:46:25 dell-m4700 kernel: DMAR: DRHD: handling fault status reg 3
avril 10 11:46:25 dell-m4700 kernel: DMAR: [DMA Read] Request device
[01:00.0] PASID ffffffff fault addr fc045000 [fault reason 06] PTE
Read access is not set
avril 10 11:46:25 dell-m4700 kernel: DMAR: DRHD: handling fault status reg 3
avril 10 11:46:25 dell-m4700 kernel: DMAR: [DMA Read] Request device
[01:00.0] PASID ffffffff fault addr fc06a000 [fault reason 06] PTE
Read access is not set
avril 10 11:46:25 dell-m4700 kernel: DMAR: DRHD: handling fault status reg 3
```

After each of those crashes, I also see a
```
avril 10 11:46:26 dell-m4700 systemd[1782]: Started Application
launched by gnome-shell.
avril 10 11:46:27 dell-m4700 systemd[1782]:
gnome-launched-gnome-background-panel.desktop-2515.scope: Succeeded.
```

Except from that gnome-shell and friends seems OK-ish.

Anything to add more verbosity on the mutter specifics?

> (Or during mutter startup and around the time you reproduce a bug, if
> you are genuinely using the standalone mutter executable - which is not
> really recommended, but should in principle work.)

I don't, here I stick on debian defaults with gnome.