https://bugzilla.kernel.org/show_bug.cgi?id=209275 --- Comment #6 from Monthero Ronald (rhmcruiser@xxxxxxxxx) --- (In reply to Dennis Wagelaar from comment #4) > This bug no longer occurs under kernel 5.8.9-101.fc31.x86_64 - closing. Ah good to know issue is resolved with upgrade to newer kernel. (Probbaly the issue was within the gnome-shell where the above stack was indicating a use after free sort of condition in the gnome userspace code causing core dumps. ep 15 08:23:46 styx gnome-shell[67420]: #9 55a8b19fc420 i resource:///org/gnome/gjs/modules/overrides/Gio.js:169 (7fba6c0d3e50 @ 39) Sep 15 08:23:46 styx gnome-shell[67420]: == Stack trace for context 0x55a8ac63e3a0 == Sep 15 08:23:46 styx gnome-shell[67420]: #0 55a8b19fc6d8 i /usr/share/gnome-shell/extensions/gamemode@xxxxxxxxxxxxxxxxxxxx/extension.js:231 (7fba10824820 @ 287) Sep 15 08:23:46 styx gnome-shell[67420]: #1 7ffe62146c90 b self-hosted:977 (7fba45130a60 @ 413) Sep 15 08:23:46 styx gnome-shell[67420]: #2 7ffe62146d70 b resource:///org/gnome/gjs/modules/signals.js:135 (7fba6c0c6040 @ 376) Sep 15 08:23:46 styx journal[67420]: Object St.Icon (0x55a8ad298110), 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. -- You are receiving this mail because: You are watching the assignee of the bug.
