Closed Bug 1608705 Opened 5 years ago Closed 4 years ago

[sway] Exits with "Error 71 (Protocol error) dispatching to Wayland display"

Categories

(Core :: Graphics, defect, P2)

74 Branch
Desktop
Linux
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox74 --- wontfix

People

(Reporter: ericdrex, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

Attachments

(3 files)

I previously reported at https://bugzilla.mozilla.org/show_bug.cgi?id=1606751#c2 however with 1606751 fixed I'm still seeing these error 71 exits occasionally.

I'm not sure how to get in a state that leads to an abnormal exit, but I toggled fullscreen several times on a split+stacked layout just before the exit.

❯ firefox-nightly     

(firefox:11296): libnotify-WARNING **: 03:19:07.287: Failed to connect to proxy
Gdk-Message: 05:58:08.174: Unable to load split_h from the cursor theme
Gdk-Message: 07:13:31.549: Unable to load split_v from the cursor theme
Gdk-Message: 08:33:54.449: Error 71 (Protocol error) dispatching to Wayland display.
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Exiting due to channel error.
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Exiting due to channel error.
[GFX1-]: Receive IPC close with reason=AbnormalShutdown
Exiting due to channel error.
Exiting due to channel error.

Hi Martin, do you think this is a potential Fix Failed on 1606751, or does it seem like a new issue?

Flags: needinfo?(stransky)

Not sure. Please run with WAYLAND_DEBUG=1 and attach the log here.
Thanks.

Blocks: wayland-sway
Flags: needinfo?(stransky) → needinfo?(ericdrex)
Attached file firefox-wl-log.txt

I can reproduce the issue reliably with the following steps, on a dual-screen setup :

  1. Launch firefox on screen 1, go to any channel on https://twitch.tv, set it fullscreen
  2. On second screen, launch any website with the terminal (for example firefox https://bugzilla.mozilla.org)
  3. No crash, firefox exits full screen. Go back in fullscreen mode.
  4. Launch firefox https://... again in the terminal. Crashes happen.

Log attached.

Forgot to mention, I have this issue on Firefox 72.0.1 as currently packaged by ArchLinux, not nightly.

Priority: -- → P2
Attached file ff-err71-debug.log

Just saw response, sorry wasn't subbed.

I tried Simon's procedure and got the error 71 exit earlier than they did, on step 2. Thanks!

Attached WAYLAND_DEBUG=1 stdout+stderr

Flags: needinfo?(ericdrex)

I can no longer repro, seems fixed, so closing. Simon, lmk if it's still happening for you.

Flags: needinfo?(sloonz)
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME

I still can reproduce the issue by following the same steps (ArchLinux, firefox-74.0-2, sway-1:1.4-8)

I can also reproduce it with Mozilla build (firefox-74.0.tar.bz2 sha256sum 09d430f7141d0bb753f9f3faed91648196af6a86f30ae4d62f27f6f9e27f2f5f) on a new profile.

Flags: needinfo?(ericdrex)

ok, reopening. I will try to repro some more when I have time.

Status: RESOLVED → UNCONFIRMED
Flags: needinfo?(sloonz)
Resolution: WORKSFORME → ---

Can reproduce this crash on Firefox Nightly only, ver. 80 2020-07-12. Currently using sway version v1.5-rc2-585236f1 (Jul 12 2020, branch 'master').

Sorry for the double mail - it is reproducible when I start Firefox with wayland enabled and start to use the webcam - the permissions prompt works fine, but then it crashes the moment the webcam feed appears.

Same for me, it appeared after this bug was fixed:
Meet.google.com takes 10 seconds until others start hearing my audio

Maybe it is related?

Currently I can't use google meet at all with firefox, and given the remote work situation...

I've attached a wayland-debug log file when opening a WebRTC test site using Firefox 80 2020-07-17. It appears to crash when loading the WebRTC sharing indicator as a window.

From this, I also deduced a workaround - by setting privacy.webrtc.legacyGlobalIndicator to false, thus using the legacy WebRTC indicator, Firefox no longer crashes when you use the webcam/microphone! Huzzah.

wl_display@1.error(xdg_surface@35, 3, "xdg_surface has never been configured")
wl_display@1.error(xdg_surface@88, 4294967295, "Tried to set invalid xdg-surface geometry")

  • looks like the popup is not configured properly.

Can you also reproduce it under Gnome/Mutter or is that Sway only?

I can only reproduce it under Sway - all is fine under either Plasma Wayland or GNOME Wayland.

I can reproduce this under sway by visiting https://mozilla.github.io/webrtc-landing/gum_test.html and attempting to capture camera and microphone. The second I click "allow", I get this exact same crash (running nightly).

(In reply to Dan Shick from comment #17)

I can reproduce this under sway by visiting https://mozilla.github.io/webrtc-landing/gum_test.html and attempting to capture camera and microphone. The second I click "allow", I get this exact same crash (running nightly).

Whoops, should have read the whole thread. Seems others have identified the same reproduction steps. Kevin Liu's workaround works for me as well.

Can you please test latest nightly under Wayland? A new popup handling code landed there.
Thanks.

Sorry, forgot to mention that this was fixed (at least for me) a few releases ago.

Downloaded nightly (2021-06-04), and I cannot reproduce it here either.

(In reply to Simon Lipp from comment #20)

Sorry, forgot to mention that this was fixed (at least for me) a few releases ago.

Downloaded nightly (2021-06-04), and I cannot reproduce it here either.

Thanks for getting back!

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: