File/Open produces the following nag screen:
The folder contents could not be displayed
Operation not supported
The message began several releases ago and exists with 3.6.4.
Fortunately, the operation is supported as I can select and open a file
after clicking OK.
I reported this as bug 55165. My original thinking was the problem is
distribution based. However, my current thinking is that I log in as
root with a / home directory - root:x:0:0:root/:/bin/bash. I realize
it's popular to use root root or log in as a non-root user to a non-root
home directory. However, I choose to use root at / and have done so for
years. LibreOffice only recently began presenting the message.
I can't find old releases for Linux and can't test exactly when the
message began. I'd appreciate if someone would test my theory. This
certainly not the world's biggest problem and I realize I operate
against the grain, but I don't believe the message should appear.
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-users] Error opening file. (The folder contents could not be displayed Operation not supported) · rhubarbpieguy
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.