Problem description: After drag & drop of slides from another document, switching back to Normal view from Slide Sorter doesn't work properly, and then Impress crashes. Steps to reproduce: 1. Create or open two Impress documents. 2. Switch to slide sorter view in both documents. 3. Drag and drop a slide from one document to the other. 4. In the document where the slides were dropped, switch back to normal view. Current behavior: After switching back to Normal, moving the mouse cursor over the slide area results in the thumbnails from Slide Sorter showing up on top of the slide contents, and the slide contents can't be interacted with. Not long after, the application crashes. See screencast: http://www.youtube.com/watch?v=TWpGSZqLHeM Expected behavior: Normal view works ... normally. Crashes don't happen. Platform (if different from the browser): Ubuntu 10.10, Thinkpad T410 Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.83 Safari/535.11
A workaround I'm using and seems to work is to do the drag-and-drop of slides into the "slides" pane of the destination document to the other rather than into the slide sorter.
Similar to Bug 50147 - "EDITING: Crash after resorting slides". Related?!
(In reply to comment #0) > Current behavior: > After switching back to Normal, moving the mouse cursor over the slide area > results in the thumbnails from Slide Sorter showing up on top of the slide > contents, and the slide contents can't be interacted with. Not long after, the > application crashes. See screencast: http://www.youtube.com/watch?v=TWpGSZqLHeM I can confirm the behavior but no crashes. Checked with: LO 3.5.4.2 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit
I can confirm crashes u(In reply to comment #3) > I can confirm the behavior but no crashes. I can confirm crashes upon exiting Impress. WinDbg session attached.
Created attachment 62288 [details] Bug 48101 - WinDbg session with FAILED_SOURCE_CODE Attached full WinDbg session with FAILED_SOURCE_CODE. Hope this helps.
NEW as bug confirmed and bt attached.
Adding myself as QA just for easy query, hoping to get someone to look at this soon. Thanks for the report and the Dbg
** 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 (4.3.5 or later): 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) Thank you for your help! -- The LibreOffice QA Team
No weirdness or crashing on exit -> WFM. Win 7 Pro 64-bit Version: 4.5.0.0.alpha0+ Build ID: 07e84cae983c08afdba03018413a19d01abb3006 TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-19_06:15:38