Bug 157710 - Invoking a document among the recently accessed ones no longer does anything if that document is already open
Summary: Invoking a document among the recently accessed ones no longer does anything ...
Status: RESOLVED DUPLICATE of bug 155043
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.5.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-11 19:08 UTC by whistlingturtle
Modified: 2023-10-26 14:24 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 whistlingturtle 2023-10-11 19:08:09 UTC
Description:
Among "File" | "Recent documents", after pressing the underlined number or letter of the document I want to re-open or switch to (or clicking on it, or using arrow-down and Enter), nothing happens if the document in question is already open. In that case, it used to switch (i.e. "bring me") to the window of the open document.
  
Tested on two machines. Also tested in safe mode. Also tested after resetting profile.

Steps to Reproduce:
1. Have at least two documents open. Let's say the currently displayed and focused one is "A".
2. Via the "File" menu, select "Recent documents" and, within the list that opens, select document "B".

Actual Results:
Nothing happens except for the menu closing.

Expected Results:
The main display should (and used to) switch to the window where document "B" is already open


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 7.5.6.2 (X86_64) / LibreOffice Community
Build ID: 50(Build:2)
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-CA (fr_CA.utf8); UI: fr-FR
Ubuntu package version: 4:7.5.6~rc2-0ubuntu0.22.04.1~lo1
Calc: threaded
______________________

First noticed the bug on Linux Mint 21.2 running LibreOffice v. 7.5.6.2, but verified it also exists on LO 7.6.2.1 (on another machine also running LM 21.2). This bug was not extant on LO v 7.3.7 and earlier. I don't know about versions between 7.3.7 and 7.5.6.2.
Comment 1 m_a_riosv 2023-10-11 23:04:47 UTC
Works for me
Version: 7.5.7.1 (X86_64) / LibreOffice Community
Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded
Version: 7.6.1.2 (X86_64) / LibreOffice Community
Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 9eb419b0b0f019f5fbc48ff1a11977e8b041edee
CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: es-ES (es_ES); UI: en-US
Calc: CL threaded Jumbo
Comment 2 Buovjaga 2023-10-25 11:21:18 UTC
Bibisected with linux-64-7.5 to 42d197ef301db68e56f7e45b6e36ace5fae04b4d, but there is an earlier report.

*** This bug has been marked as a duplicate of bug 155043 ***
Comment 3 whistlingturtle 2023-10-26 14:06:55 UTC
Linking this bug to 155043 is incorrect! They are different. 155043 concerns a bug that had been present since at least when I started using LibreOffice, i.e. 2016, whereas 157710 is a regression that was introduced after 7.3.7. Also, I had already stated (and I maintain) that the bug is still present in 7.6.2.1.
Comment 4 Buovjaga 2023-10-26 14:24:54 UTC
(In reply to whistlingturtle from comment #3)
> Linking this bug to 155043 is incorrect! They are different. 155043 concerns
> a bug that had been present since at least when I started using LibreOffice,
> i.e. 2016, whereas 157710 is a regression that was introduced after 7.3.7.
> Also, I had already stated (and I maintain) that the bug is still present in
> 7.6.2.1.

No, bug 155043 is about a regression that was introduced in 7.5, in 2022.

*** This bug has been marked as a duplicate of bug 155043 ***