on my laptop running leap 15.6 with KDE I have two users, I have a common NTFS partition to use the same files, in the past I used libreoffice in both users flawlessly, (libreoffice version 24.8.4.2)
using user1 I open calcfile1.ods (or any other file) and libreoffice works,
in user2 if I open the same calcfile1.ods libreoffice ask me to recover it (if I try to open any other file libreoffice ask me to recover calcfile1.ods), I click yes and it is reproposed to recover again and again, if I click to not recover it seems to work but when I try to open calcfile1.ods (or any other file) from the file>open menu libreoffice crash.
I tried:
to start only with user1 and it works
to start only with user2 and it crash
to start with user1 and switching another session with user2 and it crash
to rename /home/user2/.config/libreoffice folder and it crash
to start in --safe-mode and it crash
pla6TW@plaTW:~> libreoffice --safe-mode
kf.kio.filewidgets.kfilefiltercombo: Could not find filter "*|All files "
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
kf.coreaddons: "Could not load plugin from /usr/lib64/qt5/plugins/webarchivethumbnail.so: Failed to extract plugin meta data from '/usr/lib64/qt5/plugins/webarchivethumbnail.so'"
DEBUG: FC_WEIGHT didn't match
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
DEBUG: FC_WEIGHT didn't match
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
DEBUG: FC_WEIGHT didn't match
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
DEBUG: FC_WEIGHT didn't match
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
DEBUG: FC_WEIGHT didn't match
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
QPngHandler: Failed to parse ICC profile
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
QPainter::end: Painter ended with 2 saved states
KCrash: Application 'soffice.bin' crashing...
KCrash: Attempting to start /usr/lib/drkonqi
Unable to find file for pid 30092 expected at "kcrash-metadata/30092.ini"
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
QSocketNotifier: Invalid socket 19 and type 'Read', disabling...
QSocketNotifier: Invalid socket 36 and type 'Read', disabling...
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
pla6TW@plaTW:~>
When you open a file <name_of_file> in LibreOffice, a lock file named ~lock.<name_of_file># is created in the same directory. When the file is closed, that lock file is deleted.
When LO crashes, that lock file is not deleted and on restart LO finds it and asks if you want to recover, so look for lock files in your directory and possibly delete them and retry.
One caveat, the lock files have ownership and permissions of the user that last opened the LO file, so if you use two users some trouble might arise. Also, NTFS mounted on Linux has strange behaviour unless you tweaked your install and that might compound to your problem.
hi manythanks,
NTFS becouse is dual boot with windows
I use windows rarely (the last time 6 months ago) with other programs and libreoffice is not installed in windows
Hi and manythanks,
I tried to delete ~lock.calcfile1 file in the NTFS partition but it didn’t work
I deleted all the ~lock.<name_of_file> in the NTFS partition but it didn’t work
no problems to delete ~lock.<name_of_file> files
I deleted /home/user2/.config/libreoffice folder and check if there was ~lock.<name_of_file> in /home/user2 but there wasn’t that files
I logged out and in but it didn’t work
I made a new user and everything works
NTFS could be a problem but if it works wit two user and not works with user2 push me to suppose that is more a /home/user2 problem than NTFS problem
pla6TW@plaTW:~> libreoffice --norestore
kf.kio.filewidgets.kfilefiltercombo: Could not find filter "*|All files "
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
DEBUG: FC_WEIGHT didn't match
Unspecified Application Error
KCrash: Application 'soffice.bin' crashing...
KCrash: Attempting to start /usr/lib/drkonqi
QSocketNotifier: Invalid socket 7 and type 'Read', disabling...
QSocketNotifier: Invalid socket 30 and type 'Read', disabling...
QSocketNotifier: Invalid socket 36 and type 'Read', disabling...
Unable to find file for pid 32137 expected at "kcrash-metadata/32137.ini"
Unable to start Dr. Konqi
Re-raising signal for core dump handling.
pla6TW@plaTW:~>
this the working user that advised me that the file was locked by another user and gave me the choises to open read only, open a copy or open, I choosen open
pla@plaTW:~> libreoffice --norestore
kf.kio.filewidgets.kfilefiltercombo: Could not find filter "*|All files "
pla@plaTW:~>
I’m confused, since there is no file specified on that command line.
Anyway looks like user pla6TW left something behind because of the crash and user pla correctly asked what to do.
So user pla works, a new user works, so something must be wrong with user pla6TW.
Might not be “a file” but a “permission on a file”.
BTW DEBUG: FC_WEIGHT didn't match might arise when trying to open PDF or Postscript files in an application that doesn’t have the correct fonts installed or something.
I would also test with a file not stored on an NTFS partition (just in case…).
the file has been opened clicking in the libreoffice windows opened after the command and then closed
yes, the operation had been:
from user pla switched to pla6TW
launched the libreoffice --norestore command
opened the file and libreoffice crshed
logout from user pla6TW
logged in user pla
launched the libreoffice --norestore command
well I tried this:
logged in pla user, created a new file testfile1.ods in /home/pla, opened and works
copyed in NTFS partition, opened and works
logged in pla6TW user, copyed testfile1.ods from NTFS partition to /home/pla6TW
deleted /home/pla6TW/.config/libreoffice folder
logged out pla6TW user
logged in pla user
logged in pla6TW user
this opening testfile1.ods file in /home/pla6TW, it works
this opening testfile1.ods file in NTFS partition, it works
this opening another file in the same folder where previously crashed in NTFS partition, it works
this opening the file that previously crashed in NTFS partition, it works
opening files everywhere and in every user clicking on them libreoffice now works perfectly
I don’ know what has been the magic but many thanks
deleting pla6TW .config and opening a clean file (in pla6TW home) restored a clean libreoffice profile;
no crash > no leftovers in NTFS dir > everybody (pla and pla6TW) is happy.
I still think that NTFS is involved one way or another; when mounted on linux every file saved there has faked permissions and if accidentally two users open the same file at the same time odd things happen (note that it might be just a ~lock. file).
And if IIRC those files will be read by Win* as with everybody/everybody permissions, which might not be what users intended.
So, if you are the only real user of the system, just be careful. If there are real different users you might refrain from mounting NTFS on linux, or dig deeper and configure NTFS accordingly.
I think you are right, NTFS is in some way involved,
I’m not the only real user, often I use both profiles pla and pla6TW but I have other two profiles when sometimes my nephews and my girl friend use my laptop, I will be careful closing opened files when I switch to other users also without closing the previous.
I use NTFS becouse sometimes I have to use windows, and the EXT2 in windows works very worst than NTFS in linux, libreoffice is not installed but may be it can happen, may be I have to have two partitions, one EXT4 and one NTFS and when I use windows copy the interested files on NTFS and use there in windows and then transfere in EXT when I am in linux but seems annoying so it will result difficult to respect in some cases
If the partition to share files is not too big, FAT or vFAT might be an option. It has other limitations (no journaling is the most important IMHO) but linux support is good.
As for NTFS, too many years since I last dual-booted so I let others to advise.
