Summary: | "General input/output" opening a file through a symlink to a GVfs mount | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | R. Diez <rdiezmail-libreoffice> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | alex.garcia, aron.budea, serval2412 |
Priority: | medium | ||
Version: | 5.3.4.2 release | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 104742 |
Description
R. Diez
2017-07-27 13:37:55 UTC
Would it be possible you attach a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace) You may find recent LO version, with also debug symbols, here: http://dev-builds.libreoffice.org/daily/ I am sorry, but I do not have the time to provide a backtrace. It would be hard anyway, because it is not a crash. I have more information on this: 1) I am using Ubuntu 16.04.2 LTS, which has a different kernel version as the plain 16.04 version. 2) This kind of bug is apparently already known: https://bugs.launchpad.net/ubuntu/xenial/+source/gvfs/+bug/1598183 Regards, rdiez (In reply to R. Diez from comment #2) > I am sorry, but I do not have the time to provide a backtrace. It would be > hard anyway, because it is not a crash. > ... Oups, you're right of course, let's remove "wantbacktrace" It seems fixed on Ubuntu 16.10 but find nothing about 16.04. See https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1638245 (you can start reading from comment 10) In that bug report, which seems to be a different issue, they say that they fixed it in "xenial" too, which is Ubuntu 16.04. But I keep my systems up to date, and the problem I reported in this bug is still there. I have the same problem on 6.0.1.1 (debs from libreoffice.org) under Ubuntu 17.10. It's not because the symlinks, because it doesn't work if I access directly to /run/user/.... either. I cannot open or save a document. Nautilus is able to operate normally (create, modify, delete), so it's not a permission issue. Libreoffice opens the file with O_RDWR. Gvfs mounts only support opening files with O_TRUNC or O_APPEND. But not O_RDWR by itself. See... https://bugzilla.gnome.org/show_bug.cgi?id=748106 https://bugzilla.gnome.org/show_bug.cgi?id=777152 You will get an "operating not permitted" error which shows up in libreoffice as "general input/output error". Some file managers default to opening gvfs files from /run/user/... because most older or simple programs don't support opening files with gvfs URLs, they only support normal file names. Backtrace just dropped me off to an empty gdb shell. But I found this out by using --strace. |