Created attachment 123506 [details] Backtrace of the crash Drag any file to start center. Crash. 5.2 built today. 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha0+ Build ID: 235411c9d47ecba88e46d859ea93bcecefb0c46e CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8)
I can confirm with Version: 5.2.0.0.alpha0+ Build ID: aaca25d67eb5ea252730cdcf555ecc04ce04a5e6 CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-02-24_23:58:47 No crash wit 5.0.5.2, regression
Just happened to me, too...
That's a regression of https://cgit.freedesktop.org/libreoffice/core/commit/?id=f2f1f52d8b84ac088496a4964d799bb84007fc45 There is inverted condition in DNDEventDispatcher::fireDropEvent.
Thanks Maxim - good catch - let me fix that =)
Crashes in Window::DecrementLockCount() where mpWindowImpl is NULL, but accessed. Looks like a task for the vcl digger
When jumping over 'mpWindowImpl->mnLockCount--;' all works well. Other Window:: methods already use pattern return mpWindowImpl ? mpWindowImpl->mnStyle : 0; another case to use it?
Armin: sounds good - we should at least not crash; but I'll add some asserts to those two methods - for some locking pair-up we shouldn't really mis the other part of the pair there I think; at least in debug mode.
Fix pushed to gerrit; thanks =) https://gerrit.libreoffice.org/23307 tdf#98607 - fix drag and drop regression.
Doesn't affect -5-1 thankfully =)
Michael Meeks committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=652e8a2b37bded8afe73f8ee03bb6664443c7cab tdf#98607 - fix drag and drop regression. It will be available in 5.2.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Fixed with 5.2.0.0.alpha1+