Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'

Bug #1633162 reported by Anurag
280
This bug affects 59 people
Affects Status Importance Assigned to Milestone
gvfs
Fix Released
High
gvfs (Ubuntu)
Fix Released
High
Unassigned
Zesty
Won't Fix
High
Unassigned
nautilus (Ubuntu)
Invalid
High
Unassigned

Bug Description

The application crashes every time I click on 'Recent' with this message in a pop-up window:

"Unhandled error message: Message recipient disconnected from message bus without replying."

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nautilus 1:3.20.3-1ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Oct 13 22:34:57 2016
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'enable-interactive-search' b'false'
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+476+24'"
InstallationDate: Installed on 2016-10-13 (0 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

Revision history for this message
Anurag (anuragpv2003) wrote :
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
max (max-illis) wrote :

I have the same issue. Let me know what information you need

Revision history for this message
jferna57 (jferna57) wrote :

Me too. Steps to reproduce the bug:

1. Log in with an anonymous user (with a normal session happens too)
2. Open nautilus.
3. Click on Recent Items
4. An error appear (see Seleccion_040.jpg)

I try to find more information about it.

Revision history for this message
Chris Hermansen (c-hermansen) wrote :

My steps are similar to #4 above but the problem occurs when I am logged in as regular user (me).

Seems to be no workaround.

FWIW my 16.10 is upgraded from 16.04 and not a fresh install.

Revision history for this message
Jean-Max Reymond (jmreymond-free) wrote :

same issue with regular user and update from 16.04 to 16.10

Revision history for this message
Mordi (mrdc76) wrote :

I too have the same issue. Updated from (fresh) 16.04 to 16.10. The error occurs with the guest account as well.

Revision history for this message
Arno Mühren (arnomuhren) wrote :

This bug affects me as well. It was an upgrade from 16.04 to 16.10.
It is not possible to open the recents tab in nautilus.

Revision history for this message
Fabio B (bonfabio) wrote :

This bug affects me as well, anyway the "recent files" works inside modal windows while opening/selecting files

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in nautilus (Ubuntu):
importance: Undecided → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

the log has that error "nautilus[2093]: Could not find signal handler 'create_folder_dialog_on_response'. Did you compile with -rdynamic?" unsure if that's the issue though

Revision history for this message
Olivier Febwin (febcrash) wrote :

same issue!

Revision history for this message
Olivier Febwin (febcrash) wrote :
Changed in nautilus:
importance: Unknown → High
status: Unknown → Incomplete
Revision history for this message
Olivier Febwin (febcrash) wrote :
tags: added: systemd-session
Changed in nautilus (Ubuntu):
importance: Low → High
Revision history for this message
Jean-Max Reymond (jmreymond-free) wrote :

as described in https://bugzilla.gnome.org/show_bug.cgi?id=773300

Adding "Environment=DISPLAY=:0" in the service file:
/usr/lib/systemd/user/gvfs-daemon.service, solves it.

Revision history for this message
Iiro Laiho (iiro) wrote :

The package needs to be made to not to preserve the /usr/lib/systemd/user/gvfs-daemon.service file?

Revision history for this message
Robert Edwards (raedwards) wrote :

Confirmed that the fix posted by Jean-Max Reymond solves the issue.

Revision history for this message
Ioannis Iliadis - Ilousis (ioannis.ilousis) wrote :

I can also confirm that: The post, of Jean-Max Reymond on 2016-11-07, is the solution.

Revision history for this message
Meindert Frouws (m-j-frouws) wrote :

The fix posted by Jean-Max Reymond didn't solve the issue for me.

Revision history for this message
Jason Robinson (jaywink) wrote :

Confirmed #15 workaround works for me. Note, reboot/relogin is needed after editing the file. Ubuntu 16.10 fresh install.

Changed in nautilus:
status: Incomplete → Confirmed
Revision history for this message
Robert J. Wingard (bw1277-f) wrote :

Confirming #15 workaround works for me. As mentioned in #20, a reboot/relogin is required.

Revision history for this message
Riccardo (riciricir) wrote :

Same for me, workaround #15 works (Ubuntu 16.10 Unity) after reboot.

(Editing /usr/lib/systemd/user/gvfs-daemon.service requires root privileges).

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

upstream commited a simple change to not required gtk_init for that backend which should solve the issue

https://git.gnome.org/browse/gvfs/commit/?id=6883981a14fbe512815783a2966f2a8a0149034f

muhammad (aboras)
Changed in nautilus (Ubuntu):
status: Confirmed → New
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
Meindert Frouws (m-j-frouws) wrote :

#15 workaround works partially.I have two accounts on my computer. It works only for the first person that logs in.

Revision history for this message
John@vosslers.net (john-vosslers) wrote :
Download full text (6.4 KiB)

#15 workaround does NOT work for me.

My issue is specific to accessing an audio CD in an external USB CD drive.

The issue surfaced when I upgraded the Ubuntu 16.04 kernel from 4.4.0-59 to 4.4.0-62.

Booting under the older 4.4.0-59 kernel does NOT restore functionality.

At the same time I upgraded the kernel I also upgraded several packages (apt-get upgrade). I suspect the bug was introduced in one of these packages.

List of packages upgraded:

gstreamer1.0-plugins-ugly-amr:amd64 (1.8.2-1ubuntu0.1, 1.8.3-1ubuntu0.1)
liboxideqt-qmlplugin:amd64 (1.19.4-0ubuntu0.16.04.1, 1.20.4-0ubuntu0.16.04.1)
libkrb5-3:amd64 (1.13.2+dfsg-5ubuntu1, 1.13.2+dfsg-5ubuntu2)
libkrb5-3:i386 (1.13.2+dfsg-5ubuntu1, 1.13.2+dfsg-5ubuntu2)
libgssapi-krb5-2:amd64 (1.13.2+dfsg-5ubuntu1, 1.13.2+dfsg-5ubuntu2)
libgssapi-krb5-2:i386 (1.13.2+dfsg-5ubuntu1, 1.13.2+dfsg-5ubuntu2)
gstreamer1.0-alsa:amd64 (1.8.2-1ubuntu0.2, 1.8.3-1ubuntu0.1)
liboxideqtquick0:amd64 (1.19.4-0ubuntu0.16.04.1, 1.20.4-0ubuntu0.16.04.1)
libdrm-nouveau2:amd64 (2.4.67-1ubuntu0.16.04.2, 2.4.70-1~ubuntu16.04.1)
libdrm-nouveau2:i386 (2.4.67-1ubuntu0.16.04.2, 2.4.70-1~ubuntu16.04.1)
os-prober:amd64 (1.70ubuntu3, 1.70ubuntu3.3)
linux-libc-dev:amd64 (4.4.0-59.80, 4.4.0-62.83)
liboxideqtcore0:amd64 (1.19.4-0ubuntu0.16.04.1, 1.20.4-0ubuntu0.16.04.1)
gstreamer1.0-plugins-base-apps:amd64 (1.8.2-1ubuntu0.2, 1.8.3-1ubuntu0.1)
openssl:amd64 (1.0.2g-1ubuntu4.5, 1.0.2g-1ubuntu4.6)
libgnutls-openssl27:amd64 (3.4.10-4ubuntu1.1, 3.4.10-4ubuntu1.2)
ntfs-3g:amd64 (1:2015.3.14AR.1-1build1, 1:2015.3.14AR.1-1ubuntu0.1)
gstreamer1.0-tools:amd64 (1.8.2-1~ubuntu1, 1.8.3-1~ubuntu0.1)
iucode-tool:amd64 (1.5.1-1, 1.5.1-1ubuntu0.1)
gstreamer1.0-plugins-good:amd64 (1.8.2-1ubuntu0.3, 1.8.3-1ubuntu0.3)
libglapi-mesa:amd64 (11.2.0-1ubuntu2.2, 12.0.6-0ubuntu0.16.04.1)
libglapi-mesa:i386 (11.2.0-1ubuntu2.2, 12.0.6-0ubuntu0.16.04.1)
humanity-icon-theme:amd64 (0.6.10, 0.6.10.1)
sudo:amd64 (1.8.16-0ubuntu1.2, 1.8.16-0ubuntu1.3)
google-chrome-stable:amd64 (56.0.2924.76-1, 56.0.2924.87-1)
console-setup-linux:amd64 (1.108ubuntu15.2, 1.108ubuntu15.3)
open-vm-tools:amd64 (2:10.0.7-3227872-2ubuntu1, 2:10.0.7-3227872-5ubuntu1~16.04.1)
libxatracker2:amd64 (11.2.0-1ubuntu2.2, 12.0.6-0ubuntu0.16.04.1)
libk5crypto3:amd64 (1.13.2+dfsg-5ubuntu1, 1.13.2+dfsg-5ubuntu2)
libk5crypto3:i386 (1.13.2+dfsg-5ubuntu1, 1.13.2+dfsg-5ubuntu2)
gstreamer1.0-plugins-bad:amd64 (1.8.2-1ubuntu0.2, 1.8.3-1ubuntu0.2)
console-setup:amd64 (1.108ubuntu15.2, 1.108ubuntu15.3)
libegl1-mesa:amd64 (11.2.0-1ubuntu2.2, 12.0.6-0ubuntu0.16.04.1)
gstreamer1.0-plugins-base:amd64 (1.8.2-1ubuntu0.2, 1.8.3-1ubuntu0.1)
gstreamer1.0-plugins-base:i386 (1.8.2-1ubuntu0.2, 1.8.3-1ubuntu0.1)
libklibc:amd64 (2.0.4-8ubuntu1.16.04.2, 2.0.4-8ubuntu1.16.04.3)
gstreamer1.0-plugins-bad-videoparsers:amd64 (1.8.2-1ubuntu0.2, 1.8.3-1ubuntu0.2)
libwxgtk3.0-0v5:amd64 (3.0.2+dfsg-1.3, 3.0.2+dfsg-1.3ubuntu0.1)
libgstreamer-plugins-good1.0-0:amd64 (1.8.2-1ubuntu0.3, 1.8.3-1ubuntu0.3)
gstreamer1.0-pulseaudio:amd64 (1.8.2-1ubuntu0.3, 1.8.3-1ubuntu0.3)
libgbm1:amd64 (11.2.0-1ubuntu2.2, 12.0.6-0ubuntu0.16.04.1)
krb5-locales:amd64 (1.13.2+dfsg-5ubuntu1, 1.13.2+dfsg-5ubuntu2)
libdrm-amdgpu1:amd64 (2.4.67-1ubuntu0.16....

Read more...

Revision history for this message
schuko24 (gerd-saenger) wrote :

Had updated to 16.10 a few weeks ago, but running only on kernel 4.4 because of issues with systemd. Recent update to kernel 4.8 was successful and brought up the bug 1633162.

Workaround #15 works fine (Ubuntu 16.10 Unity).

Revision history for this message
N V R Vikram G (gnvrvikram) wrote :

I too have the same issue but #15 did not workout for me. Some help needed.

Revision history for this message
Terry Dixon (terry-dixon) wrote :

workaround #15 works (Ubuntu 16.10 Unity)for me

Changed in nautilus:
status: Confirmed → Fix Released
Jeremy Bícha (jbicha)
Changed in gvfs (Ubuntu):
status: New → Fix Committed
importance: Undecided → High
Changed in gvfs (Ubuntu Zesty):
importance: Undecided → High
status: New → Triaged
affects: nautilus → gvfs
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gvfs - 1.33.90-0ubuntu1

---------------
gvfs (1.33.90-0ubuntu1) artful; urgency=medium

  * New upstream release (LP: #1633162)
  * debian/control.in:
    - Drop obsolete Build-Depends on libgtk-3-dev
  * Drop disable-polkit-rules-no-admin.patch:
    - Applied in new release

 -- Jeremy Bicha <email address hidden> Mon, 14 Aug 2017 10:25:38 -0400

Changed in gvfs (Ubuntu):
status: Fix Committed → Fix Released
Changed in gvfs (Ubuntu Zesty):
status: Triaged → Won't Fix
no longer affects: nautilus (Ubuntu Zesty)
Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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