When closing LO, sometimes a directory beginning with the characters 'lu' (that's lowercase L followed by a lowercase U) is left behind in the O/S's temp directory (specified by the associated environment variable). Sometimes this directory is empty, other times it contains files beginning with 'lu' (but different than the directory name). These files should be cleaned up when LO is closed. This is not due to a crash, as it happens when LO closes cleanly. I have experienced this with LO Writer and LO Calc. Possibly with other components too, but those two for sure.
Debian 7 x86_64: $ ls -l /tmp/lu* /tmp/lumxbplr.tmp: total 0 -rw------- 1 oweng users 0 Jul 15 17:53 lumxbplt.tmp /tmp/lun5zuyw.tmp: total 920 -rwxr-xr-x 1 oweng users 740424 Jan 28 21:40 lun5zuyy.tmp -rw------- 1 oweng users 69 Jul 15 21:56 lun5zuz0.tmp -rw------- 1 oweng users 5074 Jul 15 21:56 lun5zuz2.tmp -rw------- 1 oweng users 8628 Jul 15 21:56 lun5zuz4.tmp -rw------- 1 oweng users 7914 Jul 15 21:56 lun5zuz6.tmp -rw------- 1 oweng users 2499 Jul 15 21:56 lun5zuz8.tmp -rw------- 1 oweng users 8737 Jul 15 21:56 lun5zuza.tmp -rw------- 1 oweng users 2987 Jul 15 21:56 lun5zuzc.tmp -rw------- 1 oweng users 3913 Jul 15 21:56 lun5zuze.tmp -rw------- 1 oweng users 4021 Jul 15 21:56 lun5zuzg.tmp -rw------- 1 oweng users 6571 Jul 15 21:56 lun5zuzi.tmp -rw------- 1 oweng users 8474 Jul 15 21:56 lun5zuzk.tmp -rw------- 1 oweng users 7041 Jul 15 21:56 lun5zuzm.tmp -rw------- 1 oweng users 22136 Jul 15 21:56 lun5zuzo.tmp -rw------- 1 oweng users 8863 Jul 15 21:56 lun5zuzq.tmp -rw------- 1 oweng users 8926 Jul 15 21:56 lun5zuzs.tmp -rw------- 1 oweng users 8924 Jul 15 21:56 lun5zuzu.tmp -rw------- 1 oweng users 8910 Jul 15 21:56 lun5zuzw.tmp -rw------- 1 oweng users 8348 Jul 15 21:56 lun5zuzy.tmp -rw------- 1 oweng users 4073 Jul 15 21:56 lun5zv00.tmp -rw------- 1 oweng users 7106 Jul 15 21:56 lun5zv02.tmp -rw------- 1 oweng users 8778 Jul 15 21:56 lun5zv04.tmp /tmp/luodxjbp.tmp: total 1000 -rw-r--r-- 1 oweng users 1017765 Jul 16 18:26 luodxjbr.tmp -rw------- 1 oweng users 1686 Jul 16 18:26 luodxjbu.tmp /tmp/luodyn8h.tmp: total 1000 -rw-r--r-- 1 oweng users 1017765 Jul 16 18:26 luodyn8j.tmp -rw------- 1 oweng users 1686 Jul 16 18:27 luodyn8m.tmp (In reply to comment #0) > I have experienced this with LO Writer and LO Calc. Possibly with other > components too, but those two for sure. lun5zuyy.tmp in the above is a presentation. None of the files are terribly old, but some date from yesterday. The last two identical ones are likely from a recent crash that I am looking into. Confirmed for now. Status set to NEW. Platform set to All/All. Hopefully a developer can provide further information about what might be going on here.
On pc Debian x86-64 with master sources updated today, I don't reproduce this. I created a brand new file, changed an existing file, no tmp left. Any update with recent LO version (4.4.2 or at least 4.3.6)?
I completely stopped using LibreOffice for a while, and shifted my clients to another Office suite. I plan on re-evaluating LibreOffice very soon, and will update this bug report if that plan materializes.
I am having a hell lot of lu*.tmp in my /tmp. need to resolve this issue any updates?I there any way i can close/despose all the running instances?
Sugam: on which Linux distrib and with which LO 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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO 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! Warm Regards, QA Team Sat, 10 Sep 2016 16:48:27 +0200
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 Warm Regards, QA Team MassPing-NeedInfo-20161010