Thank you. I retained the locally generated Apport core and have now run GDB against it. I have attached the complete multi-thread backtrace as gnome-shell-nvidia-610-gdb.txt.
The crashing thread directly shows the following call chain: #0 0x00000000400dde66 in ?? () #5 libnvidia-eglcore.so.610.43.02 #6 libnvidia-eglcore.so.610.43.02 #9 libnvidia-eglcore.so.610.43.02 #10 libnvidia-eglcore.so.610.43.02 #11 libnvidia-eglcore.so.610.43.02 #12 libnvidia-eglcore.so.610.43.02 #13 libnvidia-eglcore.so.610.43.02 #14 libmutter-cogl-18.so.0 #15 cogl_framebuffer_read_pixels_into_bitmap() #16 clutter_stage_paint_to_buffer() #17-#24 Mutter/Clutter frame rendering The instruction pointer at frame #0 is inside the deleted memfd:/.glXXXXXX mapping. The immediate callers are nine consecutive frames in libnvidia-eglcore.so.610.43.02, invoked while Mutter is reading/painting the The loaded libraries also include: I also confirm that bug #2162031 matches the separate gnome-remote-desktop/libei crash that appeared in the previous journal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2162030 Title: GNOME Remote Login headless GDM shell crashes with NVIDIA 610 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2162030/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
