> Does it really tell you anything useful which of them was repeated more within 209615 instances of "The offending signal" I've got withing a minute?
Yes "The offending signal was X on Y" tells us to focus on X and Y. Each combination of X and Y is a different bug. For example; bug 1994125, bug 2013070, bug 2042909, bug 1928082. > Re disabling extensions. I cannot reproduce this bug at will. Yes understood. Many people say the same. However, since we need to ensure a bug is actually caused by Ubuntu components and not bespoke customisation, we do need to be sure the problem happens with only the former and not the latter. Or else we're wasting time here discussing buggy extensions that Ubuntu does not release or maintain. This is especially important in the case of Ubuntu 22.04 which is now 3.5 years old and may be missing some fixes already present in later releases. The usual way to approach this is to just leave the bug "Incomplete" and then we have up to 60 days to provide the required information before the bug closes automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2117116 Title: Display goes black, gnome-shell goes 100% CPU spamming "Attempting to call back into JSAPI during the sweeping phase of GC." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2117116/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
