Bug 1279078 - lockups during mount process
Summary: lockups during mount process
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fuse-sshfs
Version: 22
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-07 17:56 UTC by Richard Jasmin
Modified: 2016-07-19 19:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 19:22:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Richard Jasmin 2015-11-07 17:56:42 UTC
Description of problem:
This may be a fuse issue. When trying to ssh mount a remote folder the GUI seems to be in a locked state and nothing event driven can happen until the mount has finalized. Furthermore, interrupting the mount process results in an incomplete yet half-assed mount. One must unmount the remote location.

As a further bug, even user mounted folders in user locations must be unmounted as root or sudo.If users can mount, why is root access needed to unmount?

Version-Release number of selected component (if applicable):
22

How reproducible:
every mount

Steps to Reproduce:
1.try to mount somewhere (I use my webhost)
2.try to input a copied password
-or-
try to unmount somewhere

Actual results:
!!

Expected results:
none of this should be

Comment 1 Fedora End Of Life 2016-07-19 19:22:09 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.