After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 772449 - Gnome Shell freeze on Dual Monitor
Gnome Shell freeze on Dual Monitor
Status: RESOLVED DUPLICATE of bug 774557
Product: gnome-shell
Classification: Core
Component: general
3.21.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2016-10-05 12:28 UTC by laverdone
Modified: 2016-12-05 18:57 UTC
See Also:
GNOME target: ---
GNOME version: 3.21/3.22


Attachments
journalctl -b (1.05 MB, text/plain)
2016-10-06 04:56 UTC, laverdone
Details
journalctl -b without shell extension (284.37 KB, text/plain)
2016-10-07 06:54 UTC, laverdone
Details

Description laverdone 2016-10-05 12:28:27 UTC
Gnome Shell Version 3.22 freeze on wayland session when two monitor as attached, the system respond to ping and accessible via ssh but shell and kayboard not responding:

lspci:
00:00.0 Host bridge: NVIDIA Corporation MCP89 HOST Bridge (rev a1)
00:00.1 RAM memory: NVIDIA Corporation MCP89 Memory Controller (rev a1)
00:01.0 RAM memory: NVIDIA Corporation Device 0d6d (rev a1)
00:01.1 RAM memory: NVIDIA Corporation Device 0d6e (rev a1)
00:01.2 RAM memory: NVIDIA Corporation Device 0d6f (rev a1)
00:01.3 RAM memory: NVIDIA Corporation Device 0d70 (rev a1)
00:02.0 RAM memory: NVIDIA Corporation Device 0d71 (rev a1)
00:02.1 RAM memory: NVIDIA Corporation Device 0d72 (rev a1)
00:03.0 ISA bridge: NVIDIA Corporation MCP89 LPC Bridge (rev a2)
00:03.1 RAM memory: NVIDIA Corporation MCP89 Memory Controller (rev a1)
00:03.2 SMBus: NVIDIA Corporation MCP89 SMBus (rev a1)
00:03.3 RAM memory: NVIDIA Corporation MCP89 Memory Controller (rev a1)
00:03.4 Co-processor: NVIDIA Corporation MCP89 Co-Processor (rev a1)
00:04.0 USB controller: NVIDIA Corporation MCP89 OHCI USB 1.1 Controller (rev a1)
00:04.1 USB controller: NVIDIA Corporation MCP89 EHCI USB 2.0 Controller (rev a2)
00:06.0 USB controller: NVIDIA Corporation MCP89 OHCI USB 1.1 Controller (rev a1)
00:06.1 USB controller: NVIDIA Corporation MCP89 EHCI USB 2.0 Controller (rev a2)
00:08.0 Audio device: NVIDIA Corporation MCP89 High Definition Audio (rev a2)
00:0a.0 SATA controller: NVIDIA Corporation MCP89 SATA Controller (AHCI mode) (rev a2)
00:0b.0 RAM memory: NVIDIA Corporation Device 0d75 (rev a1)
00:0e.0 PCI bridge: NVIDIA Corporation Device 0d9a (rev a1)
00:15.0 PCI bridge: NVIDIA Corporation Device 0d9b (rev a1)
00:16.0 PCI bridge: NVIDIA Corporation Device 0d9b (rev a1)
00:17.0 PCI bridge: NVIDIA Corporation MCP89 PCI Express Bridge (rev a1)
01:00.0 FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller (rev 08)
02:00.0 Network controller: Broadcom Limited BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
03:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5764M Gigabit Ethernet PCIe (rev 10)
04:00.0 VGA compatible controller: NVIDIA Corporation MCP89 [GeForce 320M] (rev a2)

uname -a

Linux bellerofonte 4.8.0-1.fc25.x86_64 #1 SMP Mon Oct 3 15:58:29 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Comment 1 Rui Matos 2016-10-05 12:36:13 UTC
(In reply to laverdone from comment #0)
> Gnome Shell Version 3.22 freeze on wayland session when two monitor as
> attached, the system respond to ping and accessible via ssh but shell and
> kayboard not responding:

If that's the case, please capture the output of "journalctl -b" after this happens and attach it here.
Comment 2 laverdone 2016-10-06 04:56:12 UTC
Created attachment 337035 [details]
journalctl -b

this is the journalctl -b after gnome-shell freeze on dual monitor
Comment 3 Rui Matos 2016-10-06 11:54:46 UTC
You seem to be using a few gnome-shell extensions. Can you try disabling them and check if this still happens?
Comment 4 laverdone 2016-10-07 06:54:52 UTC
Created attachment 337125 [details]
journalctl -b without shell extension
Comment 5 laverdone 2016-10-07 06:57:03 UTC
Without shell extensions I have the same problem
Comment 6 laverdone 2016-10-12 20:05:06 UTC
Any news for this?
Comment 7 Rui Matos 2016-10-13 10:11:32 UTC
I don't see anything evidently wrong. Are there any specific steps on your part that lead to the freeze? Does it not happen with a single monitor? Does the mouse pointer still move when it freezes?
Comment 8 laverdone 2016-10-13 12:37:55 UTC
i'm logged in to Gnome Session Wayland with single Monitor and everything working ok, then attach second monitor and the session still working for a few minute, after about 1 minute the mouse freeze, the keyboard not respond but Caps Lock led still work, the shell freeze all windows on all monitor.
 I tried to connect Monitor before start Gnome Session Wayland but i have the same problem.

I tried with Weston Compositor with two Monitor and all working fine.

This error is not present on gnome shell 3.20.
Comment 9 Guillaume Ayoub 2016-10-21 11:35:12 UTC
I can confirm this bug with a different hardware (Intel haswell). Nothing in the logs, SSH working, freeze only when there's more than 1 monitor. The freeze sometimes happens after a minute, sometimes after a couple of hours. I'm trying to find reliable steps to reproduce.

I don't remember having this problem with 3.20 (but I only used it a few hours with Wayland). I use a rotated screen, don't know if it's related.
Comment 10 Guillaume Ayoub 2016-11-09 12:15:34 UTC
The problem appears with 4 different computers here, 2 distributions (Arch and Gentoo), Intel and AMD GPUs, 3 screens each (rotated or not).
Comment 11 Guillaume Ayoub 2016-12-05 13:03:56 UTC
How could we provide more info on this bug?

SSH is working, I can kill the gnome session and everything works fine after that, but I lose my session of course. There's nothing interesting in the logs, and I really don't know how I can know what's going on.

I can use my computer for days on Wayland with one monitor, no problem. No problem either with X and 3 screens.

I've no idea about how to reproduce the bug in a reliable way :/. It sometimes happen after a couple of minutes, sometimes after hours. Everything is frozen on the screen, the mouse and the keyboard don't work (including the ctrl-alt-F1/7 shortcuts to reach a TTY).
Comment 12 Rui Matos 2016-12-05 18:57:23 UTC

*** This bug has been marked as a duplicate of bug 774557 ***