Am Mittwoch, den 24.04.2019, 17:05 +0200 schrieb Michel Dänzer: > On 2019-04-24 4:25 p.m., - wrote: > > This seems to be a serious bug, because now GNOME Shell also has > > crashed when disconnecting the thunderbolt device. > > Does it still happen with xwayland 2:1.20.4-1 from sid? If yes: > > > > I also added a journalctl log. > > > > [...] > > > > Apr 24 16:08:24 debian-t470 org.gnome.Shell.desktop[1387]: (EE) 2: > > /usr/bin/Xwayland (present_extension_init+0xcd2) [0x560ec4ee0542] > > Apr 24 16:08:24 debian-t470 org.gnome.Shell.desktop[1387]: (EE) 3: > > /usr/bin/Xwayland (present_extension_init+0xf14) [0x560ec4ee0b04] > > Apr 24 16:08:24 debian-t470 org.gnome.Shell.desktop[1387]: (EE) 4: > > /usr/bin/Xwayland (glamor_egl_fd_from_pixmap+0x637) > > [0x560ec4e22a67] > FWIW, these symbols are probably bogus, as glamor_egl_fd_from_pixmap > in > Xwayland is a stub which just returns -1, no way it ends up calling > present_* functions. > >
Interestingly, I was not able to break it anymore, even with the version in testing. I have tried it again at home and at work (both sides same dock, but each site different monitor setup). After a reboot and then multiple times connecting and disconneting the dock, I was not able to reproduce it and crash GNOME Shell. I also opened the programms I used while it crashed, even with the same websites open. Also going to suspend with the dock connected, disconnect the dock and wake the laptop up (or vice versa, disconnect -> suspend -> connect the dock -> resume laptop) do not break GNOME Shell at the moment. Maybe it was a rare combination of circumstances which does not occur often. I will try to reproduce it and continue using suspend and the docks and hopefully I can trigger it again and sent another logfile to narrow it down. In the logs where GNOME Shell crashed, around the crash there are a lot of chromium errors: Apr 24 07:13:40 debian-t470 chromium.desktop[1357]: [4373:4373:0424/071340.656718:ERROR:zygote_communication_linux.cc(276)] Failed to send GetTerminationStatus message to zygote and Apr 24 16:08:22 debian-t470 chromium.desktop[1387]: [2268:2268:0424/160822.454621:ERROR:gl_surface_presentation_helper.cc(2 37)] GetVSyncParametersIfAvailable() failed! Might this trigger crashing (in combination with the thunderbolt authentification process (boltd) and adding new displays etc.) by interupting or keeping a ressource busy so that they freeze/crash? (Just not sure, if Chromium still uses xWayland or nowadays Wayland natively.) best regards Christian Höffer
