gnome-shell crashed with SIGSEGV in stack_do_window_deletions() from stack_ensure_sorted() from get_default_focus_window() from meta_stack_get_default_focus_window() from focus_ancestor_or_top_window()
Bug #1831578 reported by
errors.ubuntu.com bug bridge
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mutter |
Fix Released
|
Unknown
|
|||
| gnome-shell (Ubuntu) |
Fix Released
|
Low
|
Marco Trevisan (Treviño) | ||
| mutter (Ubuntu) |
Fix Released
|
Low
|
Marco Trevisan (Treviño) | ||
Bug Description
The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.2-1ubuntu1, the problem page at https:/
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://
| summary: |
- /usr/bin/gnome- - shell:11:stack_do_window_deletions:stack_ensure_sorted:get_default_focus_window:meta_stack_get_default_focus_window:focus_ancestor_or_top_window + gnome-shell crashed with SIGSEGV in stack_do_window_deletions() from + stack_ensure_sorted() from get_default_focus_window() from + meta_stack_get_default_focus_window() from + focus_ancestor_or_top_window() |
| Changed in gnome-shell (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → In Progress |
| assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
| Changed in mutter (Ubuntu): | |
| status: | New → In Progress |
| importance: | Undecided → Low |
| assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
| Changed in mutter: | |
| status: | Unknown → New |
| Changed in mutter: | |
| status: | New → Fix Released |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #1 |
| tags: | removed: disco |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #2 |
| Changed in gnome-shell (Ubuntu): | |
| status: | In Progress → Fix Released |
| Changed in mutter (Ubuntu): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
See also bug 1834583