Bug 95949 - Changing Display Mode using View menu does not update Display Mode
Summary: Changing Display Mode using View menu does not update Display Mode
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
5.1.0.0.alpha1
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Display-View-Selector
  Show dependency treegraph
 
Reported: 2015-11-20 11:25 UTC by Óvári
Modified: 2024-06-01 03:15 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 Óvári 2015-11-20 11:25:45 UTC
Win 8.1
Version: 5.1.0.0.alpha1+ (x64)
Build ID: 186f365a2c541c51e404b1fa819f35c9152adaf1
TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-11-19_23:26:12

Changing the view using the Display Mode changes the selection in the View menu; however, changing the view using the View menu does not update the Display Mode.

Thank you
Comment 1 Yousuf Philips (jay) (retired) 2015-11-24 11:59:03 UTC
Version: 5.1.0.0.alpha1+
Build ID: f6bc5b79c31225c02e9500d0ced4bd26f998f82b
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-11-24_01:06:28
Locale: en-US (en_US.UTF-8)
Comment 2 QA Administrators 2017-03-06 14:03:06 UTC Comment hidden (obsolete)
Comment 3 Óvári 2017-03-06 21:39:59 UTC
(In reply to QA Administrators from comment #2)
> If the bug is present, please leave a comment that includes the version of
> LibreOffice and 
> your operating system, and any changes you see in the bug behavior
LibreOffice Version: 5.3.0.3
Build ID: 7074905676c47b82bbcfbea1aeefc84afe1c50e1
CPU Threads: 2; OS Version: Linux 4.4; UI Render: default; VCL: gtk2; Layout Engine: new

Operating system: Linux Mint 18.1 Cinnamon 64-bit
Comment 4 QA Administrators 2018-03-07 03:40:30 UTC Comment hidden (obsolete)
Comment 5 Óvári 2018-03-07 05:46:31 UTC
(In reply to QA Administrators from comment #4)
> If the bug is present, please leave a comment that includes the information
> from Help - About LibreOffice.
Version: 6.0.2.1
Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89
CPU threads: 2; OS: Linux 4.13; UI render: default; VCL: gtk2

Linux Mint 18.3 Cinnamon 64-bit
Comment 6 QA Administrators 2019-03-08 03:41:22 UTC Comment hidden (obsolete)
Comment 7 Óvári 2020-05-31 02:30:56 UTC
still repro in 

LibreOffice
Version: 6.4.4.2
Build ID: 3d775be2011f3886db32dfd395a6a6d1ca2630ff
CPU threads: 2; OS: Linux 5.3; UI render: default; VCL: gtk3

Linux Mint 19.3 Cinnamon 64-bit
Comment 8 QA Administrators 2022-06-01 03:37:26 UTC Comment hidden (obsolete)
Comment 9 Óvári 2022-06-01 10:04:38 UTC
(In reply to QA Administrators from comment #8)

still reproducible in

Version: 7.3.3.2 / LibreOffice Community
Build ID: d1d0ea68f081ee2800a922cac8f79445e4603348
CPU threads: 2; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Flatpak
Calc: threaded
Comment 10 QA Administrators 2024-06-01 03:15:22 UTC
Dear Óvári,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug