(nautilus:13848): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply.

Bug #800107 reported by Jonatan Høy Sørensen on 2011-06-21
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: nautilus

(nautilus:13848): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Makes File Manager unable to open, and causes it to stop shutdown, with error message "File manager is not responding" and won't continue untill it is forced to close file manager.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: nautilus 1:2.32.2.1-0ubuntu13
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
Date: Tue Jun 21 11:32:39 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
ProcEnviron:
 LANGUAGE=en_DK:en
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Please also attach your ~/.xsession-errors to the report, thanks in advance.

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

The bug is reproducible by simply booting the system, Happens every time, and has happened for little over a week now.

File Manager won't open. And even though icons are drawn on the desktop, I can't click, or in any way interact with them(with the exception of using the terminal)

I appear to be unable to attach the file, I am not sure why though.

Running tail on .xsession.errors gives me this:

jhs@jhs-ThinkPad-Edge:~$ tail .xsession-errors

** (nautilus:1499): CRITICAL **: syncdaemon_status_info_get_online: assertion `SYNCDAEMON_IS_STATUS_INFO (sinfo)' failed

** (nautilus:1499): WARNING **: Error calling get_folders: Message did not receive a reply (timeout by message bus)

** (nautilus:1499): WARNING **: Error calling current_status: Message did not receive a reply (timeout by message bus)

** (nautilus:1499): CRITICAL **: syncdaemon_status_info_get_online: assertion `SYNCDAEMON_IS_STATUS_INFO (sinfo)' failed

** (nautilus:1499): WARNING **: Error calling get_folders: Message did not receive a reply (timeout by message bus)

Hope it can help, else I will attempt to figure out, why it won't upload the file.

Jay Deiman (jay-splitstreams) wrote :

I have had the same exact issue on every one of my machines (4 of them) since upgrading to 11.04. Same error messages as the others in this bug report.

This is a fresh install, not an update.. And has only happend recently.. Before that it's been working for at least a month, before it started..

I'll try to upload the .xsession-errors again today, hope it works now.

After playing around with it some more, and seeing this getting spammed in dmesg:

[ 3116.742152] Valid eCryptfs headers not found in file header region or xattr region
[ 3116.742160] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO

I have come to believe they are related(as they start at the same time, 30 seconds after booting)

There aren't any 0 byte files in ~/.Private/ though, as there is in most other bug reports.

I am unsure how to proceed.

JohnC (j-s-cate) wrote :

I am getting these same errors after a recent update to Natty.

Example of pairs of messages now getting added to syslog every few seconds:-

kernel: [ 2824.271459] Valid eCryptfs headers not found in file header region or xattr region

AND

kernel: [ 2123.273844] Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO

Also Ubuntu One Control Panel reports:-

File Sync error. (org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus))"

System monitor also shows that the ubuntuone-syncdaemon cancels and restarts every few seconds with a new ID.

I have reported this through the UbuntuOne website as I'm not sure whether UbuntuOne is affecting Nautilus or Nautilus is affecting UbuntuOne - so I have posted here to see if it can help to solve the problem

I was able to get nautilus to work sometimes by killing it through system monitor, When it restarted I could for a short while use nautilus

Steve Holmes (bouncysteve) wrote :

I think that this is a duplicate of 509180 because of the trace in #7. Fix should be out any day now. Please un-duplicate if appropriate.

I confirm this bug in the latest Natty and Oneiric!

Download full text (16.2 KiB)

Here's the nautilus output:

** (nautilus:9833): WARNING **: Can't parse Nautilus' CSS custom description: /usr/share/nautilus/nautilus.css:0:0: Errore nell'aprire il file: File o directory non esistente

(nautilus:9833): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to underallocate NautilusPathBar's child GtkButton 0x9708700. Allocation is 24x37, but minimum required size is 27x27.

(nautilus:9833): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to underallocate GtkButton's child GtkArrow 0x96a7a40. Allocation is 12x25, but minimum required size is 15x15.

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_value_get_object: assertion `G_VALUE_HOLDS_OBJECT (value)' failed

(nautilus:9833): GLib-GObject-CRITICAL **: g_v...

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

Other bug subscribers