Nautilus does not open after updating to 19.04

Bug #1822351 reported by Nicolás Abel Carbone on 2019-03-29

This bug report will be marked for expiration in 58 days if no further activity occurs. (find out why)

This bug affects 4 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)

Bug Description

After updating to Ubuntu 19.04 dev branch, nautilus does not open at all. Moreover, trying to open nautilus from the terminal does not give any error, nor any output at all, and no window opens.

I don't really know how to report this bug without any terminal output.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.32.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 29 13:58:12 2019
InstallationDate: Installed on 2018-02-23 (398 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
SourcePackage: nautilus
UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)

Update: Enabling and disabling the search and notification permissions on Settings->Applications->Nautilus solved the problem.

I will leave the bug report open as I think there is still a bug involved (maybe related to tracker?).

Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: New → Incomplete

Same issue here, same workaround helps.

Sebastian, it's seems like Nautilus does not crash. It just start, sit there and do nothing, not even create a window, yet still running in background.

Sebastien Bacher (seb128) wrote : describes how to get a stacktrace of a program hanging

Murshid Ahmed (murshid1988) wrote :

Same issue for me. It was working for a while and all of a sudden it stopped. The workaround mentioned in #2 doesn't work for me.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers