Bug 126093 - CRASH: Base Reportbuilder does not start in design mode
Summary: CRASH: Base Reportbuilder does not start in design mode
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
6.2.4.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks:
 
Reported: 2019-06-25 16:42 UTC by jotielmann
Modified: 2019-06-28 15:05 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
bt Windows (windbg) (80.82 KB, text/plain)
2019-06-26 07:20 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jotielmann 2019-06-25 16:42:12 UTC
Description:
Base Reportbuilder does not start in design mode, it starts only in assistent mode

Steps to Reproduce:
1.Start any database
2.Go to Reports
3.Try to start "Berichte in der Entwurfsanmsicht erstellen"

Actual Results:
nothing happens

Expected Results:
The session should open


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Comment 1 Robert Großkopf 2019-06-25 18:59:14 UTC
Tested with LO 6.2.4.2 on OpenSUSE 15 64bit rpm Linux. Couldn't confirm any buggy behaviour here.

Which system do you use? If it is Ubuntu and the packages from Ubuntu: Did you install all needed packages for Report-Builder?
Comment 2 Julien Nabet 2019-06-26 07:20:47 UTC
Created attachment 152407 [details]
bt Windows (windbg)

On Win10 with master sources updated yesterday, I got a crash.

Here are the steps I did:
- created a brand odb file with embeddedhsqldb
- created the table tasks with wizard
- click Design Report

=> Crash
Comment 3 Julien Nabet 2019-06-26 07:21:57 UTC
Noel: noticing this on bt:
000000c7`4dd7c450 00007ffb`69df6994 vcllo!std::operator==<Node,std::default_delete<Node> >+0x14
000000c7`4dd7c490 00007ffb`aaeff99f tllo!tools::Rectangle::GetWidth+0xf
000000c7`4dd7c498 00007ffb`69df9c4f vcllo!Node::insert+0x10f
000000c7`4dd7c5e8 00007ffb`69df912f vcllo!std::_Unique_ptr_base<Node,std::default_delete<Node> >::_Myptr+0x1f
000000c7`4dd7ddf8 00007ffb`69dfa1bf vcllo!Node::isLeaf+0x3f


thought you might be interested in this one.
Comment 4 Julien Nabet 2019-06-26 07:24:15 UTC
On Win10 with LO 6.2.4.2, I don't reproduce this so perhaps something different than reporter's problem.
Comment 5 jotielmann 2019-06-26 12:04:14 UTC
I use Linux Mint 18 Sarah 64 bit
based on ubuntu 16.04.1
How can I test, if all needed packages for Report-Builder are installed?
It is strainge, that the Reportbuilder works with the assistent session, but not with the design session.
Comment 6 Alex Thurgood 2019-06-26 12:45:05 UTC
@jotielmann : where are those LO packages from ?

LO6242 is not the default release version for Mint 18, so that means that you have either installed from a PPA, or else from a snap.

If you are using a PPA, you should expect problems, which are not necessarily LO problems, because the package maintainers of the PPAs do not always put in all of the required components, for reasons that are particular only to themselves.

If you already had the default LO version provided by Mint Sarah repos (which is 6.0.7, or possibly even still stuck at 5.3), and overwrote those with the 6.2 packages, then you may have mixed up the various parts of the report-builder, which might be the reason for your problems. That wouldn't be a LO problem, but a distrib problem, and you'd have to figure out how to purge all of your LO installation(s) and start over cleanly.
Comment 7 Xisco Faulí 2019-06-28 12:43:24 UTC
(In reply to Julien Nabet from comment #2)
> Created attachment 152407 [details]
> bt Windows (windbg)
> 
> On Win10 with master sources updated yesterday, I got a crash.
> 
> Here are the steps I did:
> - created a brand odb file with embeddedhsqldb
> - created the table tasks with wizard
> - click Design Report
> 
> => Crash

I can't reproduce it in

Version: 6.4.0.0.alpha0+
Build ID: a294457eb95e60028539b6783abac78b56561fe2
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded
Comment 8 Xisco Faulí 2019-06-28 12:51:14 UTC
Nor in

Version: 6.4.0.0.alpha0+ (x64)
Build ID: fe855eda54faf6196ad9dea12d8dc090b6d6c1da
CPU threads: 16; OS: Windows 6.3; UI render: default; VCL: win; 
Locale: en-GB (en_GB); UI-Language: en-US
Calc: threaded
Comment 9 Julien Nabet 2019-06-28 13:15:00 UTC
On pc Win10 with master sources updated today + rename profile, everything is ok now (no crash and reports display).
Comment 10 Xisco Faulí 2019-06-28 13:55:56 UTC
Dear jotielmann,
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Comment 11 jotielmann 2019-06-28 15:00:54 UTC
The problem exits only in version (installed by PPA)

Version: 6.2.4.2
Build-ID: 1:6.2.4-0ubuntu0.16.04.1~lo1
CPU-Threads: 2; BS: Linux 4.15; UI-Render: Standard; VCL: gtk2; 
Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE
Calc: threaded

It exists not in Version (installed from http://downloadarchive.documentfoundation.org/libreoffice/old/6.2.4.2/deb/)

Version: 6.2.4.2
Build-ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64
CPU-Threads: 2; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; 
Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE
Calc: threaded

Thanks for help!
Comment 12 Xisco Faulí 2019-06-28 15:05:05 UTC
Thanks for retesting with the latest version.
Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.