nautilus crashes when run under Mir

Bug #1603923 reported by Daniel van Vugt on 2016-07-18
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gtk+3.0 (Ubuntu)
Undecided
Unassigned
nautilus (Ubuntu)
Undecided
Unassigned

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

Daniel van Vugt (vanvugt) wrote :

Possibly bug 1602863?

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gtk+3.0 (Ubuntu):
status: New → Confirmed
Changed in nautilus (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers