Bug 103681 - cant open template dialog
Summary: cant open template dialog
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.2.3.3 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2016-11-03 14:53 UTC by Mike Silbermann
Modified: 2019-05-15 09:31 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
It dont work (95.60 KB, image/jpeg)
2016-11-03 14:53 UTC, Mike Silbermann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Silbermann 2016-11-03 14:53:55 UTC
Created attachment 128469 [details]
It dont work

I cant open a new template in main dialog-box
Comment 1 Jean-Baptiste Faure 2016-11-04 06:04:58 UTC
Same for me in LO 5.2.4.0+ under Ubuntu.
It works if you first click on the template button then choose in the dropdown list to filter.
I do not know if it is a bug or a feature.

Best regards. JBF
Comment 2 Jean-Baptiste Faure 2016-11-04 15:06:37 UTC
Works in LO 5.2.2 and the master under Ubuntu.
So setting as NEW.

Best regards. JBF
Comment 3 Xisco Faulí 2016-11-12 14:34:34 UTC
I can no longer reproduce it in

Version: 5.3.0.0.alpha1+
Build ID: 60da087d7e182b58b63d4123c9bd96c82376d450
CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; VCL: gtk2; Layout Engine: new; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

Closing this as RESOLVED WORKSFORME
Adding backportRequest:5.2
Comment 4 Jean-Baptiste Faure 2016-11-12 17:14:53 UTC
(In reply to Xisco Faulí from comment #3)
> I can no longer reproduce it in
> 
> Version: 5.3.0.0.alpha1+
> Build ID: 60da087d7e182b58b63d4123c9bd96c82376d450
> CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; VCL: gtk2; Layout
> Engine: new; 
> Locale: ca-ES (ca_ES.UTF-8); Calc: group
> 
> Closing this as RESOLVED WORKSFORME
> Adding backportRequest:5.2

Not sure that closing this bug as WorksForMe is correct here: this bug is a regression in the 5.2 branch. Indeed it works in 5.2.2 but not in 5.2.3. Never seen this problem in the master / 5.3
WorksForMe means that we don't know what fixed the problem but, here, as he bug isn't present in the master, I guess there is nothing to backport from master to 5.2 branch.

For me this bug should be set as NEW until it is fixed in 5.2 branch or the EOL of 5.2 branch.

Best regards. JBF
Comment 5 Xisco Faulí 2016-11-12 17:25:08 UTC
if it was introduced between 5.2.2 and 5.2.3 it means it was in master at certain point too as the fixes included between 5.2.2 and 5.2.3 are cherry-picked from master.
What needs to be done now: bibisect in master at which point the regression was introduced and at which point it was fixed, and ask the developer who fixed it to backport it to 5.2 branch