severity 847572 important tag 847572 + moreinfo found 847572 1:4.3.3-2+deb8u5 thanks
Hi, On Fri, Dec 09, 2016 at 04:11:51PM +0100, Le Garage Numérique wrote: > Package: libreoffice > > debian reportbug enclosed. The reportbug thing is thought as the actual mail contents to that Package:, Version: etc take effect. (But in this case maybe, given that then the BTS doesn't see the overinflated bug severity it's probably good that you did it the way you did ;)...) > Thanks for any help.. Mmh, I am quite sure you didn't mean it this way - but this is a bug tracking system - not a support forum or a ticketing system... ;) >Package: libreoffice >Version: 1:4.3.3-2+deb8u5 >>Severity: grave > >Tags: upstream > >Justification: renders package unusable I'd argue this is overinflated severity.... I am quite sure it doesn't happen for everyone. > I have problem with libreoffice crashing on start. Always? Or in which cases? See below. > # apt-cache policy xserver-xorg-video-intel > xserver-xorg-video-intel: > Install????: 2:2.99.917+git20161105-1~bpo8+1 > Candidat??: 2:2.99.917+git20161105-1~bpo8+1 > Table de version??: > *** 2:2.99.917+git20161105-1~bpo8+1 0 > 100 http://http.debian.net/debian/ jessie-backports/main amd64 > Packages > 100 /var/lib/dpkg/status > 2:2.21.15-2+b2 0 > 500 http://ftp.fr.debian.org/debian/ jessie/main amd64 Packages > [/code] And with plain jessie? Bugs only appearing if you leave jessie and have backports are not really right here; this BTS is not about bpo bugs.. > I debug libreoffice using --backtrace option, here is gdbtrace.log: And with libreoffice-dbg installed so one gets useful infos instead of ??'s? > [code] > warning: Currently logging to gdbtrace.log. Turn the logging off and on to > make the new setting effective. > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7fffe7c8c700 (LWP 2548)] > [New Thread 0x7fffe1615700 (LWP 2549)] > [New Thread 0x7fffe0e14700 (LWP 2550)] > [New Thread 0x7fffdb586700 (LWP 2551)] > [New Thread 0x7fffd9930700 (LWP 2552)] > [New Thread 0x7fffc68c3700 (LWP 2553)] > [New Thread 0x7fffc558f700 (LWP 2556)] > [Thread 0x7fffc558f700 (LWP 2556) exited] > > Program received signal SIGSEGV, Segmentation fault. > 0x00007ffff45139f5 in ?? () from /usr/lib/libreoffice/program/libsvtlo.so > #0 0x00007ffff45139f5 in ?? () from /usr/lib/libreoffice/program/libsvtlo.so > #1 0x00007ffff4513cff in TabBar::Resize() () from > /usr/lib/libreoffice/program/libsvtlo.so [...] Here e.g. #0 misses info... But anyway, googling for "TabBar::Resize crash libreoffice" gives me https://bugzilla.redhat.com/show_bug.cgi?id=1123710 Can you try with -dbg and/or confirm the stuff mentioned in that bug? (the profile removal stuff, TabBar::ImplShowPage) etc. Maybe even test with LO from bpo. Is it with ODGs as described above? Regards, Rene
