Public bug reported: nautilus crashes when run under Mir:
Thread 1 "nautilus" received signal SIGSEGV, Segmentation fault. 0x000000007473696c in ?? () (gdb) bt #0 0x000000007473696c in ?? () #1 0x00007ffff4136c23 in g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007ffff6761a8c in gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #3 0x000000000043a0a8 in ?? () #4 0x00007ffff4424897 in ?? () Which sounds familiar. I had the same crash in Remmina and the fix was simple: bug 1444132 ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: gtk-mir ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1603923 Title: nautilus crashes when run under Mir Status in gtk+3.0 package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: nautilus crashes when run under Mir: Thread 1 "nautilus" received signal SIGSEGV, Segmentation fault. 0x000000007473696c in ?? () (gdb) bt #0 0x000000007473696c in ?? () #1 0x00007ffff4136c23 in g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007ffff6761a8c in gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #3 0x000000000043a0a8 in ?? () #4 0x00007ffff4424897 in ?? () Which sounds familiar. I had the same crash in Remmina and the fix was simple: bug 1444132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1603923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp