gnome-shell freezes on notification arrival (fixed upstream)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Shell |
Fix Released
|
Unknown
|
|||
gnome-shell (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Medium
|
Marco Trevisan (Treviño) | ||
Disco |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[ Description ]
Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded.
[ Test case ]
Install gsconnect extension in gnome-shell:
https:/
- Start Up system
- first Notification from connected device
- Hangs for about 20 sec
+ This should not happen
[ Regression potential ]
Persistent state is not kept, although the patch is living upstream for many cycles already, so it's pretty safe.
-----
I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known.
https:/
https:/
In my case it happens only with the notifications of gsconnect and maybe android studio.
I have reproduced the problem in gsconnect in case it helps.
https:/
the error is:
lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs
Ubuntu 18.04
gnome-shell
Version: 3.28.4-
Changed in gnome-shell: | |
status: | Unknown → Fix Released |
tags: | added: rls-bb-incoming |
tags: |
added: rls-bb-notfixing removed: rls-bb-incoming |
Changed in gnome-shell (Ubuntu Bionic): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
description: | updated |
Thanks for the bug report.
If you would like the bug fixed in 18.04 then please click the above link "Nominate for series".