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 779764 - Gdk-WARNING **: Error 71 (Protocol error) dispatching to Wayland display
Gdk-WARNING **: Error 71 (Protocol error) dispatching to Wayland display
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Wayland
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2017-03-08 19:43 UTC by pierpaolo.vittorini
Modified: 2018-05-02 18:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description pierpaolo.vittorini 2017-03-08 19:43:08 UTC
Evolution closes unexpectedly when typing a contact in the mailer window. After some debugging, the only relevant warning/error I could notice is the following:

(evolution:6149): Gdk-WARNING **: Error 71 (Protocol error) dispatching to Wayland display.
[Thread 0x7fff209df700 (LWP 6219) exited]
[Thread 0x7fff3bfff700 (LWP 6234) exited]
[Thread 0x7fffb6b35700 (LWP 6233) exited]
[Thread 0x7fff211e0700 (LWP 6218) exited]
[Thread 0x7fff38d47700 (LWP 6217) exited]
[Thread 0x7fffb7d73700 (LWP 6213) exited]
[Thread 0x7fffb4e27700 (LWP 6212) exited]
[Thread 0x7fff3a1c7700 (LWP 6198) exited]
[Thread 0x7fff9d7fa700 (LWP 6182) exited]
[Thread 0x7fff399c6700 (LWP 6199) exited]
[Thread 0x7fffb582f700 (LWP 6211) exited]
[Thread 0x7fffb6334700 (LWP 6244) exited]
[Thread 0x7fff9dffb700 (LWP 6179) exited]
[Thread 0x7fff9e7fc700 (LWP 6178) exited]
[Thread 0x7fff9effd700 (LWP 6177) exited]
[Thread 0x7fffcedfa700 (LWP 6162) exited]
[Thread 0x7fffcf7fe700 (LWP 6161) exited]
[Thread 0x7fffcffff700 (LWP 6160) exited]
[Thread 0x7fffd4f2e700 (LWP 6159) exited]
[Thread 0x7fffdc6ed700 (LWP 6158) exited]
[Thread 0x7ffff7ed8ac0 (LWP 6149) exited]
[Inferior 1 (process 6149) exited with code 01]

Similar issues are reported, e.g., for Libreoffice/Firefox, and looks like the problem is related to Wayland. Actually, I can confirm that this issue is happening after my upgrade to Fedora 25, which uses Wayland by default.
Comment 1 Milan Crha 2017-03-09 09:45:57 UTC
Thanks for a bug report. These things are heavily out of evolution hands, it uses the higher level API of gtk+. I'm moving this to gtk+.
Comment 2 Olivier Fourdan 2017-03-10 14:53:19 UTC
Firefox doesn't Wayland native, I am not sure about OpenOffice. But evolution does.

Can you please capture the the logs produced with WAYLAND_DEBUG=1 while the issue occurs?

That should tell what protocol error actually occurs...
Comment 3 pierpaolo.vittorini 2017-04-12 08:19:16 UTC
(In reply to Olivier Fourdan from comment #2)
> Firefox doesn't Wayland native, I am not sure about OpenOffice. But
> evolution does.
> 
> Can you please capture the the logs produced with WAYLAND_DEBUG=1 while the
> issue occurs?
> 
> That should tell what protocol error actually occurs...

Sorry for the late reply... This should be the relevant part:

[3559309,828]  -> wl_shm@5.create_pool(new id wl_shm_pool@50, fd 58, 41972416)
[3559309,857]  -> wl_shm_pool@50.create_buffer(new id wl_buffer@39, 0, 9574, 1096, 38296, 0)
[3559379,122]  -> wl_surface@59.attach(wl_buffer@39, 0, 0)
[3559379,159]  -> wl_surface@59.set_buffer_scale(2)
[3559379,180]  -> wl_surface@59.damage(0, 0, 4787, 548)
[3559379,199]  -> wl_compositor@4.create_region(new id wl_region@63)
[3559379,211]  -> wl_region@63.add(7, 0, 4773, 7)
[3559379,234]  -> wl_region@63.add(0, 7, 4787, 541)
[3559379,244]  -> wl_surface@59.set_opaque_region(wl_region@63)
[3559379,250]  -> wl_region@63.destroy()
[3559379,255]  -> wl_surface@59.set_input_region(nil)
[3559379,279]  -> wl_surface@59.frame(new id wl_callback@65)
[3559379,297]  -> wl_surface@59.commit()
[3559379,891]  -> wl_surface@51.attach(wl_buffer@56, 0, 0)
[3559379,907]  -> wl_surface@51.set_buffer_scale(2)
[3559379,915]  -> wl_surface@51.damage(715, 426, 13, 366)
[3559379,930]  -> zxdg_toplevel_v6@53.set_min_size(702, 449)
[3559379,945]  -> zxdg_toplevel_v6@53.set_max_size(0, 0)
[3559379,968]  -> zxdg_surface_v6@52.set_window_geometry(26, 23, 702, 815)
[3559380,003]  -> wl_surface@51.frame(new id wl_callback@32)
[3559380,010]  -> wl_surface@51.commit()
[3559380,018]  -> wl_subsurface@66.set_desync()
[3559380,554]  -> wl_surface@35.attach(wl_buffer@42, 0, 0)
[3559380,574]  -> wl_surface@35.set_buffer_scale(2)
[3559380,582]  -> wl_surface@35.damage(1586, 148, 13, 679)
[3559380,600]  -> zxdg_toplevel_v6@37.set_min_size(888, 439)
[3559380,612]  -> zxdg_toplevel_v6@37.set_max_size(0, 0)
[3559380,622]  -> zxdg_surface_v6@36.set_window_geometry(0, 0, 1600, 872)
[3559380,658]  -> wl_surface@35.frame(new id wl_callback@61)
[3559380,667]  -> wl_surface@35.commit()
[3559381,284] wl_display@1.delete_id(63)
[3559381,303] wl_display@1.error(wl_surface@59, 2, "Failed to create a texture for surface 59")

(evolution:6933): Gdk-WARNING **: Error 71 (Protocol error) dispatching to Wayland display.
Comment 4 Olivier Fourdan 2017-04-18 07:06:05 UTC
It looks like the surface size exceeds the hardware supported texture size.

What gives "glxinfo -l | grep GL_MAX_TEXTURE_SIZE" on that hardware (and which hardware is that)?
Comment 5 GNOME Infrastructure Team 2018-05-02 18:17:05 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/783.