Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


On Thursday 17 of April 2014, Lubos Lunak wrote:
On Wednesday 16 of April 2014, Stephan Bergmann wrote:
Jan-Marek, all,

Any details on the reason for the revert, and whether it could be the
cause for the newly seen crash?

 KDE4 file dialog support is currently apparently broken one way or
another.

 Current git master (or at least few weeks back when I checked) when built
with dbgutil simply aborts on assertion failure about holding the yield
mutex properly. Older LO version without these modifications sooner or
later crashes on QTransform::type(), I'm not sure what has changed, since
this used to be pretty stable for me on openSUSE 12.3, but with 13.1 it
crashes easily. So it looks like so far the best option is just not
including the Qt4 patch, which will mean the cumbersome generic LO file
dialog :-/.

 I haven't had yet the time to look deeper into this, and getting this
event loops stuff is not exactly trivial :(.

 Ok, I suffered enough with the generic file dialog, and found some time for 
this. I've just pushed 2cd8a1e0f1e81efd15979953d7f274ab8a6806d6 .. 
508337db0c53caa5fb43ef26f781df159497a482 , which has links to Qt bugreports 
for needed fixes, if they're not present you get the generic file dialog 
without crashes (and without convenient use), otherwise KFileDialog seems to 
work fine for me.

 I haven't really tested it yet that much, but It Should Be Okay(TM), so feel 
free to backport to 4.2 if you feel like.

-- 
 Lubos Lunak
 l.lunak@collabora.com

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.