Bug#927852: Info received (Bug#927852: Acknowledgement (xwayland: GNOME Shell crashes after connecting ThinkPad Thunderbolt 3 Dock Gen 2 via Thunderbolt to a Lenovo T470))
Am Freitag, den 10.05.2019, 12:13 +0200 schrieb Michel Dänzer: > On 2019-05-07 7:13 a.m., - wrote: > > This morning GNOME Shell crashed again, see attached logs. > > Connecting/disconecting the Thunderbolt Gen2 Dock was working fine > > for > > 1-2 weeks, now it crashed again. > > > > Hope the logs help to narrow down the issue finally. > > It looks like it could be (related to) > https://gitlab.freedesktop.org/xorg/xserver/issues/11 , which is said > to > be fixed with Xwayland 1.20.4. Have you tried that? > This evening I have installed Xwayland 1.20.4 and xserver-common 1.20.4 from unstable. I will report back if the issue is solved and how the system behaves. Thanks for the hint. Christian Höffer
Bug#927852: Info received (Bug#927852: Acknowledgement (xwayland: GNOME Shell crashes after connecting ThinkPad Thunderbolt 3 Dock Gen 2 via Thunderbolt to a Lenovo T470))
On 2019-05-07 7:13 a.m., - wrote: > This morning GNOME Shell crashed again, see attached logs. > Connecting/disconecting the Thunderbolt Gen2 Dock was working fine for > 1-2 weeks, now it crashed again. > > Hope the logs help to narrow down the issue finally. It looks like it could be (related to) https://gitlab.freedesktop.org/xorg/xserver/issues/11 , which is said to be fixed with Xwayland 1.20.4. Have you tried that? -- Earthling Michel Dänzer | https://www.amd.com Libre software enthusiast | Mesa and X developer
Bug#927852: Info received (Bug#927852: Acknowledgement (xwayland: GNOME Shell crashes after connecting ThinkPad Thunderbolt 3 Dock Gen 2 via Thunderbolt to a Lenovo T470))
On 2019-04-25 5:06 p.m., - wrote: > > So what would be your suggestion on how to proceed? Are there any > promising paths I could follow to narrow down the issues? You should probably file a separate report against the chromium package about the chromium crash. -- Earthling Michel Dänzer | https://www.amd.com Libre software enthusiast | Mesa and X developer
Bug#927852: Info received (Bug#927852: Acknowledgement (xwayland: GNOME Shell crashes after connecting ThinkPad Thunderbolt 3 Dock Gen 2 via Thunderbolt to a Lenovo T470))
> > > > I installed auditd and added the following rule: > > > > -a always,exit -F arch=b64 -S kill > > > > Now there are more detailed log entries in journalctl. > > Do they help to narrow down who is terminating the processes? I am > > not > > able to interpret them, therefore I am asking. > > Looks like that was a red herring, in the form of GDM terminating its > own GNOME session for the login screen while another VT is active. > So what would be your suggestion on how to proceed? Are there any promising paths I could follow to narrow down the issues? Or is there anything interesting/critical errors in the log files I have posted which could help? best regards Christian Höffer
Bug#927852: Info received (Bug#927852: Acknowledgement (xwayland: GNOME Shell crashes after connecting ThinkPad Thunderbolt 3 Dock Gen 2 via Thunderbolt to a Lenovo T470))
On 2019-04-25 1:26 p.m., - wrote: >> >> Signal 15 is SIGTERM, so this looks like something terminates a lot >> (most / all?) of processes in your session. Maybe Xwayland is another >> victim of that. There is no evidence here of anything going wrong in >> Xwayland itself. >> > > I installed auditd and added the following rule: > > -a always,exit -F arch=b64 -S kill > > Now there are more detailed log entries in journalctl. > Do they help to narrow down who is terminating the processes? I am not > able to interpret them, therefore I am asking. Looks like that was a red herring, in the form of GDM terminating its own GNOME session for the login screen while another VT is active. -- Earthling Michel Dänzer | https://www.amd.com Libre software enthusiast | Mesa and X developer
Bug#927852: Info received (Bug#927852: Acknowledgement (xwayland: GNOME Shell crashes after connecting ThinkPad Thunderbolt 3 Dock Gen 2 via Thunderbolt to a Lenovo T470))
On 2019-04-25 9:16 a.m., - wrote: > This morning I applied all available updates, did a reboot, waited ~10 > sec and then connected the dock. Monitor arrangement was fine and GNOME > Shell did not crash. > But this time Chromium was not responding correctly (e.g. right click > to open a folder from the bookmarks in incognito window) and then > finally just crashed and closed. > > There are two interesting parts in the log I think. > > First one is after bolt started > > " > ... > Apr 25 08:46:11 debian-t470 boltd[1708]: bolt 0.7 starting up. > Apr 25 08:46:11 debian-t470 boltd[1708]: config: loading user config > Apr 25 08:46:11 debian-t470 boltd[1708]: bouncer: initializing polkit > Apr 25 08:46:11 debian-t470 boltd[1708]: udev: initializing udev > ... > Apr 25 08:46:16 debian-t470 gnome-session-binary[837]: WARNING: > Application 'org.gnome.SettingsDaemon.A11ySettings.desktop' killed by > signal 15 > [...] Signal 15 is SIGTERM, so this looks like something terminates a lot (most / all?) of processes in your session. Maybe Xwayland is another victim of that. There is no evidence here of anything going wrong in Xwayland itself. -- Earthling Michel Dänzer | https://www.amd.com Libre software enthusiast | Mesa and X developer
