Bug 124593 - Libreoffice Calc 6.2 crash fresh install
Summary: Libreoffice Calc 6.2 crash fresh install
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.2.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 124493 124650 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-04-07 21:37 UTC by Jonny Grant
Modified: 2019-11-08 15:56 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
gdb (12.22 KB, text/x-log)
2019-04-07 21:38 UTC, Jonny Grant
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jonny Grant 2019-04-07 21:37:40 UTC
Description:
Do you know maintains OutputDevice::LogicToPixel ?


Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
0x00007f978d71ed80 in OutputDevice::LogicToPixel(Size const&, MapMode const&) const () from /usr/lib/libreoffice/program/libmergedlo.so
#0  0x00007f978d71ed80 in OutputDevice::LogicToPixel(Size const&, MapMode const&) const () at /usr/lib/libreoffice/program/libmergedlo.so

Steps to Reproduce:
1. install https://www.libreoffice.org/download/download/
2.open calc
3. close calc.

Actual Results:
Observe crash after 3

Expected Results:
Not crash


Reproducible: Always


User Profile Reset: No



Additional Info:
Will attach gdb trace
Comment 1 Jonny Grant 2019-04-07 21:38:12 UTC
Created attachment 150587 [details]
gdb
Comment 2 m_a_riosv 2019-04-07 22:24:01 UTC
Please test Menu/Help/Restart in Safe Mode.
Comment 3 Jonny Grant 2019-04-08 08:43:33 UTC
Do you know maintains OutputDevice::LogicToPixel ?
Please address in first instance.
I don't have the buggy DEBs installed anymore.
Comment 4 Xisco Faulí 2019-04-09 12:21:35 UTC
Could you please paste the info from Help - about LibreOffice ?
Comment 5 Jonny Grant 2019-04-09 17:53:49 UTC
Uninstalled the DEBs, which were 6.2.2

Did you reproduce?
Comment 6 Xisco Faulí 2019-04-12 09:55:40 UTC
*** Bug 124493 has been marked as a duplicate of this bug. ***
Comment 7 Xisco Faulí 2019-04-12 09:55:52 UTC
*** Bug 124650 has been marked as a duplicate of this bug. ***
Comment 8 QA Administrators 2019-10-10 02:41:00 UTC Comment hidden (obsolete)
Comment 9 Jonny Grant 2019-10-10 16:43:27 UTC
There are none of your developers working on this? Just close it. I'll no longer waste my time reporting crash bugs on a project without a team. You may as well close every ticket, if no one is working on crashes with a backtrace OutputDevice::LogicToPixel(Size const&, MapMode const&) const () from /usr/lib/libreoffice/program/libmergedlo.so

Why is it de-referencing NULL?
Comment 10 Jonny Grant 2019-10-10 16:59:52 UTC
Looks like it is this file that is crashing

https://code.woboq.org/libreoffice/libreoffice/vcl/source/gdi/outmap.cxx.html

Size OutputDevice::LogicToPixel( const Size& rLogicSize,
                                 const MapMode& rMapMode ) const
Comment 11 QA Administrators 2019-10-11 02:39:19 UTC Comment hidden (obsolete)
Comment 12 Xisco Faulí 2019-10-16 08:49:26 UTC
(In reply to Xisco Faulí from comment #4)
> Could you please paste the info from Help - about LibreOffice ?

This question remains unanswered...
Comment 13 Jonny Grant 2019-10-16 12:48:44 UTC
(In reply to Xisco Faulí from comment #12)
> (In reply to Xisco Faulí from comment #4)
> > Could you please paste the info from Help - about LibreOffice ?
> 
> This question remains unanswered...

See comment #5
Comment 14 QA Administrators 2019-10-17 02:37:44 UTC Comment hidden (obsolete)
Comment 15 Xisco Faulí 2019-11-08 12:05:19 UTC
(In reply to Jonny Grant from comment #13)
> (In reply to Xisco Faulí from comment #12)
> > (In reply to Xisco Faulí from comment #4)
> > > Could you please paste the info from Help - about LibreOffice ?
> > 
> > This question remains unanswered...
> 
> See comment #5

I'm not interested in the version but in the environment you are using. we use different backends, gtk3, gtk2, x11, kde5...
Comment 16 Jonny Grant 2019-11-08 12:19:53 UTC
(In reply to Xisco Faulí from comment #15)
> (In reply to Jonny Grant from comment #13)
> > (In reply to Xisco Faulí from comment #12)
> > > (In reply to Xisco Faulí from comment #4)
> > > > Could you please paste the info from Help - about LibreOffice ?
> > > 
> > > This question remains unanswered...
> > 
> > See comment #5
> 
> I'm not interested in the version but in the environment you are using. we
> use different backends, gtk3, gtk2, x11, kde5...



Version: 6.0.7.3
Build ID: 1:6.0.7-0ubuntu0.18.04.10
CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); Calc: group

What did you identify from the backtrace?
Comment 17 Xisco Faulí 2019-11-08 12:23:54 UTC
(In reply to Jonny Grant from comment #16)
> (In reply to Xisco Faulí from comment #15)
> > (In reply to Jonny Grant from comment #13)
> > > (In reply to Xisco Faulí from comment #12)
> > > > (In reply to Xisco Faulí from comment #4)
> > > > > Could you please paste the info from Help - about LibreOffice ?
> > > > 
> > > > This question remains unanswered...
> > > 
> > > See comment #5
> > 
> > I'm not interested in the version but in the environment you are using. we
> > use different backends, gtk3, gtk2, x11, kde5...
> 
> 
> 
> Version: 6.0.7.3
> Build ID: 1:6.0.7-0ubuntu0.18.04.10
> CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; 
> Locale: en-GB (en_GB.UTF-8); Calc: group
> 
> What did you identify from the backtrace?

Nothing, it should be taked with a debug build. You can get one from https://dev-builds.libreoffice.org/daily/master/ ( those with dbg in there name ). Call LibreOffice with program/soffice --backtrace, reproduce the crash and attach the gdbtrace.log file
Comment 18 Jonny Grant 2019-11-08 12:30:31 UTC
(In reply to Xisco Faulí from comment #17)
> (In reply to Jonny Grant from comment #16)
> > (In reply to Xisco Faulí from comment #15)
> > > (In reply to Jonny Grant from comment #13)
> > > > (In reply to Xisco Faulí from comment #12)
> > > > > (In reply to Xisco Faulí from comment #4)
> > > > > > Could you please paste the info from Help - about LibreOffice ?
> > > > > 
> > > > > This question remains unanswered...
> > > > 
> > > > See comment #5
> > > 
> > > I'm not interested in the version but in the environment you are using. we
> > > use different backends, gtk3, gtk2, x11, kde5...
> > 
> > 
> > 
> > Version: 6.0.7.3
> > Build ID: 1:6.0.7-0ubuntu0.18.04.10
> > CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; 
> > Locale: en-GB (en_GB.UTF-8); Calc: group
> > 
> > What did you identify from the backtrace?
> 
> Nothing, it should be taked with a debug build. You can get one from
> https://dev-builds.libreoffice.org/daily/master/ ( those with dbg in there
> name ). Call LibreOffice with program/soffice --backtrace, reproduce the
> crash and attach the gdbtrace.log file

Attached that gdb backtrace months ago.

Just close the ticket, you're wasting my time.
Comment 19 Xisco Faulí 2019-11-08 12:36:26 UTC
(In reply to Jonny Grant from comment #18)
> (In reply to Xisco Faulí from comment #17)
> > (In reply to Jonny Grant from comment #16)
> > > (In reply to Xisco Faulí from comment #15)
> > > > (In reply to Jonny Grant from comment #13)
> > > > > (In reply to Xisco Faulí from comment #12)
> > > > > > (In reply to Xisco Faulí from comment #4)
> > > > > > > Could you please paste the info from Help - about LibreOffice ?
> > > > > > 
> > > > > > This question remains unanswered...
> > > > > 
> > > > > See comment #5
> > > > 
> > > > I'm not interested in the version but in the environment you are using. we
> > > > use different backends, gtk3, gtk2, x11, kde5...
> > > 
> > > 
> > > 
> > > Version: 6.0.7.3
> > > Build ID: 1:6.0.7-0ubuntu0.18.04.10
> > > CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; 
> > > Locale: en-GB (en_GB.UTF-8); Calc: group
> > > 
> > > What did you identify from the backtrace?
> > 
> > Nothing, it should be taked with a debug build. You can get one from
> > https://dev-builds.libreoffice.org/daily/master/ ( those with dbg in there
> > name ). Call LibreOffice with program/soffice --backtrace, reproduce the
> > crash and attach the gdbtrace.log file
> 
> Attached that gdb backtrace months ago.
> 
> Just close the ticket, you're wasting my time.

Did you use a debug build back in the time? I doubt it
Comment 20 Jonny Grant 2019-11-08 12:54:13 UTC
(In reply to Xisco Faulí from comment #19)
> (In reply to Jonny Grant from comment #18)
> > (In reply to Xisco Faulí from comment #17)
> > > (In reply to Jonny Grant from comment #16)
> > > > (In reply to Xisco Faulí from comment #15)
> > > > > (In reply to Jonny Grant from comment #13)
> > > > > > (In reply to Xisco Faulí from comment #12)
> > > > > > > (In reply to Xisco Faulí from comment #4)
> > > > > > > > Could you please paste the info from Help - about LibreOffice ?
> > > > > > > 
> > > > > > > This question remains unanswered...
> > > > > > 
> > > > > > See comment #5
> > > > > 
> > > > > I'm not interested in the version but in the environment you are using. we
> > > > > use different backends, gtk3, gtk2, x11, kde5...
> > > > 
> > > > 
> > > > 
> > > > Version: 6.0.7.3
> > > > Build ID: 1:6.0.7-0ubuntu0.18.04.10
> > > > CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; 
> > > > Locale: en-GB (en_GB.UTF-8); Calc: group
> > > > 
> > > > What did you identify from the backtrace?
> > > 
> > > Nothing, it should be taked with a debug build. You can get one from
> > > https://dev-builds.libreoffice.org/daily/master/ ( those with dbg in there
> > > name ). Call LibreOffice with program/soffice --backtrace, reproduce the
> > > crash and attach the gdbtrace.log file
> > 
> > Attached that gdb backtrace months ago.
> > 
> > Just close the ticket, you're wasting my time.
> 
> Did you use a debug build back in the time? I doubt it

It's a long time since gdb report 2019-04-07, I don't recall.
Well some of the symbols are there.

Why not fix the backtrace script to append a complete version log of all binaries and confirmation if it is a debug build?
Comment 21 Xisco Faulí 2019-11-08 13:03:15 UTC
(In reply to Jonny Grant from comment #20)
> Why not fix the backtrace script to append a complete version log of all
> binaries and confirmation if it is a debug build?

How do you know it's not fixed in master if you don't even try it ? You're using 6.0.7.3 which was released 1 year ago. The file vcl/source/gdi/outmap.cxx you mentioned in comment 10 doesn't even exist anymore.
Who is waiting other's time here ?
Comment 22 Jonny Grant 2019-11-08 15:56:46 UTC
(In reply to Xisco Faulí from comment #21)
> (In reply to Jonny Grant from comment #20)
> > Why not fix the backtrace script to append a complete version log of all
> > binaries and confirmation if it is a debug build?
> 
> How do you know it's not fixed in master if you don't even try it ? You're
> using 6.0.7.3 which was released 1 year ago. The file
> vcl/source/gdi/outmap.cxx you mentioned in comment 10 doesn't even exist
> anymore.
> Who is waiting other's time here ?

This was raised 8 months ago. Clearly I am wasting my time providing crash reports.

I'll save us both time and close the ticket.