Bug 1269987 - KDE Applications won't show contents of nfs mount (automount)
Summary: KDE Applications won't show contents of nfs mount (automount)
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 22
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-08 17:35 UTC by info@kobaltwit.be
Modified: 2016-07-19 18:09 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:09:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot displaying the same nfs directory in different applications (239.22 KB, image/png)
2015-10-08 17:35 UTC, info@kobaltwit.be
no flags Details


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 356791 0 None None None 2015-12-16 20:05:36 UTC

Description info@kobaltwit.be 2015-10-08 17:35:08 UTC
Created attachment 1081071 [details]
Screenshot displaying the same nfs directory in different applications

Description of problem:
KDE gui applications such as Dolphin or kde gui componenents such as the File Open dialog fail to show the contents of some automounted nfs partitions.

I have attached a screenshot to illustrate the issue. I have captured 4 different applications attempting to display the contents of
/kobaltnet/goudsmid/bin
/kobaltnet is the base mount point for my autofs mounted nfs shares. goudsmid is one such share.

1. In the top-left you see Konsole running a bash session. It can list the contents of the directory just fine
2. Top-right is dolphin, which just shows an empty directory
3. Bottom-left is nautilus, which shows the directory contents just fine
4. Bottom-right is the file-open dialog for okular, listing an empty directory

Version-Release number of selected component (if applicable):
I'm not sure I chose the right component. I don't really know which part of kde/plasma is responsible for this.
Anyway, I see this with 5.4.1-3 and up (also the updates in updates-testing).

There are a few remarkable details that are important:
- this only happens with nfs shares I'm not the owner of (my id is janssege in the screenshot, the nfs share is owned by user goudsmid). When I access shares I do own, this behaviour doesn't show.
- the behaviour starts from the second level down the mount point. In the example, I can see the contents of /kobaltnet/goudsmid, but not of any of its subdirectories.
- hitting F5 on the empty contents does shortly reveal the contents (it flashes a fraction of a second) and the the window goes blank again. So this suggests the directory contents is properly written but then discarded from some reason.

How reproducible:
Always

Steps to Reproduce:
1. Set up an nfs share which is automounted, not owned by you, but with proper group access permissions
2. Open dolphin and navigate to the mounted share. The contents will be visible.
3. Continue to navigate to a subdirectory.
4. Hit F5

Actual results:
3. The contents of the subdirectory won't be shown
4. The actual contents briefly flashes in the window, but won't show permanently.

Expected results:
Normal navigation through the share and all of it's subdirectories. The other applications (konsole/bash and nautilus) illustrate there's no access/file permission issue causing this.

Additional info:
This change is fairly recent. I know I recently updated to plasma 5.4.1 from 5.3.x. However the KDE frameworks were also recently updated, so perhaps that's the culprit.

Comment 1 info@kobaltwit.be 2016-02-17 20:53:19 UTC
Some further evolution. It looks like this bug is fixed for kf5 based applications. Current Dolphin (dolphin-15.12.1-1.fc23.x86_64) no longer has this issue.

KDE 4 based applications still behave erratically. For example, current okular still won't properly show the contents of an nfs share not owned by the logged in user.

Note also that even though the folder contents is not shown (or only briefly), I can still navigate deeper down the hierarchy by typing the the address bar. This still correctly autocompletes as well. So it's really something in the folder content view area that's messed up.

Comment 2 info@kobaltwit.be 2016-05-10 12:58:03 UTC
Unfortunately after yesterday's update to plasma 5.6.2, dolphin has regressed to the bad behaviour. This is one of the most frustrating bugs I have encountered so far as it affects almost all interactions with my nfs mounts (dolphin, okular, kontact,...).

I intended to add more details about some components that may be related. However the packages were updated from the software updater in the system tray and this appears to leave no history record in dnf history. So I'm not sure how to trace back what exactly was updated. I recall plasma workspace got updated to 5.6.2 and also kf5-kio got updated to 5.21.0.

Current version of dolphin: dolphin-15.12.3-1.fc23.x86_64, however I don't know if it was updated yesterday. Anyway I don't think it's in dolphin specific code as I can reproduce it with almost any kde application.

Any help or suggestions to debug this would be more than welcome.

Comment 3 Rex Dieter 2016-05-11 13:51:03 UTC
dolphin doesn't rely on plasma at all really (besides window manager), it's more likely to be kf5-related

Comment 4 info@kobaltwit.be 2016-05-26 16:19:56 UTC
I tried to narrow it down by more selectively upgrading on another system, but failed due to strong dependencies between kf5 and plasma.

Below is a summary of my attempts:
- install only qt5 updates => dolphin still works fine
- install all available kf5 updates => dolphin starts misbehaving
- downgraded kf5 updates back to original f23 versions => dolphin works fine again
- install all plasma updates => won't work without updated kf5 packages
- several attempts to add some kf5 updates => either plasma still didn't work or dolphin starts misbehaving

So I can't confirm whether the issue is with plasma or kf5.

I was able to narrow down the poor behaviour a bit more though:
- example simple directory hierarchy:
  nfs-share
    \
    subdir
      \
      sub-subdir
  so the nfs share "nfs-share" has one subdirectory called "subdirectory" and in that directory there's another subdirectory called "sub-subdirectory"
- current user is janssege
- nfs-share is owned by goudsmid:goudsmid and has permissions rwxrwx---
=> user can view contents of the share, but not contents of subdirectories on the share

Change permissions to rwxrwx--x
=> user can also view contents of subdirectories on the share

The permissions on subdirectory will likewise define whether I can see the contents of sub-subdirectory. If the permissions of subdirectory are rwxrwx---, the contents of sub-subdirectory is empty, of they are rwxrwx--x, I can see the contents. Navigating back up from sub-subdirectory (when I can't see it's contents) will bring me back to subdirectory, but it will no longer have sub-subdirectory listed in its contents. That is restored by hitting F5.

It also still stands that I can navigate to sub-subdirectory in all circumstances above from a konsole window or in nautilus and will always see its contents. And also when explicitly typing the address in dolphin's address bar, the suggestion dropdown properly suggests all subdirectories, regardless of the permissions.

So it's apparently limited to the widget that should display the contents of the directory.

Comment 5 info@kobaltwit.be 2016-05-28 16:18:03 UTC
Forgot to mention in my previous comment:

User janssege is member of the goudsmid group, but that's not the user's primary group.

Comment 6 Fedora End Of Life 2016-07-19 18:09:29 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.