| Summary: | open file doesn't work anymore with my *.odt files in Writer | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Bernhard <mynewjob> |
| Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | barta, serval2412 |
| Priority: | medium | ||
| Version: | 4.2.3.3 release | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
|
Description
Bernhard
2014-05-07 00:12:01 UTC
did you try resetting user profile? https://wiki.documentfoundation.org/UserProfile what about Calc, Impress etc. etc.? -------- Original-Nachricht -------- Betreff: Re: [Bug 78364] open file doesn't work anymore with my *.odt files in Writer Datum: Wed, 07 May 2014 10:28:56 +0200 Von: Wodi <jwmail@t-online.de> An: bugzilla-daemon@freedesktop.org Hello, - I did reset the user profile as explained within your link. Opening a file afterwards has the same behaviour as before the reset. Below you see the last log-entry after this try: [ 599.825075] soffice.bin[2171]: segfault at 39 ip b66b2b10 sp bff8b530 error 4 in libmergedlo.so[b455f000+2ffd000] - Never used any other Office application so far. - My current OS is Ubuntu 14.04 LTS installed. I worked some weeks with writer and my files before this behaviour happened first. - Additionally I tried opening one file with Writer of LibreOffice 3.5.2.2 from within a live distribution Linux Mint 13 Maya. Here is no problem to open a file several times. Is Read-Only because of the existing lock-file. - Ran chkrootkit from Kali Live distibution to check the Ubuntu partition. Below see the results. Don't know whether there may be a connection?! Searching for Suckit rootkit... Warning: /media/efa2e102-d07f-464d-8fc7-ea31c5de8d6b/sbin/init INFECTED Searching for suspicious files and dirs, it may take a while... The following suspicious files and directories were found: /media/efa2e102-d07f-464d-8fc7-ea31c5de8d6b/usr/lib/python2.7/dist-packages/PyQt4/uic/widget-plugins/.noinit /media/efa2e102-d07f-464d-8fc7-ea31c5de8d6b/usr/lib/pymodules/python2.7/.path Am 07.05.2014 07:25, schrieb bugzilla-daemon@freedesktop.org: > tommy27 <mailto:barta@quipo.it> changed bug 78364 > <https://bugs.freedesktop.org/show_bug.cgi?id=78364> > What Removed Added > CC barta@quipo.it > > *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=78364#c1> > on bug 78364 <https://bugs.freedesktop.org/show_bug.cgi?id=78364> from > tommy27 <mailto:barta@quipo.it> * > did you try resetting user profile? > https://wiki.documentfoundation.org/UserProfile > > what about Calc, Impress etc. etc.? > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. > Where do your odt come from? Same machine or another one? Are the odt on local hard disk or on some network share? Do you reproduce this problem if you create a brand new file (just containing "test" for example) and open it again? Would it be possible you attach a file? (which doesn't contain any confidential/private part since the attachments are automatically made public) (Please don't answer directly from your emailer but from bugzilla). First - I did some experiments. 1) Some odt-files: Deleting the lock-file and trying to open the odt again doesn't work. The lock-file is built again immediatly. 2) Some othe odt-files: Deleting the lock-file and trying to open the odt again works once. Closing the odt and tying to open again fails. The lock-file is built again immediatly. 3) Copied the odt of case 2) to another directory. Opening the odt there works once as in case 2). 3) Copied the odt of case 2) to a usb-hd. Opening the odt there fails immediatly as in case 1). 4) One of my odts works always - no failure. Is it correct, that the odt-files cannot be the reason? Because deleting the lock-file and opening a file works with the live distribution on the same machine. Doing the same with the installed Writer, the lock-file is built again and the odt-file keep closed. Please find the answers for your questions below... Am 08.05.2014 00:33, schrieb bugzilla-daemon@freedesktop.org: > Julien Nabet <mailto:serval2412@yahoo.fr> changed bug 78364 > <https://bugs.freedesktop.org/show_bug.cgi?id=78364> > What Removed Added > Status UNCONFIRMED NEEDINFO > CC serval2412@yahoo.fr > Ever confirmed 1 > > *Comment # 3 <https://bugs.freedesktop.org/show_bug.cgi?id=78364#c3> > on bug 78364 <https://bugs.freedesktop.org/show_bug.cgi?id=78364> from > Julien Nabet <mailto:serval2412@yahoo.fr> * > Where do your odt come from? Same machine or another one? > Are the odt on local hard disk or on some network share? All affected odt-files are build by myself on the local hard disk of the same machine. Some files written by myself, some files additionally contain copied text from web sides. > > Do you reproduce this problem if you create a brand new file (just containing > "test" for example) and open it again? I built a new odt-file with some text, filled some document description and set the mark to include the fonts as I do for all the other. This file works (3 tries) - I can open / modify / store / open / close / open ... > > Would it be possible you attach a file? (which doesn't contain any > confidential/private part since the attachments are automatically made public) Attached 2 Files: Mp3DateienAnpassen_Linux.odt is a file of case 2). BIOS-Pieptoene.odt is a file of case 4). > > (Please don't answer directly from your emailer but from bugzilla). I don't understand what that means. I use thunderbird downloading this mail. I open an read it. Press the answer button, write my stuff and send. Is that the wrong way?? > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. > Hello, additionally here the segfaults happened during my experiments described in my previous answer. May 12 11:41:22 Travelmate6292 kernel: [ 2164.306058] soffice.bin[2948]: segfault at 6fd16814 ip b6724b1a sp bf8902b0 error 4 in libmergedlo.so[b45d1000+2ffd000] May 12 11:41:45 Travelmate6292 kernel: [ 2186.846100] soffice.bin[2984]: segfault at 69a16814 ip b66c1b1a sp bfe0d720 error 4 in libmergedlo.so[b456e000+2ffd000] May 12 11:41:58 Travelmate6292 kernel: [ 2200.172917] soffice.bin[3022]: segfault at 3b ip b66ceb10 sp bfddda20 error 4 in libmergedlo.so[b457b000+2ffd000] May 12 11:42:25 Travelmate6292 kernel: [ 2227.107232] soffice.bin[3089]: segfault at 73016814 ip b6757b1a sp bfcf5040 error 4 in libmergedlo.so[b4604000+2ffd000] May 12 11:42:34 Travelmate6292 kernel: [ 2235.666659] soffice.bin[3124]: segfault at 3b ip b679fb10 sp bffb8de0 error 4 in libmergedlo.so[b464c000+2ffd000] May 12 11:42:42 Travelmate6292 kernel: [ 2243.541884] soffice.bin[3158]: segfault at 3a ip b66deb10 sp bfb8cb80 error 4 in libmergedlo.so[b458b000+2ffd000] May 12 11:42:44 Travelmate6292 kernel: [ 2246.426871] perf samples too long (2515 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 May 12 11:43:28 Travelmate6292 kernel: [ 2289.480184] soffice.bin[3227]: segfault at 3a ip b677bb10 sp bfe1f130 error 4 in libmergedlo.so[b4628000+2ffd000] May 12 11:48:49 Travelmate6292 kernel: [ 2610.477828] soffice.bin[3267]: segfault at 75916814 ip b6780b1a sp bff43f60 error 4 in libmergedlo.so[b462d000+2ffd000] ------------------------------------------------------------------------------------------------ Following the segfaults happened while testing the odt on the usb-hd. May 12 11:49:29 Travelmate6292 udisksd[1856]: Mounted /dev/sdc1 at /media/wodi/BlauData_ntfs on behalf of uid 1001 May 12 11:49:47 Travelmate6292 kernel: [ 2668.822070] soffice.bin[3383]: segfault at 3b ip b66f8b10 sp bf855cf0 error 4 in libmergedlo.so[b45a5000+2ffd000] May 12 11:53:18 Travelmate6292 kernel: [ 2879.643688] soffice.bin[3425]: segfault at 77816814 ip b679fb1a sp bfec8670 error 4 in libmergedlo.so[b464c000+2ffd000] May 12 12:03:08 Travelmate6292 kernel: [ 3470.427645] soffice.bin[3642]: segfault at 75216814 ip b6779b1a sp bf837e10 error 4 in libmergedlo.so[b4626000+2ffd000] Am 08.05.2014 00:33, schrieb bugzilla-daemon@freedesktop.org: > Julien Nabet <mailto:serval2412@yahoo.fr> changed bug 78364 > <https://bugs.freedesktop.org/show_bug.cgi?id=78364> > What Removed Added > Status UNCONFIRMED NEEDINFO > CC serval2412@yahoo.fr > Ever confirmed 1 > > *Comment # 3 <https://bugs.freedesktop.org/show_bug.cgi?id=78364#c3> > on bug 78364 <https://bugs.freedesktop.org/show_bug.cgi?id=78364> from > Julien Nabet <mailto:serval2412@yahoo.fr> * > Where do your odt come from? Same machine or another one? > Are the odt on local hard disk or on some network share? > > Do you reproduce this problem if you create a brand new file (just containing > "test" for example) and open it again? > > Would it be possible you attach a file? (which doesn't contain any > confidential/private part since the attachments are automatically made public) > > (Please don't answer directly from your emailer but from bugzilla). > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. > Hello, don't know, whether you received my last answer with the two attached odts. Because I got an indication, that the attachement exceededs a size limit. After that I analysed, that the fonts included into the documents expand my odts. Then I tried to get the fonts out of the files - difficult - because I could not open the odt. But I detected the following sequence: 1) I open a working odt-file and close it again. 2) I delete the lock-file of an faulty odt. 3) Now I can open the faulty odt. 4) Close the odt. 5) Trying open the faulty odt second time fails - lock file is built again. Changed sequence, tried to throw the fonts out of the odt: 1) I open a working odt-file and close it again. 2) I delete the lock-file of an faulty odt. 3) Checking the filesize of the odt: size = X 4) Now I can open the faulty odt. 5) Unmark the including of the fonts into the odt. 6) Close the odt. (cannot save, because the save-button is not active) 7) Checking the filesize of the odt: size = X 8) Trying open the faulty odt second time fails - lock file is built again. Changed sequence, again tried to throw the fonts out of the odt: 1) I open a working odt-file and close it again. 2) I delete the lock-file of an faulty odt. 3) Checking the filesize of the odt: size = X 4) Now I can open the faulty odt. 5) Unmark the including of the fonts into the odt. 6) Editing some text. That activates the save button. 5) Saving and closing the odt. 3) Checking the filesize of the odt: size = much smaller than X (I think the fonts are out now) 4) Now this odt is a working odt. I can open it always. After that I checked some odts: All checked working odts have no fonts included. All checked faulty odts have the fonts included. Question: Is it a wrong way including fonts into the odts? Maybe the result can be reached on another way of doing this. Ok, to continue my work with these odts, I throw the fonts out of them. But I can't edit the files on PCs of my friends, where the fonts are not available. Maybe the fonts are not installed or my friends don't want to have them being installed. Does the library mentioned within the segfault logs has anything to do with "including font[s] into an odt"? If I attach an odt that doesn't work (with included fonts), it always exceeds an email-size- or attachement-size-limit. Am 08.05.2014 00:33, schrieb bugzilla-daemon@freedesktop.org: > Julien Nabet <mailto:serval2412@yahoo.fr> changed bug 78364 > <https://bugs.freedesktop.org/show_bug.cgi?id=78364> > What Removed Added > Status UNCONFIRMED NEEDINFO > CC serval2412@yahoo.fr > Ever confirmed 1 > > *Comment # 3 <https://bugs.freedesktop.org/show_bug.cgi?id=78364#c3> > on bug 78364 <https://bugs.freedesktop.org/show_bug.cgi?id=78364> from > Julien Nabet <mailto:serval2412@yahoo.fr> * > Where do your odt come from? Same machine or another one? > Are the odt on local hard disk or on some network share? > > Do you reproduce this problem if you create a brand new file (just containing > "test" for example) and open it again? > > Would it be possible you attach a file? (which doesn't contain any > confidential/private part since the attachments are automatically made public) > > (Please don't answer directly from your emailer but from bugzilla). > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. > Hello, found out some news about the behaviour with these faulty odts. I build an odt, insert some text, switch on including fonts, edit some text and save the document. Now I have an odt including the fonts. I can open it always, as long as I don't save it again!!! But if I open the odt again, edit some text and save the document, afterwards the faulty behaviour begins. Am 08.05.2014 00:33, schrieb bugzilla-daemon@freedesktop.org: > Julien Nabet <mailto:serval2412@yahoo.fr> changed bug 78364 > <https://bugs.freedesktop.org/show_bug.cgi?id=78364> > What Removed Added > Status UNCONFIRMED NEEDINFO > CC serval2412@yahoo.fr > Ever confirmed 1 > > *Comment # 3 <https://bugs.freedesktop.org/show_bug.cgi?id=78364#c3> > on bug 78364 <https://bugs.freedesktop.org/show_bug.cgi?id=78364> from > Julien Nabet <mailto:serval2412@yahoo.fr> * > Where do your odt come from? Same machine or another one? > Are the odt on local hard disk or on some network share? > > Do you reproduce this problem if you create a brand new file (just containing > "test" for example) and open it again? > > Would it be possible you attach a file? (which doesn't contain any > confidential/private part since the attachments are automatically made public) > > (Please don't answer directly from your emailer but from bugzilla). > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. > Bernhard: Please don't answer from Thunderbird. You can read the comments from your emailer, it's normal since Bugzilla sends the comments to the people who created the bugtracker and people put in CC List of the bugtracker. To answer, click on this link: https://bugs.freedesktop.org/show_bug.cgi?id=78364# and add a comment. To understand what I mean, just take a look to your comments in https://bugs.freedesktop.org/show_bug.cgi?id=78364 You also may see there's no attachment to the bugtracker. About >3MB attachments, I read about https://wiki.documentfoundation.org/QA/Bugzilla-Attachments but didn't understand how it worked. Anyway, could you try this: - create your document without any specific fonts and test if open/save/close/reopen works - create your document with 1 (not all of them) specific font and test if open/save/close/reopen works The pb could be 1 (or more) of the fonts. Could you give name of them + link where you retrieved them? The font I use is "Liberation Serif". I didn't retrieve it from anywhere. It is within the list of selectable fonts. Within some documents I used "Times New Roman" (Don't know how it entered my documents???). Couldn't find this font within the list to select it, but when the cursor was set within text formatted with "Times New Roman", this name was displayed within the font field on the formats symbol bar. When I then opened the font list, the font was not listed to select it.
Within my "Options.Basic Fonts" I found listed "Times New Roman" and "Arial". I changed it to Standard: "Liberation Serif" and "Libaration Sans".
Then I built a new Document with some Text in "Liberation Serif". Set the option to include the fonts into the document and saved it. Now I tried to open it with double click from within the filemanager SpaceFM.
1) Open failed and a lockfile was built.
2) Then deleted the lockfile and tried again to open --> OK.
Closed it unchanged (no save).
3) Then open and close unchanged again works several times (2-4 times).
4) Then open failed and a lockfile was built.
5) Then deleted the lockfile and tried to open --> OK.
Did some changes and closed with save.
6) Then open failed immediatly.
Thank you Bernard for your feedback, I put it back to UNCONFIRMED since I don't have more questions. I must recognize I'm a bit lost with all this: several distribs used, use of chroot, suspicious file, file manager I don't know at all (not even heard about it), ntfs partition, etc. Times New Roman/Arial used by default whereas you're on Linux; there are too much variables on the equations, for the moment, I think it's more a problem of the system but can't be sure of course. If you've got a spare machine, just install a system from scratch (a mainstream distrib: Debian, Mint, Ubuntu, ArchLinux, etc. on filesystem like ext3/ext4 or other mainstream Linux filesystem) and give it a new try (without changing any font settings first) + LibreOffice. Use LO package provided by your distrib or from official website: http://www.libreoffice.org/download/libreoffice-fresh/ 1) Very basic test: - create a brand new file - type test - save - close - reopen this file 2) basic test: - change your font settings - create a brand new file - type test - save - close - reopen this file 3) Normal test - retrieve an old file your have - add a space to a word - save - close - reopen this file Before keeping on, give results of these 3 tests. Of course, if 1) fails, don't keep on with the others. The final goal is to find the element which triggers the problem, so we must advance step by step. BTW, having a lock file when a file is opened, is completely normal. When closing, this lock file must disappear. (In reply to comment #10) > Thank you Bernard for your feedback, I put it back to UNCONFIRMED since I > don't have more questions. > I must recognize I'm a bit lost with all this: several distribs used, use of > chroot, suspicious file, file manager I don't know at all (not even heard > about it), ntfs partition, etc. Times New Roman/Arial used by default > whereas you're on Linux; there are too much variables on the equations, for > the moment, I think it's more a problem of the system but can't be sure of > course. > > If you've got a spare machine, just install a system from scratch (a > mainstream distrib: Debian, Mint, Ubuntu, ArchLinux, etc. on filesystem like > ext3/ext4 or other mainstream Linux filesystem) and give it a new try > (without changing any font settings first) + LibreOffice. Use LO package > provided by your distrib or from official website: > http://www.libreoffice.org/download/libreoffice-fresh/ > 1) Very basic test: > - create a brand new file > - type test > - save > - close > - reopen this file > 2) basic test: > - change your font settings > - create a brand new file > - type test > - save > - close > - reopen this file > 3) Normal test > - retrieve an old file your have > - add a space to a word > - save > - close > - reopen this file > > Before keeping on, give results of these 3 tests. Of course, if 1) fails, > don't keep on with the others. > The final goal is to find the element which triggers the problem, so we must > advance step by step. > > BTW, having a lock file when a file is opened, is completely normal. When > closing, this lock file must disappear. Hi Julien, first thank you for your help and patience. Meanwhile a workaround works. I deleted the fonts "Times New Roman" and "Arial" out of my documents and out of LibreOffice (wherever they were listed. Both fonts seem not to be used fonts within Ubuntu 14.04 (that I use) and they are not selectable within a new writer document. Don't know whether they enter my documents when I copied some text from a website or from a foreign document. However, now I can open, edit and save my writer-documents NEARLY without problems. One thing is still an error for me: When I set the option "save fonts within the document" and OK, writer doesn't detect this as a change and doesn't activate the save button. I have to edit some text to be able to save my document. Installing a new Ubuntu is currently too big for me. I installed many additional programs, entered some softlink-concepts ... Because of the running workaround I don't want to install complete systems to analyse this error. If you know additional checks for me to find the error within my current system, I enjoy to do them. Thank you, Bernhard Bernhard: Thank you for your new feedback. Perhaps there were a problem with these 2 fonts (too old, corrupted or something). Let's close this tracker and I let you open a new one specific to the problem "Embed fonts in the document". I'll confirm this one since I can reproduce this problem with master sources (future 4.4.0) on pc Debian x86-64. Also if you want to use "Arial" and "Times New Roman" fonts, you can create another specific bugtracker and include links to download them You must have in mind that 1 bugtracker must correspond to 1 problem. The goal is to manager more easily bugs for QA and devs. |