Whatsapp For Linux: Error 71 (Protocol error) dispatching to Wayland display

English Applications
1

I have installed whatsapp-for-linux package from repo-oss. When I launch it it crashes with the following error message in console.

<13>Jul 31 20:02:47 whatsapp-for-linux[3403]: Gdk-Message: 20:02:47.878: Error 71 (Protocol error) dispatching to Wayland display.

I have tried a fix from Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display but it didn’t work out.

2

I use zapzap, is better on flatpak or repo-oss

1 Like
3

@mirko You have a dual graphics (hybrid) setup with an Intel GPU, if so ensure libvulkan_intel package is removed.

4

No such package installed. I use RTX 3070, and yes I have an intel cpu.

5

@mirko It’s Vulkan related from memory/testing. I set the Mesa device to my Nvidia GPU, so try starting the app with MESA_VK_DEVICE_SELECT="xxxx:yyyy" <your app>

Where xxxx:nnnn is the Chip ID info from inxi -Gxxz

For example, I have a RTX4000 so would be;

Device-2: NVIDIA TU104GL [Quadro RTX 4000] vendor: Hewlett-Packard
    driver: nvidia v: 575.64.05 arch: Turing pcie: speed: 2.5 GT/s lanes: 16
    ports: active: none empty: DP-4, DP-5, DP-6, Unknown-1 bus-ID: 07:00.0
    chip-ID: 10de:1eb1

MESA_VK_DEVICE_SELECT="10de:1eb1"

I set this globally in a /etc/environment file if inline doesn’t work…

6

@malcolmlewis I have tried inline MESA_VK_DEVICE_SELECT and the output is the same

7

Then add the environment file reboot and test

8

No, it didn’t work

9

@mirko Can you show the output from inxi -GSaz then.

10

https://paste.opensuse.org/pastes/b2607e2f289e

11

You need to remove nomodeset and add nvidia_drm.modeset=1 to the boot options, you have the Intel GPU disabled in the BIOS?

12

I did that on purpose when I was installing the system, using grub e option, it didn’t detect the GPU and installer didn’t show up. Is it okay to change using yast boot loader?

13

I have changed it, but it still shows the same error

14

@mirko Can you show the latest inxi -GSaz output.

15

@malcolmlewis openSUSE Paste

16

@mirko it could be SELinux… if you set to permissive, does this help?
https://en.opensuse.org/Portal:SELinux/Troubleshooting

I could be Plasma related (I don’t run this DE)…

17

Unfortunately no

18

@mirko then I’ve exhausted my notes on fixes related to using GNOME, plus I’ve not seen that issue for some time.

Might need to create a bug report…

19

I do not see any fix there (at least, I do not see anything that looks like a description of a fix). It is always better to simply tell us what you did instead of referring to an external resource that can be interpreted differently.

Anyway - as you have hybrid graphics system, you may be hitting Making sure you're not a bot! and disabling Vulkan could work around it.