This is a regression from v5.4. 1. Go to File -> Recent Documents 2. Press 1 The first file should open, but nothing happens in Calc 6.2.
no repro Version: 5.4.1.2 Build ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: kde4; Locale: nl-BE (en_US.UTF-8); Calc: group Version: 6.1.4.0.0+ Build ID: 8b141eb612a89a112b9bb11baeff32155e4a0150 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: kde4; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-6-1, Time: 2018-11-28_11:46:02 Locale: nl-BE (en_US.UTF-8); Calc: group threaded Version: 6.2.0.0.beta1+ Build ID: 7c95a895983b93d7eff7ecd3eaa07f2830e15e94 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk2; Locale: nl-BE (en_US.UTF-8); UI-Language: en-US Calc: threaded
Maybe it's language-dependent? I'm using en-US.
when changing language to en_US no repro Version: 5.4.1.2 Build ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: kde4; Locale: en-US (en_US.UTF-8); Calc: group Version: 6.0.7.3 Build ID: dc89aa7a9eabfd848af146d5086077aeed2ae4a5 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: kde4; Locale: en-US (en_US.UTF-8); Calc: group
Cannot reproduce the bug in (en_US) Version: 6.0.6.2 Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 CPU threads: 2; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: group
(In reply to Durgapriyanka from comment #4) > Cannot reproduce the bug in (en_US) > > Version: 6.0.6.2 > Build ID: 0c292870b25a325b5ed35f6b45599d2ea4458e77 > CPU threads: 2; OS: Windows 6.1; UI render: default; Thanks for testing on Windows. I see the bug on Ubuntu. Here's an exact sequence of key presses after launching Calc: Alt+F u 1 Result: nothing happens. Expected result: the first recent document should open. If I press right arrow while after the Recent Documents menu expands, then the 1, 2, 3, ... accelerators do work. So this key sequence does open the most recent document in LibreCalc 6.2 on Ubuntu en_US: Alt+F u Right arrow 1
I can no longer reproduce this bug in 6.2.0.1 on Ubuntu 18.04.