Make an empty table in an Impress presentation. Then right click on it and select "cut". Libreoffice will immediately crash.
Ubuntu 14.04 x64
LibreOffice 188.8.131.52 release
@Brandon - can you try 184.108.40.206 with a fresh profile: https://wiki.documentfoundation.org/UserProfile
no crash on Win7x64 using 220.127.116.11
Also not reproduced on OSX / 18.104.22.168 release and 4.4 master
As above, please try again with a clean profile and let us know if it still happens.
If it does, it would be helpful to have a backtrace from the crash. If you don't know how to do that, please see:
Created attachment 107673 [details]
It still occurs after I made a fresh profile. But I noticed it only crashes with certain files (an empty file won't crash, but one with several slides full of pictures, diagrams, etc. will). I've attached a backtrace.
Please attach one of those files.
Created attachment 107674 [details]
File that will crash
I've attached it. Pictures removed to reduce size, so lots of empty slides. But the crash can still be reproduced with the attached file. Make a new slide, choose to insert a table, try to cut the table and it will crash.
Confirmed on OSX and Linux / LO 22.214.171.124 using the test file
I can't however immediately reproduce this on master. If it's been fixed then something may need backporting
-> OS: All
-> Importance: High
This was fixed on master by the combination of the following two commits:
Author: Michael Stahl <firstname.lastname@example.org>
Date: Fri Aug 29 19:09:29 2014 +0200
n#708518: sd: check that master page matches when setting parent style
In ODF import it happened that the parent style of "outline2" etc.
was always set to the "outline1" style of the first master page in
the document, but it should be the "outline1" style of the same master
page as the "outline2".
(regression from e955433c3574cb602dedba96bc645898f97858bf)
Author: Caolán McNamara <email@example.com>
Date: Tue Sep 9 15:32:49 2014 +0100
crashtest: sep should be curSep
At first glance these look like good candidates for backporting - need to build a 4.3 to check
Back to confused. Those two patches have already been cherry-picked onto 4.3 and are in 126.96.36.199, so there must be another element to fixing the crash that hasn't been backported yet
In the daily dbgutil bibisect repo, I can confirm that the crash goes away between the versions 2014-09-09 and 2014-09-10, only to be replaced by the misbehaviour reported in bug 85398.
After Matthew's work, I do not know how it can help, but in the 43-all
bibisect repo, I see from `git bisect bad`:
642edb6eec6b6ba276c33b60cb38d56411e70f4a is the first bad commit
Author: Bjoern Michaelsen <firstname.lastname@example.org>
Date: Tue May 20 14:45:24 2014 +0000
Author: Thomas Arnhold <email@example.com>
AuthorDate: Sat May 10 18:19:39 2014 +0200
Commit: Thomas Arnhold <firstname.lastname@example.org>
CommitDate: Sun May 11 01:55:39 2014 +0200
:100644 100644 8f7b406390da8ecd41a0a0703ccb3c596d0270ad 7676516ae2308ce13b4a9a89ad5bd4de2cefa380 M ccache.log
:100644 100644 100b1b3f429b84659c9ea89781c7af862b5717ac c796aef63228c8907475fa817076f337fee7dc5a M commitmsg
:100644 100644 3feb51566ae73b1658d73efe9aa7c8d7fac0e397 ade30f1e4fe61fed4f3695ed7e0e630aa6b58826 M make.log
:040000 040000 0f190a6bc7977d598e6b83e40329fd725757c977 9595318cb9a2736916f60d50dfdf3bcefce1781a M opt
and from `git bisect log`::
# bad: [423a84c4f7068853974887d98442bc2a2d0cc91b] source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e
# good: [65fd30f5cb4cdd37995a33420ed8273c0a29bf00] source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932
git bisect start 'latest' 'oldest'
# good: [e02439a3d6297a1f5334fa558ddec5ef4212c574] source-hash-6b8393474974d2af7a2cb3c47b3d5c081b550bdb
git bisect good e02439a3d6297a1f5334fa558ddec5ef4212c574
# good: [4850941efe43ae800be5c76e1102ab80ac2c085d] source-hash-980a6e552502f02f12c15bfb1c9f8e6269499f4b
git bisect good 4850941efe43ae800be5c76e1102ab80ac2c085d
# good: [a900e72b6357882284c5955bdf939bf14269f5fb] source-hash-dd1050b182260a26a1d0ba6d0ef3a6fecc3f4e07
git bisect good a900e72b6357882284c5955bdf939bf14269f5fb
# skip: [e80660c5a1d812cd04586dae1f22767fc3778c4a] source-hash-07c60c8ee2d1465544a6a39e57bc06b3690b8dfb
git bisect skip e80660c5a1d812cd04586dae1f22767fc3778c4a
# good: [df9bcaed2faa2a8d11b19f877cdff3a12a887278] source-hash-6ba9692d8bbe3e3c245aca9a7c928e81178d05f1
git bisect good df9bcaed2faa2a8d11b19f877cdff3a12a887278
# good: [741197a13a361480f59eeb3bd1401f984f49f1c0] source-hash-9a61470eb1fa161cba70f2e9c4ea8817dc7f617e
git bisect good 741197a13a361480f59eeb3bd1401f984f49f1c0
# bad: [882db5e268e28962bdf805c820a5e031b0df9936] source-hash-383dccc094f8c8c07b4298ce0b7406d18cd61cee
git bisect bad 882db5e268e28962bdf805c820a5e031b0df9936
# good: [17f897f0e3734070f0e5c6abd39f2f907f42ac86] source-hash-4041263bde64dcc9a9a225d7f5a171f3b0455724
git bisect good 17f897f0e3734070f0e5c6abd39f2f907f42ac86
# good: [5c9e81ec77cd98f952434decf83ec9820d736e56] source-hash-94e3f3e5015e53b5f3c8e5775b668e0bc12ab457
git bisect good 5c9e81ec77cd98f952434decf83ec9820d736e56
# bad: [642edb6eec6b6ba276c33b60cb38d56411e70f4a] source-hash-2bac61013e57013bccac8c9d76482b34b5db7f69
git bisect bad 642edb6eec6b6ba276c33b60cb38d56411e70f4a
# first bad commit: [642edb6eec6b6ba276c33b60cb38d56411e70f4a] source-hash-2bac61013e57013bccac8c9d76482b34b5db7f69
Same bt than fdo put in See Also.
*** Bug 84509 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 82681 ***
Migrating Whiteboard tags to Keywords: (bibisected)