nautilus crashes on non-X11 systems Wayland and Mir, with SIGSEGV trying to call XInternAtom() from gdk_x11_atom_to_xatom_for_display()

[Cristian Aravena Romero]

Crash nautilus.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
Uname: Linux 4.7.0-040700rc7-lowlatency x86_64
ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jul 13 17:03:08 2016
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2015-07-26 (353 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
ProcCmdline: nautilus -n
SegvAnalysis:
 Segfault happened at: 0x1a7fa20: add (%rax),%eax
 PC (0x01a7fa20) in non-executable VMA region: 0x01a3f000-0x01eb7000 rw-p [heap]
 source "(%rax)" (0x01a7bf00) ok
 destination "%eax" ok
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 XInternAtom () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in XInternAtom()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 XInternAtom (dpy=0x1a7f160, name=name@entry=0x1e96f90 "_NET_DESKTOP_MANAGER_S0", onlyIfExists=onlyIfExists@entry=0) at ../../src/IntAtom.c:174
 gdk_x11_atom_to_xatom_for_display (display=display@entry=0x1ac0000, atom=atom@entry=0x53) at /build/gtk+3.0-hEt8eK/gtk+3.0-3.18.9/./gdk/x11/gdkproperty-x11.c:115
 nautilus_desktop_window_init_selection (window=0x1d2e330) at nautilus-desktop-window.c:136
 nautilus_desktop_window_constructed (obj=<optimized out>) at nautilus-desktop-window.c:191

[Daniel van Vugt (vanvugt)]

Hi, are you using Unity7/X11 or Unity8, or other?

I just found a similar crash in bug 1603923

[Cristian Aravena Romero (caravena)]

Hi, gnome-shell

[Daniel van Vugt (vanvugt)]

Gnome Shell on X11 (default) or on Wayland?

[Cristian Aravena Romero (caravena)]

Daniel, Wayland

[Daniel van Vugt (vanvugt)]

Awesome, thanks. Then my Mir crash is the same bug as this. Nautilus on any non-X11 platform will hit it.

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

I fixed a similar crash a while back in a different app. It might be the same issue...
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1444132/comments/1

[Sebastien Bacher (seb128)]

Does it work if you make it no display the background (using --no-desktop or changing the gsettings key)?

It might be fixed with https://git.gnome.org/browse/nautilus/commit/?id=c8f45f2 if somebody wants to try that patch, unsure if it would need updating for our older nautilus version though

[Daniel van Vugt (vanvugt)]

It still crashes in the same place even with nautilus --no-desktop

I'm still guessing it's a simple fix like in comment #12.

[Sebastien Bacher (seb128)]

@Daniel, your backtrace looks different from the one on this bug though ... anyway, to debug by somebody who has a machine without x11 working well enough to be able to start nautilus

[Daniel van Vugt (vanvugt)]

Oh I see... this was already fixed upstream in nautilus 3.16 but Ubuntu has version "3.18.4.is.3.14.3-0ubuntu4" which is actually quite old.

[Daniel van Vugt (vanvugt)]

Yes, comments on the upstream bug are that this was already resolved by:

https://git.gnome.org/browse/nautilus/commit/?id=c8f45f2

We just need that patch in Ubuntu.

[Daniel van Vugt (vanvugt)]

Ubuntu 16.10 yakkety has been updated with the latest Gnome packages and it works now.