Bug 132828 - FILEOPEN CSV in Calc now requires mouse or 20 key presses (regression)
Summary: FILEOPEN CSV in Calc now requires mouse or 20 key presses (regression)
Status: RESOLVED DUPLICATE of bug 131076
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.3.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-07 20:20 UTC by Marco van Zwetselaar
Modified: 2020-05-08 14:14 UTC (History)
1 user (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 Marco van Zwetselaar 2020-05-07 20:20:42 UTC
Description:
One of LibreOffice Calc's strong points has always been the ease of working with CSV/TSV files.  Just open the file, hit the Enter key in the "Text Import" dialog that appears, done!

Since 6.4.3, this doesn't work any more.  Pressing Enter in the Text Import dialog now opens a dropdown list of Character sets.  The cause is that the default focus in that dialog is not the OK button, but the Character Set dropdown.

For those who do/ not use a mouse now requires pressing Tab 19 times till the focus is on the OK button, followed by the Enter.

Steps to Reproduce:
Either 
1. In Calc: press Alt+F O, pick any CSV file, hit Enter.
2. The Text Import dialog appears. Hit Enter.

Or:
1. From commandline: xdg-open somefile.csv
2. The Text Import dialog appears. Hit Enter.

Actual Results:
A long drop down list of Character Encodings opens.

Expected Results:
The dialog closes, and the CSV is open in Calc.


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
Version: 6.4.3.2
Build ID: 1:6.4.3-0ubuntu0.20.04.1
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
Calc: threaded
Comment 1 Ming Hua 2020-05-07 22:38:22 UTC
Hi Marco, thanks for reporting this bug.

When you say "Since 6.4.3, this doesn't work any more", which version were you comparing to?  A similar issue was reported as bug 131076, but that was for versions 6.4.0 to 6.4.2, and should have been fixed for 6.4.3.

Or maybe Ubuntu is doing funny things with their package version number...
Comment 2 Ming Hua 2020-05-07 22:45:43 UTC
(In reply to Ming Hua from comment #1)
> Or maybe Ubuntu is doing funny things with their package version number...
According to http://changelogs.ubuntu.com/changelogs/pool/main/libr/libreoffice/libreoffice_6.4.3-0ubuntu0.20.04.1/changelog the reporter's version is indeed based on 6.4.3 final release, so this should not happen.
Comment 3 Marco van Zwetselaar 2020-05-08 08:48:47 UTC
Dear Ming Hua, thank you for the fabulously swift response.  

This is indeed a duplicate of bug 131076, with apologies, though there now is the mystery why (if this had indeed been solved in 6.4.3) the issue occurs in the Ubuntu package.

I recently upgraded from Ubuntu 18.04 to 20.04.  It is a bog standard installation, with no extraneous software installs or PPA's.

Shall I report this against the Ubuntu package?  Are we certain that it was fixed in 6.4.3?
Comment 4 Ming Hua 2020-05-08 11:38:05 UTC
(In reply to Marco van Zwetselaar from comment #3)
> Shall I report this against the Ubuntu package?
It's up to you.  If Ubuntu has active bug triagers and testers for their libreoffice package it would be useful.  However from my limited experience that doesn't seem to be the case.

> Are we certain that it was fixed in 6.4.3?
Unfortunately looking at that bug I can't say I'm 100% certain.  This bug is GTK specific so only Linux users can test, and I'm a Windows user.

If you have time and are not afraid of tweaking your system, you can try installing the LibreOffice official 6.4.3 packages from https://www.libreoffice.org/download/download/ (It installs into /opt and can be uninstalled later) and see if they are any different from the Ubuntu ones.

If you can't test that, we'll have to wait another Linux user to either reproduce your issue or confirm the fix.  I'll write a comment in the other bug to see if there's anyone available there.
Comment 5 Ming Hua 2020-05-08 12:19:44 UTC
(In reply to Ming Hua from comment #4)
> (In reply to Marco van Zwetselaar from comment #3)
> > Are we certain that it was fixed in 6.4.3?
> Unfortunately looking at that bug I can't say I'm 100% certain.  This bug is
> GTK specific so only Linux users can test, and I'm a Windows user.
Another user reported that this is NOT fixed for 6.4.3.  Let's mark this as DUPLICATE and move all the follow-up to the other bug.

*** This bug has been marked as a duplicate of bug 131076 ***
Comment 6 John Hills 2020-05-08 14:14:32 UTC
I can confirm that this bug is fixed in 6.4.3.2 from on Debian buster-backports