Bug 152226 - Crashed using Base: Create Report in Design View, changing report data type from table to query
Summary: Crashed using Base: Create Report in Design View, changing report data type f...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
7.3.7.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-25 19:36 UTC by Nigel Blakey
Modified: 2023-08-06 03:05 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Result of Run Graphics Test from Tools>Options>LibreOffice>View (46.87 KB, application/x-zip-compressed)
2022-12-05 11:29 UTC, Nigel Blakey
Details
Result of second Run Graphics Test (46.67 KB, application/x-zip-compressed)
2022-12-05 11:33 UTC, Nigel Blakey
Details
Result of third Run Graphics Test (46.89 KB, application/x-zip-compressed)
2022-12-05 11:36 UTC, Nigel Blakey
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nigel Blakey 2022-11-25 19:36:24 UTC
Description:
Screen goes black but able to recover by clicking through the report navigator (Functions, Page Header, Groups, Detail, Page Footer) in turn and then clicking on the Page Footer on the left of the screen whereupon normal colours return. I can then work on and save save the report but when I close the report editor an error box appears asking me to close LibreOffice and send a crash report. When I restart LibreOffice the document is recovered and the report is there as I saved it and I can continue working on it - all OK unless I change the report data type again, when the process is repeated. 

Steps to Reproduce:
1.Open Base Report in Design View
2.Change report data type from table to query or vice versa
3.

Actual Results:
Screen instantly goes black

Expected Results:
Screen should remain workable


Reproducible: Always


User Profile Reset: No

Additional Info:
If you click through the report navigator (Functions, Page Header, Groups, Detail, Page Footer) in turn and then click on the Page Footer on the left of the screen then normal colours return and its possible to continue working, save and close the report, but then a bug report is generated. That should not happen - I don't know when I last used the report generator but I have not had the problem with earlier releases.
Comment 1 Julien Nabet 2022-11-26 08:09:57 UTC
On pc Debian x86-64 with master sources updated today + gen rendering, I don't reproduce this.

Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps ?
If you still reproduce this, perhaps you may try brand new 7.4.3 since there won't be new release for 7.3 branch?
Comment 2 Nigel Blakey 2022-11-28 13:01:24 UTC
Further to the above, I have updated LibreOffice to 7.4.3.2. I've looked through the First Steps reference that you quoted. This is the specification of my computer: 

Device name	DESKTOP-H0EE8UE
Processor	Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz   3.70 GHz
Installed RAM	8.00 GB (7.88 GB usable)
Device ID	3AB2C426-58FA-45C6-BDBF-E61E4EF6048D
Product ID	00331-20090-32338-AA181
System type	64-bit operating system, x64-based processor
Pen and touch	No pen or touch input is available for this display

I've tried it on another computer and get the same bug. Here is the specification of the other computer:

Device name    LAPTOP-B88NGE75
Processor    Intel(R) Celeron(R) CPU  N2840  @ 2.16GHz   2.16 GHz
Installed RAM    4.00 GB (3.88 GB usable)
Device ID    31171F10-FE69-4F3E-8899-254DB0157A80
Product ID    00325-80399-49007-AAOEM
System type    64-bit operating system, x64-based processor
Pen and touch    No pen or touch input is available for this display 

I've taken before and after screen-shots but can't paste them into this text box. 

The sequence of actions is as follows:
1. Open a Base document
2. Select Reports
3. Select Create Report in Design View
4. Select Report Navigator
5. In Report Navigator select Report
6. In the right hand panel select Data
7. Initially the Content type is Table but from the drop down list select Query
8. The screen goes black, but recovers (without the top menu bar) by selecting the middle icon on the extreme top right of the Windows screen i.e the three icons: Minimise, Maximise, Close. Selecting the Maximise button again recovers the menu bar. 
9. Continue designing the report, save it, but then on closing the report designer the standard error message appears asking for an error report and saying the file will be recovered on next starting LibreOffice. 

It is possible to work round all this but it is annoying!
Comment 3 Robert Großkopf 2022-11-28 14:08:09 UTC
Couldn't confirm any buggy behavior here. Could change form table to query as source of the report without any problems.

Tested with
Version: 7.4.3.2 / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

on OpenSUSE 15.3 64bit rpm Linux.
Comment 4 Alex Thurgood 2022-11-28 15:20:16 UTC
(In reply to Nigel Blakey from comment #0)
> Description:
> Screen goes black but able to recover by clicking through the report
> navigator (Functions, Page Header, Groups, Detail, Page Footer) in turn and
> then clicking on the Page Footer on the left of the screen whereupon normal
> colours return. I can then work on and save save the report but when I close
> the report editor an error box appears asking me to close LibreOffice and
> send a crash report. When I restart LibreOffice the document is recovered
> and the report is there as I saved it and I can continue working on it - all
> OK unless I change the report data type again, when the process is repeated. 
> 


> Actual Results:
> Screen instantly goes black
> 
> Expected Results:
> Screen should remain workable
> 
> 

The screen blacking out in one or more places is often a sign of an incompatibility with the graphics chip (or driver for the graphics chip), on the one hand, and the activation of Skia rendering within the LibreOffice application preferences, on the other hand.


@Nigel : can you try switching off any Skia rendering options under the Display settings of the LibreOffice settings dialogs (from within a running LibreOffice, I think it is via the menu : Tools > Options > LibreOffice > Display)

Does the Celeron N2840 chip have a dedicated GPU ?

There are some tests that can be run from within LibreOffice to put the graphics chip through its paces, and which can be found under Tools > Options > LibreOffice > Display.

You can download the results of those tests(as a CSV file ?), and upload them here so we could have a look, you never know, it might help us pinpoint an issue.
Comment 5 Nigel Blakey 2022-12-05 11:29:13 UTC
Created attachment 183992 [details]
Result of Run Graphics Test from Tools>Options>LibreOffice>View

Graphics Test run with both Skia options enabled
Comment 6 Nigel Blakey 2022-12-05 11:33:35 UTC
Created attachment 183993 [details]
Result of second Run Graphics Test

Test was run with neither of Skia Options enabled
Comment 7 Nigel Blakey 2022-12-05 11:36:21 UTC
Created attachment 183994 [details]
Result of third Run Graphics Test

This Run Graphics Test was done with only Use Skia for All Rendering enabled, but with Force Skia Software Rendering disabled.
Comment 8 Nigel Blakey 2022-12-05 11:38:41 UTC
Sorry for the delay. Attached are the test results from using the Base Report Create in Design View: (1) with Skia, (2) without Force Skia and (3) with neither Force Skia  nor Use Skia for all Rendering.

My computer displays the screen normally and LibreOffice does not crash with neither of the Skia options enabled, but the screen goes black and LibreOffice crashes when either or both the Skia options are enabled.

Just for the avoidance of doubt here are the specifications of my computer:

Device name    DESKTOP-H0EE8UE
Processor    Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz   3.70 GHz
Installed RAM    8.00 GB (7.88 GB usable)
Device ID    3AB2C426-58FA-45C6-BDBF-E61E4EF6048D
Product ID    00331-20090-32338-AA181
System type    64-bit operating system, x64-based processor
Pen and touch    No pen or touch input is available for this display

Edition    Windows 10 Pro
Version    22H2
Installed on    ‎06/‎06/‎2021
OS build    19045.2251
Experience    Windows Feature Experience Pack 120.2212.4180.0

Thank you for your help. I hope my bug is of assistance.

Regards
Nigel Blakey
Comment 9 Julien Nabet 2022-12-09 11:45:19 UTC
Since the pb seems related to Skia, could you apply https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_.28_Skia_.29 ?

To summerize, 1) check you got last version of your graphic driver 2) if it's still buggy, attach <user profile>/cache/skia.log
Comment 10 QA Administrators 2023-07-06 03:15:25 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2023-08-06 03:05:44 UTC
Dear Nigel Blakey,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp