I've had a look at your crash files and unfortunately they do not contain stack traces we can read yet. Sometimes they do in plain text... Uploading the crash files with the 'ubuntu-bug' command should fix that, allowing robots to do proper retracing on them.
Asking other people to reproduce such problems is not a good idea, since there are too many similar gnome-shell crashes right now. Another person is just as likely to reproduce a different crash to yours which confuses the situation. Next step: Please upload the crash files using the ubuntu-bug command only. We cannot proceed until that is done: ubuntu-bug _usr_bin_gnome-shell.1000.crash ubuntu-bug _usr_bin_Xwayland.1000.crash When done, please tell us the new bug IDs. P.S. Sharing crash files publicly on your own web server is considered insecure, because it is publicly readable by anyone. A more secure approach for sharing crash files (and only if 'ubuntu-bug' fails), is to set your bug report to "Private" and then attach them to the bug report. That way only a very small number of bug managers can see it, as well as yourself. Using the ubuntu-bug command also creates 'Private' bugs by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749779 Title: System freeze when going back and forth fullscreen mode with Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
