Activity log for bug #1748450

Date Who What changed Old value New value Message
2018-02-09 14:55:42 Donald L Walters bug added bug
2018-02-09 15:18:22 Apport retracing service bug added subscriber Crash bug triagers for Ubuntu packages
2018-02-09 15:18:24 Apport retracing service attachment added Stacktrace.txt https://bugs.launchpad.net/bugs/1748450/+attachment/5051817/+files/Stacktrace.txt
2018-02-09 15:18:25 Apport retracing service attachment added StacktraceSource.txt https://bugs.launchpad.net/bugs/1748450/+attachment/5051818/+files/StacktraceSource.txt
2018-02-09 15:18:26 Apport retracing service attachment added ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1748450/+attachment/5051819/+files/ThreadStacktrace.txt
2018-02-09 15:18:28 Apport retracing service attachment removed CoreDump.gz https://bugs.launchpad.net/bugs/1748450/+attachment/5051798/+files/CoreDump.gz
2018-02-09 15:18:29 Apport retracing service gnome-shell (Ubuntu): importance Undecided Medium
2018-02-09 15:18:35 Apport retracing service tags amd64 apport-crash bionic need-amd64-retrace third-party-packages amd64 apport-crash bionic third-party-packages
2018-02-09 21:13:21 Launchpad Janitor gnome-shell (Ubuntu): status New Confirmed
2018-02-12 02:37:47 Daniel van Vugt information type Private Public
2018-02-12 02:40:21 Daniel van Vugt summary gnome-shell crashed with signal 5 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from <bug 1505409>
2018-02-12 02:41:33 Daniel van Vugt description unknown 18.04 beta after initial startup and trying to run software update app. Don Walters Hilbert Space Technical Arts (an L^2 sub-space of Banach L^p Space, where p= ~5/3)) w9dki / w9gty ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron:  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop:  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0  _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups:
2018-02-12 02:41:37 Daniel van Vugt gnome-shell (Ubuntu): importance Medium High
2018-02-12 02:41:41 Daniel van Vugt gnome-shell (Ubuntu): status Confirmed Triaged
2018-02-12 02:42:23 Daniel van Vugt description *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron:  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop:  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0  _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron:  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop:  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0  _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups:
2018-02-14 03:37:06 Apport retracing service tags amd64 apport-crash bionic third-party-packages amd64 apport-crash bionic bugpattern-needed third-party-packages
2018-02-15 16:43:52 Apport retracing service tags amd64 apport-crash bionic bugpattern-needed third-party-packages amd64 apport-crash artful bionic bugpattern-needed third-party-packages
2018-03-09 07:04:22 Karma Dorje bug added subscriber Karma Dorje
2018-03-26 12:44:37 Jean-Baptiste Lallement tags amd64 apport-crash artful bionic bugpattern-needed third-party-packages amd64 apport-crash artful bionic bugpattern-needed rls-bb-incoming third-party-packages
2018-03-26 12:58:57 Carl Stock bug added subscriber Carl Stock
2018-03-26 15:03:16 bernhard bug added subscriber bernhard
2018-03-27 14:46:37 Sebastien Bacher tags amd64 apport-crash artful bionic bugpattern-needed rls-bb-incoming third-party-packages amd64 apport-crash artful bionic bugpattern-needed rls-bb-notfixing third-party-packages
2018-03-27 15:06:49 Ben-Ja bug added subscriber Ben-Ja
2018-03-30 10:24:31 Jean-Baptiste Lallement tags amd64 apport-crash artful bionic bugpattern-needed rls-bb-notfixing third-party-packages amd64 apport-crash artful bionic bugpattern-needed rls-bb-incoming rls-bb-notfixing third-party-packages
2018-04-03 07:03:10 Paul Schweinzer bug added subscriber Paul Schweinzer
2018-04-03 09:04:12 Dmitriy Geels bug added subscriber Dmitriy Geels
2018-04-03 09:21:01 Paul Schweinzer removed subscriber Paul Schweinzer
2018-04-03 13:10:24 Hamberfim bug added subscriber Hamberfim
2018-04-03 13:52:01 Jean-Baptiste Lallement tags amd64 apport-crash artful bionic bugpattern-needed rls-bb-incoming rls-bb-notfixing third-party-packages amd64 apport-crash artful bionic bugpattern-needed rls-bb-incoming third-party-packages
2018-04-03 14:04:27 Paul White bug added subscriber Paul White
2018-04-03 18:13:46 bolek bug added subscriber bolek
2018-04-10 14:09:15 Will Cooke nominated for series Ubuntu Bionic
2018-04-10 14:09:15 Will Cooke bug task added gnome-shell (Ubuntu Bionic)
2018-04-10 14:09:26 Will Cooke gnome-shell (Ubuntu Bionic): assignee Jean-Baptiste Lallement (jibel)
2018-04-10 14:09:39 Will Cooke tags amd64 apport-crash artful bionic bugpattern-needed rls-bb-incoming third-party-packages amd64 apport-crash artful bionic bugpattern-needed third-party-packages
2018-04-16 03:57:20 pdelteil bug added subscriber pdelteil
2018-04-16 03:57:26 pdelteil removed subscriber pdelteil
2018-04-16 03:57:32 pdelteil bug added subscriber pdelteil
2018-04-16 13:01:42 Mahmudul Haque bug added subscriber Mahmudul Haque
2018-04-19 17:39:18 j1n3l0 bug added subscriber j1n3l0
2018-04-19 17:40:14 j1n3l0 removed subscriber j1n3l0
2018-04-24 04:51:17 Daniel van Vugt description *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron:  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop:  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0  _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: [Impact] * Xwayland is failing frequently (not crashing), which triggers a crash in gnome-shell because gnome-shell doesn't know how to survive without Xwayland. * The frequent gnome-shell crashes create frequent problem reports and annoying dialogs for users, after they log in to an apparently working gnome-shell. * This affects Xorg sessions too, because the gdm login screen itself is a Wayland session. And Xorg users will see the problem dialog after they have logged into a Xorg session. * The fix simply converts the crash into a silent exit (as decided by Gnome upstream). This avoids the mountain of crash reports and annoying error dialogs at least. It does not fix the root causes that remain in Xwayland, but this is considered acceptable because there really isn't a bug in gnome-shell here other than it doesn't know how to survive without a connection to Xwayland. * For users of Xorg sessions, like bionic default, this is a full fix as Xorg users will never get an Xwayland instance after logging in. And hence no Xwayland bugs. [Test Case] * Just install bionic, use it lightly and reboot a few times. * Observe crash files are left in /var/crash and problem report dialogs after logging in. [Regression Potential] Medium. The fix does not really change the structure of the existing error handling, only changes it from a core dump into a silent exit. For Xorg users this should be invisible as the affected login screen restarts automatically. [Other Info] This is a whole class of gnome-shell crash which includes bug 1505409, bug 1748450 and bug 1556601. All three should be considered the same crash for the sake of this SRU. --------- *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron:  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop:  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0  _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups:
2018-04-24 04:55:58 Daniel van Vugt description [Impact] * Xwayland is failing frequently (not crashing), which triggers a crash in gnome-shell because gnome-shell doesn't know how to survive without Xwayland. * The frequent gnome-shell crashes create frequent problem reports and annoying dialogs for users, after they log in to an apparently working gnome-shell. * This affects Xorg sessions too, because the gdm login screen itself is a Wayland session. And Xorg users will see the problem dialog after they have logged into a Xorg session. * The fix simply converts the crash into a silent exit (as decided by Gnome upstream). This avoids the mountain of crash reports and annoying error dialogs at least. It does not fix the root causes that remain in Xwayland, but this is considered acceptable because there really isn't a bug in gnome-shell here other than it doesn't know how to survive without a connection to Xwayland. * For users of Xorg sessions, like bionic default, this is a full fix as Xorg users will never get an Xwayland instance after logging in. And hence no Xwayland bugs. [Test Case] * Just install bionic, use it lightly and reboot a few times. * Observe crash files are left in /var/crash and problem report dialogs after logging in. [Regression Potential] Medium. The fix does not really change the structure of the existing error handling, only changes it from a core dump into a silent exit. For Xorg users this should be invisible as the affected login screen restarts automatically. [Other Info] This is a whole class of gnome-shell crash which includes bug 1505409, bug 1748450 and bug 1556601. All three should be considered the same crash for the sake of this SRU. --------- *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron:  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop:  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0  _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: [Impact] * Xwayland is failing frequently (not crashing), which triggers a crash in gnome-shell because gnome-shell doesn't know how to survive without Xwayland. * The frequent gnome-shell crashes create frequent problem reports and annoying dialogs for users, after they log in to an apparently working gnome-shell. * This affects Xorg sessions too, because the gdm login screen itself is a Wayland session. And Xorg users will see the problem dialog after they have logged into a Xorg session. * The fix simply converts the crash into a silent exit (as decided by Gnome upstream). This avoids the mountain of crash reports and annoying error dialogs at least. It does not fix the root causes that remain in Xwayland, but this is considered acceptable because there really isn't a bug in gnome-shell here other than it doesn't know how to survive without a connection to Xwayland. * For users of Xorg sessions, like bionic default, this is a full fix as Xorg users will never get an Xwayland instance after logging in. And hence no Xwayland bugs. [Test Case] * Just install bionic, use it lightly and reboot a few times. * Observe crash files are left in /var/crash and problem report dialogs after logging in. [Regression Potential] Medium. The fix does not really change the structure of the existing error handling, only changes it from a core dump into a silent exit. For Xorg users this should be invisible as the affected login screen restarts automatically. [Other Info] This is a whole class of gnome-shell crash which includes bug 1505409, bug 1748450 and bug 1556601. All three should be considered the same crash for the sake of this SRU. Just don't mark them as duplicates of each other because they are all still collecting duplicates of their own. --------- *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron:  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop:  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0  _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups:
2018-04-24 05:08:31 Daniel van Vugt description [Impact] * Xwayland is failing frequently (not crashing), which triggers a crash in gnome-shell because gnome-shell doesn't know how to survive without Xwayland. * The frequent gnome-shell crashes create frequent problem reports and annoying dialogs for users, after they log in to an apparently working gnome-shell. * This affects Xorg sessions too, because the gdm login screen itself is a Wayland session. And Xorg users will see the problem dialog after they have logged into a Xorg session. * The fix simply converts the crash into a silent exit (as decided by Gnome upstream). This avoids the mountain of crash reports and annoying error dialogs at least. It does not fix the root causes that remain in Xwayland, but this is considered acceptable because there really isn't a bug in gnome-shell here other than it doesn't know how to survive without a connection to Xwayland. * For users of Xorg sessions, like bionic default, this is a full fix as Xorg users will never get an Xwayland instance after logging in. And hence no Xwayland bugs. [Test Case] * Just install bionic, use it lightly and reboot a few times. * Observe crash files are left in /var/crash and problem report dialogs after logging in. [Regression Potential] Medium. The fix does not really change the structure of the existing error handling, only changes it from a core dump into a silent exit. For Xorg users this should be invisible as the affected login screen restarts automatically. [Other Info] This is a whole class of gnome-shell crash which includes bug 1505409, bug 1748450 and bug 1556601. All three should be considered the same crash for the sake of this SRU. Just don't mark them as duplicates of each other because they are all still collecting duplicates of their own. --------- *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron:  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop:  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0  _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: [Impact] * Xwayland is failing frequently (not crashing), which triggers a crash in gnome-shell because gnome-shell doesn't know how to survive after Xwayland has reset itself. * The frequent gnome-shell crashes create frequent problem reports and annoying dialogs for users, after they log in to an apparently working gnome-shell. * This affects Xorg sessions too, because the gdm login screen itself is a Wayland session. And Xorg users will see the problem dialog after they have logged into a Xorg session. * The fix simply converts the crash into a silent exit (as decided by Gnome upstream). This avoids the mountain of crash reports and annoying error dialogs at least. It does not fix the root causes that remain in Xwayland, but this is considered acceptable because there really isn't a bug in gnome-shell here other than it doesn't know how to survive without a connection to Xwayland. * For users of Xorg sessions, like bionic default, this is a full fix as Xorg users will never get an Xwayland instance after logging in. And hence no Xwayland bugs. [Test Case] * Just install bionic, use it lightly and reboot a few times. * Observe crash files are left in /var/crash and problem report dialogs after logging in. [Regression Potential] Medium. The fix does not really change the structure of the existing error handling, only changes it from a core dump into a silent exit. For Xorg users this should be invisible as the affected login screen restarts automatically. [Other Info] This is a whole class of gnome-shell crash which includes bug 1505409, bug 1748450 and bug 1556601. All three should be considered the same crash for the sake of this SRU. Just don't mark them as duplicates of each other because they are all still collecting duplicates of their own. --------- *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron:  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop:  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0  _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups:
2018-04-24 05:10:01 Daniel van Vugt description [Impact] * Xwayland is failing frequently (not crashing), which triggers a crash in gnome-shell because gnome-shell doesn't know how to survive after Xwayland has reset itself. * The frequent gnome-shell crashes create frequent problem reports and annoying dialogs for users, after they log in to an apparently working gnome-shell. * This affects Xorg sessions too, because the gdm login screen itself is a Wayland session. And Xorg users will see the problem dialog after they have logged into a Xorg session. * The fix simply converts the crash into a silent exit (as decided by Gnome upstream). This avoids the mountain of crash reports and annoying error dialogs at least. It does not fix the root causes that remain in Xwayland, but this is considered acceptable because there really isn't a bug in gnome-shell here other than it doesn't know how to survive without a connection to Xwayland. * For users of Xorg sessions, like bionic default, this is a full fix as Xorg users will never get an Xwayland instance after logging in. And hence no Xwayland bugs. [Test Case] * Just install bionic, use it lightly and reboot a few times. * Observe crash files are left in /var/crash and problem report dialogs after logging in. [Regression Potential] Medium. The fix does not really change the structure of the existing error handling, only changes it from a core dump into a silent exit. For Xorg users this should be invisible as the affected login screen restarts automatically. [Other Info] This is a whole class of gnome-shell crash which includes bug 1505409, bug 1748450 and bug 1556601. All three should be considered the same crash for the sake of this SRU. Just don't mark them as duplicates of each other because they are all still collecting duplicates of their own. --------- *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron:  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop:  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0  _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups: [Impact] * Xwayland is failing frequently (not crashing), which triggers a crash in gnome-shell because gnome-shell doesn't know how to survive after Xwayland has reset itself. * The frequent gnome-shell crashes create frequent problem reports and annoying dialogs for users, after they log in to an apparently working gnome-shell. * This affects Xorg sessions too, because the gdm login screen itself is a Wayland session. And Xorg users will see the problem dialog after they have logged into a Xorg session. * The fix simply converts the crash into a silent exit (as decided by Gnome upstream). This avoids the mountain of crash reports and annoying error dialogs at least. It does not fix the root causes that remain in Xwayland, but this is considered acceptable because there really isn't a bug in gnome-shell here other than it doesn't know how to survive without a connection to Xwayland. * For users of Xorg sessions, like bionic default, this is a full fix as Xorg users will never get an Xwayland instance after logging in. And hence the Xwayland bugs are irrelevant. [Test Case] * Just install bionic, use it lightly and reboot a few times. * Observe crash files are left in /var/crash and problem report dialogs after logging in. [Regression Potential] Medium. The fix does not really change the structure of the existing error handling, only changes it from a core dump into a silent exit. For Xorg users this should be invisible as the affected login screen restarts automatically. [Other Info] This is a whole class of gnome-shell crash which includes bug 1505409, bug 1748450 and bug 1556601. All three should be considered the same crash for the sake of this SRU. Just don't mark them as duplicates of each other because they are all still collecting duplicates of their own. --------- *** This is a duplicate of bug 1505409, but is being kept separate so as to automatically collect duplicate reports since the stacktrace signature has changed recently. Any resolution and discussion should occur in bug 1505409. *** See also: https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13 Uname: Linux 4.13.0-33-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Feb 8 23:50:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-21 (690 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/gnome-shell ProcEnviron:  PATH=(custom, no user)  XDG_RUNTIME_DIR=<set>  LANG=en_US.UTF-8  SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop:  () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0  _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago) UserGroups:
2018-04-24 06:42:13 Daniel van Vugt gnome-shell (Ubuntu Bionic): assignee Jean-Baptiste Lallement (jibel)
2018-04-26 01:23:05 Daniel van Vugt gnome-shell (Ubuntu Bionic): status Triaged Fix Released
2018-04-26 01:47:12 Daniel van Vugt bug task added mutter (Ubuntu)
2018-04-26 01:47:24 Daniel van Vugt mutter (Ubuntu Bionic): status New Fix Released
2018-04-26 01:47:28 Daniel van Vugt mutter (Ubuntu Bionic): importance Undecided High
2018-04-26 01:47:34 Daniel van Vugt gnome-shell (Ubuntu Bionic): status Fix Released Invalid
2018-04-26 07:44:02 lnx bug added subscriber lnx
2018-05-25 06:29:32 Apport retracing service tags amd64 apport-crash artful bionic bugpattern-needed third-party-packages amd64 apport-crash artful bionic bugpattern-needed cosmic third-party-packages
2018-05-25 18:46:29 René Froh bug added subscriber René Froh
2018-05-26 16:51:03 Marcos Nascimento bug added subscriber Marcos Nascimento
2019-01-04 11:01:39 Marcos Nascimento removed subscriber Marcos Nascimento
2019-01-04 11:57:18 Paul White removed subscriber Paul White
2019-01-06 03:08:57 Ryan Obrock bug added subscriber Ryan Obrock
2019-01-07 04:32:01 Salvatore LaMendola bug added subscriber Salvatore LaMendola
2019-01-07 08:17:08 Eugene bug added subscriber Eugene
2019-01-07 08:17:14 Eugene removed subscriber Eugene
2019-01-07 08:17:54 Eugene bug added subscriber Eugene
2019-01-07 08:18:38 Eugene removed subscriber Eugene
2019-01-07 16:17:59 René Froh removed subscriber René Froh
2019-01-07 16:25:01 Henry Primeau bug added subscriber Henry Primeau
2019-01-07 16:25:05 Henry Primeau removed subscriber Henry Primeau
2019-01-07 16:25:09 Henry Primeau bug added subscriber Henry Primeau
2019-01-07 16:25:49 Henry Primeau removed subscriber Henry Primeau
2019-01-07 16:25:54 Henry Primeau bug added subscriber Henry Primeau
2019-01-08 04:19:06 nvsoar bug added subscriber nvsoar
2019-01-08 04:19:23 nvsoar removed subscriber nvsoar
2019-01-08 04:19:40 nvsoar bug added subscriber nvsoar