This bug may still be impacting me, but since I'm not 100% sure if the cause is the same I am not sure. It seems to have gotten better in some but not all situations. I did reboot to apply the released fix so this is the most recent versions hopefully.
Perhaps useful to note that it doesn't crash until the monitor turns back on. I was able to test this because I play brown noise in a terminal with the monitor off but not locked overnight. In the morning sound is still playing, and I was able to Ctl-C without turning on the monitor to turn off the sound so it was still a responsive and logged in system until then. But then it crashed when I turned the monitor back on. I've uploaded the crash logs for the different methods of failure a few times using ubuntu-bug. I'm not certain that the logs are showing up, nor sure how to check. When I run ubuntu-bug on the crash file it opens the dialog for reporting a bug, I click continue but then the dialog immediately exits with no further user interaction. Is this correct behavior? I seem to remember years ago that the dialog would open up a web browser to this site but it hasn't done that in ages for me. I'm assuming it's working transparently now but please let me know if they aren't showing up as reported bugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724557 Title: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724557/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
