I have an external storage that I access by my local network (Datatank Gateway - Freecom). I had Ubuntu 18.04 version and I could access to this external device without problems. I could move all files from-to the external device and open and execute them properly. I upgraded to 20.04 Ubuntu version and it stopped to access to this device. Then I changed smb.conf file adding the line: "client min protocol = NT1" and then I got access to the device. I can see the folders and subfolders, but all icons are folders, even the .xls or .doc or .pdf are shown as folders. I cannot transfer them from external device to any of my internal folders in my pc. I can read some of them, like .doc, but I have to select manually what program I need to execute to read it. .pdf files can also be read. But .xls or .pgn or .mp3 cannot be read. An error message appear saying "Content cannot be shown. It is not a folder". In summary I have access to me external device but I cannot manage normally any of the files inside my external device, as I did before with ubuntu version 18.04. All icons appear as folders regardless it is a real folder or a file.
I woudl appreciate to assist to solve thsi problem.
Thank you
Leopoldo Soria
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gvfs 1.44.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 1 19:13:04 2020
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=es_ES.UTF-8
SHELL=/bin/bash
SourcePackage: gvfs
Symptom: storage
Title: Documents cannot be opened in desktop UI on storage device
UpgradeStatus: No upgrade log present (probably fresh install)
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1872476, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.