Red Hat Bugzilla – Bug 477598
Something is being impatient when unmounting slower volumes
Last modified: 2015-03-03 17:33:48 EST
Description of problem:
One of either nautilus, dbus or hal is timing out too hastily when unmounting slower volumes with a large amount of data yet to be synced. After a while, I get the error message
Unable to unmount <slow volume label>
DBus error org.freedesktop.DBus.Error.NoReply: 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
The device does unmount successfully. I don't see this with faster devices.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Find a slower volume (such as a cheap USB stick).
2. Write a lot of data to it.
3. Unmount via nautilus and wait.
Error message described.
System waits patiently until the job is done (so the timeout needs to be *much* higher, or use some intelligent measure based upon the device's performance).
Created attachment 347614 [details]
Error being displayed on USB flash drive unmount
I'm seeing this in Fedora 11 as well, if you want to update the release. The attached screenshot shows data being written when the error pops up. After the data write completes, the "Writing data to..." message clears, but the error remains until acknowledged manually.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.