Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
Hello Rene, *, On Sun, Aug 14, 2016 at 02:20:01PM +0200, Rene Engelhard wrote: > On Sun, Aug 14, 2016 at 12:35:53PM +0200, Thomas Hackert wrote: > > > OK, then IMHO it's even minor, since normal users won't do that :) > > > > Well, but people in QA at LO or some users trying to get a backtrace > > to report a bug ... ;) > > Sure, but it doesn't affect normal operations. OK. > > > > > 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. > > > > > > > > But still it should not crash immediately ... ;) > > > > > > That's true. I was aiming at your "I don't want to install the -dbgsym > > > packages". > > > > But how do I install the debug packages? Neither "apt-cache search > > libreoffice dbg" or "libreoffice debug" show anything. "apt-cache > > search dbgsym" does only show mariadb, openhpi packages and owfs-dbg > > -dbg packages are suppoed to be gone. -dbgsym is what is done now.. OK. > > ... :( Do I need an special entry to my sources.list? > > .. and yes, it's a different archive. Google would have told you: > > http://lmgtfy.com/?q=dbgsym+Debian Oh, sorry for the dump question ... :( Though I prefer https://lmddgtfy.net/ ... ;) Sorry for the noise Thomas. -- Money is its own reward.
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
Hi, On Sun, Aug 14, 2016 at 12:35:53PM +0200, Thomas Hackert wrote: > > OK, then IMHO it's even minor, since normal users won't do that :) > > Well, but people in QA at LO or some users trying to get a backtrace > to report a bug ... ;) Sure, but it doesn't affect normal operations. > > > > 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. > > > > > > But still it should not crash immediately ... ;) > > > > That's true. I was aiming at your "I don't want to install the -dbgsym > > packages". > > But how do I install the debug packages? Neither "apt-cache search > libreoffice dbg" or "libreoffice debug" show anything. "apt-cache > search dbgsym" does only show mariadb, openhpi packages and owfs-dbg -dbg packages are suppoed to be gone. -dbgsym is what is done now.. > ... :( Do I need an special entry to my sources.list? .. and yes, it's a different archive. Google would have told you: http://lmgtfy.com/?q=dbgsym+Debian Regards, Rene
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
Hello Rene, *, On Sun, Aug 14, 2016 at 12:01:15PM +0200, Rene Engelhard wrote: > On Sat, Aug 13, 2016 at 02:34:32PM +0200, Thomas Hackert wrote: > > > 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. > > > > Yes. It only happens if I start LO from command line with "soffice > > --backtrace". > > OK, then IMHO it's even minor, since normal users won't do that :) Well, but people in QA at LO or some users trying to get a backtrace to report a bug ... ;) > > > 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. > > > > But still it should not crash immediately ... ;) > > That's true. I was aiming at your "I don't want to install the -dbgsym > packages". But how do I install the debug packages? Neither "apt-cache search libreoffice dbg" or "libreoffice debug" show anything. "apt-cache search dbgsym" does only show mariadb, openhpi packages and owfs-dbg ... :( Do I need an special entry to my sources.list? Have a nice day Thomas. -- Yeah, well that's why it's numbered 2.3.1... it's for those of us who miss NT-like uptimes
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
severity 834220 minor thanks Hi, On Sat, Aug 13, 2016 at 02:34:32PM +0200, Thomas Hackert wrote: > > 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. > > Yes. It only happens if I start LO from command line with "soffice > --backtrace". OK, then IMHO it's even minor, since normal users won't do that :) > > 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. > > But still it should not crash immediately ... ;) That's true. I was aiming at your "I don't want to install the -dbgsym packages". Regards, Rene
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
On Sat, Aug 13, 2016 at 02:47:22PM +0200, Thomas Hackert wrote: > it is only 4k in size and empty, but I will attach it to this mail. If it's empty, well you don't need a empty file.. But most probably reportbug-ng failed again. What a surprise. NOT. Maybe you should use reportbug again? common sense says that ypu don't need to do that ;) Anyways, in your initial post you said "while trying to get a backtrace for a crash with an installed extension,"... So please list me all installed extensions. (reportbug would have done so...) /usr/lib/libreoffice/program/unopkg list /usr/lib/libreoffice/program/unopkg list --shared /usr/lib/libreoffice/program/unopkg list --bundled In any case, it is almost impossible to "support" any random extension in any random development state here. They can do so much and also cause crashes.. Did you try withot the extension? (I see you moved the user dir, so a user-installed one should have gone away - but maybe you installed some not in Debian system-wide?) Regards, Rene
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
And again ... ;) On Sat, Aug 13, 2016 at 02:26:03PM +0200, Rene Engelhard wrote: > On Sat, Aug 13, 2016 at 12:19:44PM +0200, Thomas Hackert wrote: > > do something further to help fixing this bug (apart from installing > > all LO debug packages or so), feel free to ask as well. > [...] > > -8<---8<---8<---8<---8<---8<---8<---8<---8<-- > > Please attach the file: > > /tmp/reportbug-ng-libreoffice-atcAcA.txt > > to the mail. I'd do it myself if the output wasn't too long to handle. > > > > Thank you! > > ->8--->8--->8--->8--->8--->8--->8--->8--->8-- > > Oh, and you should do what it says :) Especially if it's caused by some > extension, it will show installed extensions it is only 4k in size and empty, but I will attach it to this mail. Sorry for the inconvenience Thomas. -- NP: Bring Me the Horizon – Who Want's Flowers when You're Dead? Nobody
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
Hello Rene, *, On Sat, Aug 13, 2016 at 01:48:51PM +0200, Rene Engelhard wrote: > 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. I know ... ;) > 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. Yes. It only happens if I start LO from command line with "soffice --backtrace". > > - pressing + > > 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). O.K. > > - 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. O.K. > > (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. O.K. Thanks for changing it :) > > 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. It still crashes after moving .config/libreoffice to .config/libreoffice_old and starting "soffice --backtrace" from commandline on my 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. But still it should not crash immediately ... ;) > [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] No idea, sorry ... :( Have a nice afternoon Thomas. -- Academicians care, that's who.
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
On Sat, Aug 13, 2016 at 12:19:44PM +0200, Thomas Hackert wrote: > do something further to help fixing this bug (apart from installing > all LO debug packages or so), feel free to ask as well. [...] > -8<---8<---8<---8<---8<---8<---8<---8<---8<-- > Please attach the file: > /tmp/reportbug-ng-libreoffice-atcAcA.txt > to the mail. I'd do it myself if the output wasn't too long to handle. > > Thank you! > ->8--->8--->8--->8--->8--->8--->8--->8--->8-- Oh, and you should do what it says :) Especially if it's caused by some extension, it will show installed extensions Regards, Rene
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
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 + 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
Bug#834220: [libreoffice] LO crashes if started from command line with "--backtrace" parameter on several occasions
Package: libreoffice Version: 1:5.2.0-1 Severity: normal --- Please enter the report below this line. --- Hello @ll, 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 - pressing + - clicking either on "Writer Document", "Impress Presentation", or "Draw Drawing" - it does not crashes immediately but later in Base (after saving the file as a last step in the Base wizard) - 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 (5.1.5-2, IIRC) but due to an update to 5.2.0.1 today, I have this version no longer installed. 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. Sorry for the inconvenience Thomas. --- System information. --- Architecture: amd64 Kernel: Linux 4.5.0-2-amd64 Debian Release: stretch/sid 500 xenial ppa.launchpad.net 500 unstabledownload.jitsi.org 500 testing www.deb-multimedia.org 500 testing ftp.de.debian.org 500 stable deb.opera.com 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed ==-+-= fonts-sil-gentium-basic| 1.1-7 libreoffice-base | 1:5.2.0-1 libreoffice-calc | 1:5.2.0-1 libreoffice-core (= 1:5.2.0-1) | 1:5.2.0-1 libreoffice-draw | 1:5.2.0-1 libreoffice-impress| 1:5.2.0-1 libreoffice-math | 1:5.2.0-1 libreoffice-report-builder-bin | 1:5.2.0-1 libreoffice-writer | 1:5.2.0-1 libreoffice-avmedia-backend-gstreamer | 1:5.2.0-1 OR libreoffice-avmedia-backend-vlc| fonts-dejavu | 2.36-1 libreoffice-java-common (>= 1:5.2.0~) | 1:5.2.0-1 python3-uno (>= 4.4.0~beta2) | 1:5.2.0-1 fontconfig | 2.11.0-6.5 fonts-opensymbol | 2:102.7+LibO5.2.0-1 libreoffice-common(>> 1:5.2.0) | 1:5.2.0-1 ure (>= 4.2~) | 5.2.0-1 libboost-date-time1.61.0 | 1.61.0+dfsg-2.1 libc6(>= 2.16) | libcairo2 (>= 1.12.0) | libclucene-contribs1v5(>= 2.3.3.4) | libclucene-core1v5(>= 2.3.3.4) | libcmis-0.5-5v5| libcups2(>= 1.4.0) | libcurl3-gnutls(>= 7.16.2) | libdbus-1-3(>= 1.9.14) | libdbus-glib-1-2 (>= 0.78) | libdconf1 (>= 0.14.0) | libeot0| libexpat1 (>= 2.0.1) | libexttextcat-2.0-0 (>= 2.2-8) | libfontconfig1 (>= 2.11) | libfreetype6(>= 2.3.5) | libgcc1 (>= 1:3.4) | libgl1-mesa-glx| OR libgl1 | libglew1.13(>= 1.12.0) | libglib2.0-0 (>= 2.31.8) | libgltf-0.0-0v5| libglu1-mesa | OR libglu1| libgraphite2-3 (>= 1.2.2) | libharfbuzz-icu0 (>= 0.9.18) | libharfbuzz0b (>= 0.9.42) | libhunspell-1.4-0 | libhyphen0 (>= 2.7.1) | libice6 (>= 1:1.0.0) | libicu57 (>= 57.1-1~) | libjpeg62-turbo
