found 834220 1:5.1.5~rc2-1 tag 834220 + moreinfo tag 834220 + unreproducible thanks
Hi, just tried in clean, current sid (you use a testing with some mix from some random stuff you probably shouldn't use - like Ubuntu xenial ppas..). But testing and sid should be similar enough. On Sat, Aug 13, 2016 at 12:19:44PM +0200, Thomas Hackert wrote: > while trying to get a backtrace for a crash with an installed > extension, I started LO from command line with "soffice > --backtrace". To my astonishment LO crashes, when You mean it only happens with --backtrace or also without? Your title suggests the first. > - pressing <Ctrl>+<N> works for me. > - clicking either on "Writer Document", "Impress Presentation", > or "Draw Drawing" works for me. > - it does not crashes immediately but later in Base (after > saving the file as a last step in the Base wizard) Didn't try (yet). > - if a crash happened and you have not recovered a document and > closed LO before, a new "soffice --backtrace" will also crash > immediately ... :( Actually I found this bug with the last version No, that was the case on my first try, worked, too. > (5.1.5-2, IIRC) but due to an update to 5.2.0.1 today, I have this > version no longer installed. Then you should set Version: to the correct value. The BTS tracks that, ans right now only thinks 5.2.0-1 was affected. > If you need any further information, feel free to ask :) If I could > do something further to help fixing this bug (apart from installing > all LO debug packages or so), feel free to ask as well. I'd firstly try in a clean system. But yes, if you want a --backtrace, you DO need the -dbgsym packages. They contain the debug symbols. Without them a backtrace not very useful. [useless reportbug-ng output snipped. Does reportbug-ng have a bug and doesn't display the versions of the dependencies? Isn't shown here at least and I saw it before too] Regards, Rene
