After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 768893 - nautilus crashed with SIGSEGV in XInternAtom()
nautilus crashed with SIGSEGV in XInternAtom()
Status: RESOLVED DUPLICATE of bug 746286
Product: nautilus
Classification: Core
Component: Crashers
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-07-17 00:01 UTC by Cristian Aravena Romero
Modified: 2016-07-21 07:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Cristian Aravena Romero 2016-07-17 00:01:38 UTC
Open bug in launchpad.net :
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1602863

"Crash nautilus."

BackTrace:
  • #0 ??
  • #1 XInternAtom
    at ../../src/IntAtom.c line 174
  • #2 gdk_x11_atom_to_xatom_for_display
    at /build/gtk+3.0-hEt8eK/gtk+3.0-3.18.9/./gdk/x11/gdkproperty-x11.c line 115
  • #3 nautilus_desktop_window_init_selection
    at nautilus-desktop-window.c line 136
  • #4 nautilus_desktop_window_constructed
    at nautilus-desktop-window.c line 191
  • #5 g_object_new_internal
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #6 g_object_new_valist
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #7 g_object_new
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #8 nautilus_desktop_window_new
    at nautilus-desktop-window.c line 254
  • #9 nautilus_desktop_window_ensure
    at nautilus-desktop-window.c line 272
  • #10 g_closure_invoke
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #11 signal_emit_unlocked_R
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #14 g_simple_action_activate
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #15 update_desktop_from_gsettings
    at nautilus-application.c line 1008
  • #16 init_desktop
    at nautilus-application.c line 1022
  • #17 nautilus_application_startup
    at nautilus-application.c line 1269
  • #18 _g_closure_invoke_va
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #21 g_application_register
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #22 nautilus_application_handle_local_options
    at nautilus-application.c line 908
  • #23 ffi_call_unix64
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libffi.so.6
  • #24 ffi_call
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libffi.so.6
  • #25 g_cclosure_marshal_generic_va
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #26 _g_closure_invoke_va
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #29 g_application_real_local_command_line
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #30 g_application_run
    from /tmp/apport_sandbox_CpyxkK/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #31 main
    at nautilus-main.c line 103

Comment 1 Carlos Soriano 2016-07-18 12:57:50 UTC
In the bug report in launchpad this crash is with version 3.14, however this is set to version 3.18.

Is that reproducible with version 3.18?
Also, do you use X server or a different display manager?
Comment 2 Cristian Aravena Romero 2016-07-20 21:45:01 UTC
Carlos, Wayland.
Comment 3 Carlos Soriano 2016-07-21 07:45:07 UTC
This was fixed long time ago for 3.16, looks like you are using an old unsupported version.

*** This bug has been marked as a duplicate of bug 746286 ***