Created attachment 123760 [details] file that breaks the save as dialog While attempting to Save As, if the current working directory starts at or moves to a directory containing this specific file, Libreoffice crashes. I tested in both Calc and Writer components; the behavior was identical. It doesn't seem to matter what the current file contains (crash happened even on a brand-new file). The file appears to be a broken MacOS alias. I broke some fresh new aliases and was unable to reproduce, but copying this file still produced a directory-breaking file. Non-Libreoffice applications are not affected. I am using MacOS 10.11.3 (15D21) on a MacBook (Retina, 12-inch, Early 2015), in case that is relevant.
No problem here. Having the file in the same directory as a document being saved as works ok. Version: 5.1.1.3 Build ID: 89f508ef3ecebd2cfb8e1def0f0ba9a803b88a6d CPU Threads: 4; OS Version: Mac OS X 10.11.4; UI Render: default; Locale: en-US (en.UTF-8)
mslbork : what kind of file are you attempting to save ? Does the crash happen with any Save as file format, or only specific ones ?
Confirming with Version: 5.1.3.2 Build ID: 644e4637d1d8544fd9f56425bd6cec110e49301b CPU Threads: 2; OS Version: Mac OS X 10.11.5; UI Render: default; Locale: fr-FR (fr.UTF-8) 1) Downloaded the PDF file to /Downloads. 2) Then opened a Writer document in LO. 3) File > Save as, the Finder dialog appears, and then LO crashes. 4) Tried the same with a Calc file, same results. 5) Removed PDF from Downloads, repeated tests, no crash.
Looks like you got reproduction on your own, but as you noted it happens with (at least) empty documents in either Writer or Calc.
Alex: can you get debug output?
(In reply to Buovjaga from comment #5) > Alex: can you get debug output? If I get some time tomorrow, I'll see if I can get anything out of my build-nocheck dbgutil enabled build. What I would note is that the PDF is not a recognizable PDF by any of the apps I have on my Mac, whether it be Adobe Reader, Preview, Abby Fine Reader Pro, etc. In fact, the PDF in question provided by the OP is clearly incomplete, buggy or malformed. It is this malformed PDF that is causing the problem - maybe there is some kind of file type inspection performed by LO and stored in memory when LO accesses a directory ?
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
Still present, was not present in 3.3 so this could be worth a bibisect Version: 6.0.0.0.alpha1+ Build ID: 7e03c4eed72452fdfb87341214a21956c08ba969 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2017-10-25_23:45:02 Locale: en-US (en_US.UTF-8); Calc: group
Bibisected down to this, is this something for you to look at Norbert? Or are you just mentioned as author since you manage the bibisect repository? 101df9bdbbc3be25c3ff4f67944e333f5b714c27 is the first bad commit commit 101df9bdbbc3be25c3ff4f67944e333f5b714c27 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Mon Nov 11 11:43:54 2013 -0600 source 6319803762d051c4aa645692cde7245a1bbcf7ee source 6319803762d051c4aa645692cde7245a1bbcf7ee :040000 040000 2b8437ea60f9973b912efe979eae380b14c9b64a 172e04a13d0327cc1500c0a07c0bf7948515cf39 M LibreOffice.app eisa01s-MBP:bibisect_mac_lo42 eisa01$ git bisect log # bad: [c5b9a799f9d24eba970966f1afabfe931574e933] source 80373a6969fd8d3c19231041e465372cf03f53f2 # good: [e47ec366529846e008a4db27c8c507cdc7714c78] source 02021163dbbcc8904da0b2138c8b53684dcc8ab4 git bisect start 'master' 'bibisect_start' # bad: [fce5a68e80da196922e2f63d84c756a81f93fea7] source 4910c54a39703d19f5e36fa9c47938c1033f91e9 git bisect bad fce5a68e80da196922e2f63d84c756a81f93fea7 # bad: [b436ee2f3e51826d49dbd860bf3cf0c8b0a97c1d] source 28a6e1cf1bb9d6e8865736432dd32c12f0002cf9 git bisect bad b436ee2f3e51826d49dbd860bf3cf0c8b0a97c1d # bad: [227b285c1e4e13757feb1c83a5fdb62bcb0c672f] source 9ab800829b8a0e44824dc11276b54b1870bc5b2b git bisect bad 227b285c1e4e13757feb1c83a5fdb62bcb0c672f # bad: [101df9bdbbc3be25c3ff4f67944e333f5b714c27] source 6319803762d051c4aa645692cde7245a1bbcf7ee git bisect bad 101df9bdbbc3be25c3ff4f67944e333f5b714c27 # good: [e0bc7ceaaa019ebee406b67ada9c376c6c4096ec] source 0badc400706d059381ec396c33dd0760042c4c0b git bisect good e0bc7ceaaa019ebee406b67ada9c376c6c4096ec # good: [f2cb8dedd51fbe990c62bae2087d35c287cf3f12] source d209e133191853f12557d879d1dcda7a0309dac6 git bisect good f2cb8dedd51fbe990c62bae2087d35c287cf3f12 # good: [88622dec19c9b9fc723e58ece864af821384807c] source d60d1300f56d008056ccc8739e67495ba31cad97 git bisect good 88622dec19c9b9fc723e58ece864af821384807c # good: [062a701df1abaceeaac296f2be9a330b5e65dc27] source 9b4ea9fdfc0c780bead46fde74a71078e542c493 git bisect good 062a701df1abaceeaac296f2be9a330b5e65dc27 # good: [880343540bcce9d1a53c2efd44632f383ff97e18] source 32345f9963dd2900da174d9c7dec6a070fce8f9c git bisect good 880343540bcce9d1a53c2efd44632f383ff97e18 # good: [2873d071fbd2d72d3ebfb2152a4ce24f47f768b6] source 6d51f9f948c5bf877ec8a53e3716f00fe5e81a23 git bisect good 2873d071fbd2d72d3ebfb2152a4ce24f47f768b6 # good: [32fd2097c730a4bb603d9afe477568f42fac683a] source a05c0cfa40001aa1f4247a4e9f1fcefad7e7cf88 git bisect good 32fd2097c730a4bb603d9afe477568f42fac683a # first bad commit: [101df9bdbbc3be25c3ff4f67944e333f5b714c27] source 6319803762d051c4aa645692cde7245a1bbcf7ee
(In reply to eisa01 from comment #9) > Bibisected down to this, is this something for you to look at Norbert? Or > are you just mentioned as author since you manage the bibisect repository? Yes, he is the author of the repo. Somehow does not seem https://cgit.freedesktop.org/libreoffice/core/commit/?id=6319803762d051c4aa645692cde7245a1bbcf7ee is the commit to blame.
I tried to bibisect this again, found a new bad commit, tested it, turned out the previous was also bad, tried again, turned out to work after all, tried again and the first good was the previous which no longer worked... So I think this is not bibisectable Still present in master as of March 26 2018
eisa01: can you get debug output for the crash? https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Mac_OSX
Created attachment 141235 [details] Backtrace Backtrace from Version: 6.1.0.0.alpha0+ Build ID: a488c7ad2763b944713997911c1ddb0315d8c93f CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-03-26_00:38:29 Locale: en-US (en_US.UTF-8); Calc: group
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I can't seem to repro this any more, however I haven't tried the exact same build as I did back then... Version: 6.3.0.0.alpha0+ Build ID: ea9c13be02ba731074fa4207944ff7df40a0fb5c CPU threads: 2; OS: Mac OS X 10.13.6; UI render: default; VCL: osx; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2019-04-10_20:43:17 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded Version: 6.0.0.3 Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 2; OS: Mac OS X 10.13.6; UI render: default; Locale: en-US (en_US.UTF-8); Calc: group
(In reply to eisa01 from comment #15) > I can't seem to repro this any more, however I haven't tried the exact same > build as I did back then... mslbork: as eisa01 is unable to repro, could you please test with a recent release, preferably 6.2.3?
(In reply to Buovjaga from comment #16) > (In reply to eisa01 from comment #15) > > I can't seem to repro this any more, however I haven't tried the exact same > > build as I did back then... > > mslbork: as eisa01 is unable to repro, could you please test with a recent > release, preferably 6.2.3? Eh, accidentally commented in "silent mode" so asking again.
I managed to repro this after all, but I had to download the file via Firefox as Safari seems to have issues with bugzilla - e.g., .doc files saved as .dot and filename referring UTF8 and so on Version: 6.3.0.0.alpha0+ Build ID: ea9c13be02ba731074fa4207944ff7df40a0fb5c CPU threads: 2; OS: Mac OS X 10.13.6; UI render: default; VCL: osx; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2019-04-10_20:43:17 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
This works fine. Probably fixed by moving to the native save as dialogs? Version: 6.4.3.5 Build ID: 4db9852e73d9e9d662fc8a2783bace79addf1805 CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded