No, the offending signal changes even withing a single incident. E.g. I've just got this bug when I opened laptop lid while the laptop was in the docking station with output on the external monitor. I've got 400MB+ of messages
$ sed -n -e 's/^.*\(The offending signal\)/\1/p' /var/log/syslog | uniq The offending signal was window-added on MetaWorkspace 0x58fd9a3bc060. The offending signal was window-left-monitor on MetaDisplay 0x58fd9a566030. The offending signal was window-entered-monitor on MetaDisplay 0x58fd9a566030. The offending signal was size-changed on ShellWM 0x58fd9a168160. The offending signal was window-removed on MetaWorkspace 0x58fd9a36de60. The offending signal was window-removed on MetaWorkspace 0x58fd9a36def0. The offending signal was window-removed on MetaWorkspace 0x58fd9a3bc060. The offending signal was window-removed on MetaWorkspace 0x58fd9a3bc0f0. ... -- 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
