Bug 65519 - UI: Closing "Execute SQL Statement" closes LO completely
Summary: UI: Closing "Execute SQL Statement" closes LO completely
Status: CLOSED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
4.2.0.0.alpha0+ Master
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-06-07 17:55 UTC by Julien Nabet
Modified: 2023-03-19 00:14 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Nabet 2013-06-07 17:55:20 UTC 
Problem description: 
On pc Debian x86-64 with master sources updated today + brand new LO profile, closing "Execute SQL Statement" closes LO completely 

No segfault but I noticed these console logs:
warn:legacy.osl:6159:1:vcl/source/window/window.cxx:4430: Window (Execute SQL Statement) with live children destroyed:  8CheckBox (~Show output of "select" statements)
Window (Execute SQL Statement) with live children destroyed:  8CheckBox (~Show output of "select" statements)

Steps to reproduce:
1. Open a brand new HSQLDB
2. Menu Tools/SQL => the execute SQL window appears
3. Click Close

Current behavior:
LO closes completely

Expected behavior:
just the window "Execute SQL window" should close

              
Operating System: Debian
Version: 4.2.0.0.alpha0+ Master
Comment 1 Julien Nabet 2013-06-07 17:56:40 UTC 
For the record, with 4.0.3 Debian packages and brand new LO profile, I don't reproduce this.
Comment 2 Jorendc 2013-06-08 11:14:24 UTC 
Reproducible using Linux Mint 15 x64 and Libreoffice Version: 4.2.0.0.alpha0+
Build ID: 55ff402fa24bcf9478e7fde94f2ab57c2223b7f

Kind regards,
Joren
Comment 3 Jorendc 2013-06-08 11:26:02 UTC 
Not reproducible with Version: 4.2.0.0.alpha0+ Build ID: 0143805a565418d2a114c16b7eeba3b784176d9 , so it is somewhere introduced between 2013-05-28 16:03:22 and 2013-06-07 15:00:34

I'm now syncing my bisectrepo, will retest when it's done.
Comment 4 Mirosław Zalewski 2013-10-24 15:19:23 UTC 
I could NOT reproduce this on:
- 4.0.6
- 4.1.2
- master builds from 4 December 2012 to 17 September 2013 (during usual bibisect session from oldest to latest, not a single build has been affected).
Debian testing, amd64.

@Julien: can you reproduce this issue on reasonably recent master build?

If yes, then I think that there might be something that interferes in your case. It might still be LO bug, but more complex than you presented in your original report.

If no, then I think that was temporary turmoil that has been fixed since then. You were just unlucky to build broken version. Will you agree to mark this issue as FIXED/WORKSFORME?

I will leave status of this bug as NEEDINFO until we hear back from you.
Comment 5 Julien Nabet 2013-11-06 20:54:41 UTC 
Sorry for the delay, I don't reproduce this anymore with master sources updated today.

Thank you Jorendc and Mirosław for your feedback.
Comment 6 Robinson Tryon (qubit) 2015-12-17 07:15:41 UTC 
Migrating Whiteboard tags to Keywords: (bibisectrequest)
[NinjaEdit]