Bug 492242

Summary:	Mounting NTFS or HFS drives displays seemingly pointless message "An operation is already pending"
Product:	[Fedora] Fedora	Reporter:	Stewart Adam <s.adam>
Component:	gvfs	Assignee:	Tomáš Bžatek <tbzatek>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	11	CC:	alexl, davidz, spike85051, steve.hugill, tbzatek, tsmetana
Target Milestone:	---	Flags:	spike85051: needinfo?
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-06-28 11:33:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Stewart Adam 2009-03-26 03:37:13 UTC

Description of problem:
As I was testing the nouveau driver using the Test Day 2009-03-25 Live CD, I found that attempting to mount my HFS+ or NTFS internal partitions displayed this error message:

Unable to mount location
DBus error org.gtk.Private.RemoteVolumeMonitor.Failed: An operation is already pending

However, after a second or two the partitions mounted as usual.

Version-Release number of selected component (if applicable):
Test Day 2009-03-25 Live CD

How reproducible:
Always

Steps to Reproduce:
1. Select Places > Computer from the menu
2. Attempt to mount HFS+ or NTFS volumes
  
Actual results:
Error message: "DBus error org.gtk.Private.RemoteVolumeMonitor.Failed: An operation is already pending" as the volume is being mounted

Expected results:
Volumes mount without the error message being displayed

Additional info:
I was running off of a CD, not USB media- maybe the operation was just taking longer than expected because of the slow read speeds?

Comment 1 Tomáš Bžatek 2009-03-27 09:54:02 UTC

Seems like the NTFS mount operation takes very long time.

Comment 2 Stewart Adam 2009-03-27 10:42:39 UTC

That's why I found the error a bit odd, since the entire process I described above took no more than about 3-5 seconds.

Comment 3 David Zeuthen 2009-04-06 23:51:05 UTC

(In reply to comment #0)
> DBus error org.gtk.Private.RemoteVolumeMonitor.Failed: An operation is already
> pending

This suggests that it is a gvfs bug.

Comment 4 Bug Zapper 2009-06-09 12:38:30 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2010-04-27 13:19:33 UTC

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Steve Hugill 2010-06-07 01:03:41 UTC

Hi,

I'm getting this constantly on the first release of FC13...

any ideas?

Comment 7 Bug Zapper 2010-06-28 11:33:56 UTC

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.

Comment 8 Richard Jasmin 2015-12-14 14:03:28 UTC

UH, someone CANT READ. 13> 11.
I can report it with various filesystems on 22.
22>11.
The underlying filesystem is unimportant.In this particular case, it may be gvfs, however this seems to be an automounting glitch.Straight off the repo as it were a clean install or boot generally wont trip this.

As I said, it appears to be an automounter glitch.
Under LXDE I am now getting this error on ANY media insertion. While I welcome automounting on insert, everything seems to get mounted twice now for some reason.

Is autofs installed, YOU BET.Will removing it fix the issue is unknown.I would rather not get the "what do you want to do with this" on every mount of any device. Generally "open" is acceptable.