User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier: LibreOffice 188.8.131.52 under linux gentoo amd64
image (.png) inserted from network disappear after some time
images are stored in the calc document
this bug affect older version of libreoffice in gentoo linux
Steps to Reproduce:
1.create calc document
2. insert image png for me and save
3. reopen document or wait some time image disappear
[Information automatically included from LibreOffice]
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Reset User Profile?No
It's a problem that I have had years ago, but I can't reproduce it any more.
Can you add information on the way you connect to your network (nfs, samba share, cifs mount, fstab entrys) and the server type (Windows, Linux)? I will try to confirm the problem for you.
The server is another linux gentoo server on the same network lan
i use ssh for connect to directly from gnome 3.16.2 interface
have some precision
image disappear after some time with no activity just the calc doc upen (i think 5 or more minutes but less 15 minutes)
and after that if i wan't to save the doc have an error that say something like
error to write access temp folder and i can't save doc
this error appear if i use the calc (or draw) doc from my ssh network folder on server
but if i use and edit the doc on my local linux computer haven't got this error only network image error...
i think it's problem sound like ssh network timeout for temp folder with libreoffice
my gentoo is updated and use systemd for precision
i work with lbreoffice linux in my office, and now i'm must use windows libreoffice (same version) with same network linux gentoo (shared with samba) and haven't got this bug (have another libreoffice bug but it's another story)
Thank for reading
Hello Christophe, *,
thank you for reporting your bug here :) I have not found a way to connect LO on my netbook via SSH to my notebook, but instead tried it with ownCloud via WebDAV, which worked without any problem ... ;)
As you mentioned Gentoo, where you have observed this behaviour: does this problem only occur with Gentoo's LO version or also with ours? If it only occurs with Gentoo, I think, it would be better to report it at https://bugs.gentoo.org (after looking through https://bugs.gentoo.org/buglist.cgi?quicksearch=app-office%2Flibreoffice, if it is not already reported there ... ;) And have you tried it with a newer version than 184.108.40.206? Does this bug occur there, too?
Sorry for the inconvenience
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Dear Bug Submitter,
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Dear Bug Submitter,
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker