Bug 155168 - LibreOffice no longer remembers which Style Sidebar I had open.
Summary: LibreOffice no longer remembers which Style Sidebar I had open.
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.3.4 release
Hardware: All Linux (All)
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-06 19:40 UTC by douglas.mathieu
Modified: 2023-12-30 03:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description douglas.mathieu 2023-05-06 19:40:24 UTC
Description:
I don't know if this is more of a bug or an enhancement request, but LibreOffice Writer USED to remember which Styles list I had open in the Sidebar, and now it does not.  I always have the "Applied Styles" Sidebar open, but if I save, close, and open the document again, it reverts back to "Hierarchical".  I am working between hundreds of documents which I constantly open and close, so this rather disrupting to my workflow.  Again, the LAST version of LibreOffice Writer remembered my Styles Sidebar; it is only after the most recent update that it stopped remembering.

Steps to Reproduce:
1.In LibreOffice Writer, open Styles in Sidebar (F11), and use dropdown to switch from "Hierarchical" to "Applied Styles".
2.Save, close, and reopen document
3.Open Styles again (F11).

Actual Results:
"Hierarchical" opens in the Sidebar.

Expected Results:
It should be "Applied Styles" that opens in the Sidebar.  This is what it used to do.


Reproducible: Always


User Profile Reset: No

Additional Info:
(I tried running in Safe Mode, and the problem persisted, which means the user profile was not the cause of the problem.)
Comment 1 BogdanB 2023-05-07 17:08:10 UTC
I don't have this problem on
Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3
Locale: ro-RO (ro_RO.UTF-8); UI: en-US
Calc: threaded

Can you test on a newer version?
Comment 2 Stéphane Guillou (stragu) 2023-06-01 11:03:37 UTC
Can't reproduce either in 7.4:

Version: 7.4.7.2 / LibreOffice Community
Build ID: 723314e595e8007d3cf785c16538505a1c878ca5
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

nor in 7.5:

Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Please test a currently-supported version (currently 7.5) and let us know if you can still reproduce.
Comment 3 QA Administrators 2023-11-29 03:14:27 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2023-12-30 03:13:44 UTC
Dear douglas.mathieu,

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