gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon()
Bug #1934457 reported by
errors.ubuntu.com bug bridge
This bug report is a duplicate of:
Bug #1934458: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon().
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Shell |
Unknown
|
Unknown
|
|||
gnome-shell (Ubuntu) |
Fix Committed
|
Undecided
|
Unassigned |
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.38.4-
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:g_type_check_instance_is_fundamentally_a:g_object_unref:on_window_icon_changed:g_closure_invoke:signal_emit_unlocked_R + gnome-shell crashed with SIGSEGV in + g_type_check_instance_is_fundamentally_a() from g_object_unref() from + on_window_icon_changed() from g_closure_invoke() from + signal_emit_unlocked_R() |
summary: |
gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from - signal_emit_unlocked_R() + signal_emit_unlocked_R() from g_signal_emit_valist() from + g_signal_emit() from g_object_dispatch_properties_changed() from + g_object_notify_queue_thaw() from g_object_thaw_notify() from + g_object_thaw_notify() from meta_window_update_icon_now() from + idle_update_icon |
summary: |
gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from - g_object_thaw_notify() from meta_window_update_icon_now() from - idle_update_icon + meta_window_update_icon_now() from idle_update_icon() |
Changed in gnome-shell (Ubuntu): | |
status: | New → Confirmed |
tags: | added: jammy |
Changed in gnome-shell (Ubuntu): | |
status: | Confirmed → Fix Committed |
tags: | added: fixed-in-42 fixed-upstream |
tags: |
added: fixed-in-42.0 removed: fixed-in-42 |
tags: | removed: hirsute |
tags: | removed: kylin-21.04 |
To post a comment you must log in.
I would prefer to keep this bug separate.
Even if the fix is the same as bug 1934458, the call stacks are different. Both in Launchpad and upstream where each have their own separate reports.
Until a fix is released it would cause less confusion keeping different looking crashes separate.