2022-04-22 07:05:10 |
Daniel van Vugt |
bug |
|
|
added bug |
2022-04-22 07:05:20 |
Daniel van Vugt |
bug watch added |
|
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5330 |
|
2022-04-22 07:05:20 |
Daniel van Vugt |
bug task added |
|
gnome-shell |
|
2022-04-22 07:05:52 |
Daniel van Vugt |
tags |
|
jammy |
|
2022-04-22 07:05:56 |
Daniel van Vugt |
gnome-shell (Ubuntu): importance |
Undecided |
High |
|
2022-04-22 07:05:59 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
New |
Confirmed |
|
2022-04-22 07:09:42 |
Daniel van Vugt |
summary |
gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from windowManager.js:1543:9 |
gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9] |
|
2022-05-09 01:42:22 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
Confirmed |
In Progress |
|
2022-05-12 01:20:00 |
Daniel van Vugt |
gnome-shell (Ubuntu): status |
In Progress |
Fix Committed |
|
2022-05-12 01:20:11 |
Daniel van Vugt |
tags |
jammy |
fixed-in-43 fixed-upstream jammy |
|
2022-05-12 01:20:21 |
Daniel van Vugt |
affects |
gnome-shell (Ubuntu) |
mutter (Ubuntu) |
|
2022-05-17 06:34:12 |
Daniel van Vugt |
description |
gnome-shell crashes with SIGSEGV just after logging:
gnome-shell[3117]: JS ERROR: TypeError: window is null
_destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16
Examples:
https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206
https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206
Tracking in:
https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470
^^^ this is the second most common gnome-shell crash on errors.ubuntu.com |
gnome-shell crashes with SIGSEGV just after logging:
gnome-shell[3117]: JS ERROR: TypeError: window is null
_destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16
Examples:
https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206
https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206
https://errors.ubuntu.com/oops/aa5bf652-d517-11ec-9aa3-fa163e55efd0
Tracking in:
https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470
^^^ this is the second most common gnome-shell crash on errors.ubuntu.com |
|
2022-06-01 12:11:00 |
Jeremy Bícha |
nominated for series |
|
Ubuntu Jammy |
|
2022-06-01 12:11:00 |
Jeremy Bícha |
bug task added |
|
mutter (Ubuntu Jammy) |
|
2022-06-01 12:11:07 |
Jeremy Bícha |
mutter (Ubuntu Jammy): status |
New |
Triaged |
|
2022-06-01 12:11:10 |
Jeremy Bícha |
mutter (Ubuntu Jammy): importance |
Undecided |
High |
|
2022-06-02 06:45:39 |
Launchpad Janitor |
mutter (Ubuntu): status |
Fix Committed |
Fix Released |
|
2022-06-07 19:06:05 |
Jeremy Bícha |
mutter (Ubuntu Jammy): status |
Triaged |
In Progress |
|
2022-06-07 19:08:56 |
Jeremy Bícha |
description |
gnome-shell crashes with SIGSEGV just after logging:
gnome-shell[3117]: JS ERROR: TypeError: window is null
_destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16
Examples:
https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206
https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206
https://errors.ubuntu.com/oops/aa5bf652-d517-11ec-9aa3-fa163e55efd0
Tracking in:
https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470
^^^ this is the second most common gnome-shell crash on errors.ubuntu.com |
Impact
======
GNOME Shell crashes when it's restarted on Xorg. (There is no option to restart GNOME Shell on Wayland.)
Test Case
=========
Install the update
On the login screen, select your name.
Click the gear button in the lower right and choose Ubuntu on Xorg
Enter your password to finish logging in.
Open the file browser.
Press Alt-F2.
In the dialog, enter 'r'
GNOME Shell should restart without a crash message. Your file browser window should remain open.
What Could Go Wrong
===================
See the master bug for this update LP: #1976381
More Details
============
gnome-shell crashes with SIGSEGV just after logging:
gnome-shell[3117]: JS ERROR: TypeError: window is null
_destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9
_initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16
Examples:
https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206
https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206
https://errors.ubuntu.com/oops/aa5bf652-d517-11ec-9aa3-fa163e55efd0
Tracking in:
https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470
^^^ this is the second most common gnome-shell crash on errors.ubuntu.com |
|
2022-06-08 05:02:40 |
Daniel van Vugt |
tags |
fixed-in-43 fixed-upstream jammy |
fixed-in-42.2 fixed-in-43 fixed-upstream jammy |
|
2022-06-10 16:58:08 |
Steve Langasek |
mutter (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
2022-06-10 16:58:09 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
2022-06-10 16:58:11 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
2022-06-10 16:58:14 |
Steve Langasek |
tags |
fixed-in-42.2 fixed-in-43 fixed-upstream jammy |
fixed-in-42.2 fixed-in-43 fixed-upstream jammy verification-needed verification-needed-jammy |
|
2022-06-17 15:57:43 |
Jeremy Bícha |
tags |
fixed-in-42.2 fixed-in-43 fixed-upstream jammy verification-needed verification-needed-jammy |
fixed-in-42.2 fixed-in-43 fixed-upstream jammy verification-done verification-done-jammy |
|
2022-06-20 14:39:46 |
Launchpad Janitor |
mutter (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
2022-06-20 14:40:06 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
2022-06-21 15:59:06 |
Jay S. |
bug |
|
|
added subscriber Jay S. |
2022-10-30 15:37:10 |
Bug Watch Updater |
gnome-shell: status |
Unknown |
Fix Released |
|