OK we'll need to see the stack trace then so please:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
Take care to avoid attaching .crash files to bugs as we are unable to
process them as file attachments. It would also be a security risk for
yourself.
** This bug is no longer a duplicate of bug 2050865
GNOME Wayland session crashes with
libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor:
assertion failed: (logical_monitor)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097003
Title:
gnome-shell crashed with SIGABRT
[libmutter:ERROR:../src/core/window.c:5937:meta_window_get_work_area_for_logical_monitor:
assertion failed: (logical_monitor)]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2097003/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
