nautilus segfault with gnome-session-wayland

Bug #1520906 reported by Bryan Hundven
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Expired
Low
Unassigned

Bug Description

This is on 16.04, `update-manager -d` from 15.10 ubuntugnome.

Installed gnome-session-wayland after successfully using the normal gnome-session and tried to start nautilus after logging in.

It didn't start. I tried to start it from the shell and just got:

$ nautilus
Segmentation fault (core dumped)

I installed the wayland, libx11 and nautilus dbg packages and ran gdb:

$ gdb nautilus
(gdb) run
Starting program: /usr/bin/nautilus
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe8da7700 (LWP 6014)]
[New Thread 0x7fffe3fff700 (LWP 6015)]
[New Thread 0x7fffe37fe700 (LWP 6016)]
[New Thread 0x7fffe2bd3700 (LWP 6017)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff589850a in XInternAtom (dpy=0x799160,
    name=0xb54e30 "_NET_DESKTOP_MANAGER_S0", onlyIfExists=0)
    at ../../src/IntAtom.c:174
174 ../../src/IntAtom.c: No such file or directory.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.14.2-0ubuntu15
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.2-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Nov 29 02:02:35 2015
GsettingsChanges:

InstallationDate: Installed on 2015-11-29 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to xenial on 2015-11-29 (0 days ago)

Revision history for this message
Bryan Hundven (bryanhundven) wrote :
Revision history for this message
Bryan Hundven (bryanhundven) wrote :
Changed in nautilus (Ubuntu):
importance: Undecided → Low
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
Alexander Skwar (alexander-skwar) wrote :

Same for me with Xenial "final".

~/ gdb nautilus
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from nautilus...Reading symbols from /usr/lib/debug//usr/bin/nautilus...done.
done.
(gdb) run
Starting program: /usr/bin/nautilus
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe8af4700 (LWP 6969)]
[New Thread 0x7fffe3fff700 (LWP 6970)]
[New Thread 0x7fffe37fe700 (LWP 6971)]
[New Thread 0x7fffe2997700 (LWP 6972)]

Thread 1 "nautilus" received signal SIGSEGV, Segmentation fault.
0x00007ffff585450a in XInternAtom () from /usr/lib/x86_64-linux-gnu/libX11.so.6
(gdb) quit

Revision history for this message
Kartoch (kartoch) wrote :

This bug is still present in 16.04 with latest updates.

Revision history for this message
Kartoch (kartoch) wrote :

Workaround #1:

https://askubuntu.com/questions/790047/nautilus-not-launching-on-wayland

Quote:

    The problem was, nautilus wasn't updated to 3.18 in Ubuntu Gnome. I have updated it with the
    following commands:

    sudo add-apt-repository ppa:gnome3-team/gnome3
    sudo apt-get update && sudo apt-get upgrade

    And yes, it works!!!

Revision history for this message
Kartoch (kartoch) wrote :

The workaround #1 does not work for ubuntu 16.04:

output:

$ sudo add-apt-repository ppa:gnome3-team/gnome
Before upgrading your system to a new Ubuntu release (i.e. from Ubuntu 16.04 to 16.10), you should run 'ppa-purge ppa:gnome3-team/gnome3' first.

*** You need to run 'sudo apt-get dist-upgrade' to avoid problems. ***
Please read the output before entering 'Y' to make sure important packages won't be removed.

=== Bugs ===
Please use 'ubuntu-bug' to report bugs against packages in this PPA

=== End of Life ===
This PPA is no longer updated for releases older than Ubuntu 17.04. If you are using an older release, please ppa-purge this PPA and consider upgrading to a newer Ubuntu release.
Unless otherwise posted, updates will only be provided in this PPA for 7 months from the original release of the associated Ubuntu series.
https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004229.html
 More info: https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3

Revision history for this message
Brandon Jansen (jansennerd10) wrote :

The same issue is present on a fresh Ubuntu GNOME 16.04 LTS install with gnome-session-wayland.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Does anyone still get that issue in 18.04 or 18.10?

Changed in nautilus (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.]

Changed in nautilus (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.