Ubuntu
libreoffice package

(LibreOffice Calc) Pressing Enter fails to shift cursor down after a Copy-Paste

Bug #1983779 reported by blueapple128
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LibreOffice
Confirmed
Wishlist
libreoffice (Ubuntu)
New
Undecided
Unassigned

Bug Description

Steps to reproduce:
- (LibreOffice Calc) Copy any cell and Paste its contents to any cell.
- Then, press Enter any number of times.

Expected behavior:
- The cursor shifts down by 1 cell on each Enter press.

Actual behavior:
- The cursor does not move on any of the Enter presses.

Thanks!

$ lsb_release -rd
Description: Ubuntu 20.04.4 LTS
Release: 20.04

$ apt-cache policy libreoffice-calc
libreoffice-calc:
  Installed: 1:6.4.7-0ubuntu0.20.04.4
  Candidate: 1:6.4.7-0ubuntu0.20.04.4
  Version table:
     1:7.2.7-0ubuntu0.21.10.1~bpo20.04.1 100
        100 http://us.archive.ubuntu.com/ubuntu focal-backports/main amd64 Packages
 *** 1:6.4.7-0ubuntu0.20.04.4 500
        500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1:6.4.2-0ubuntu3 500
        500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

$ apt-show-versions -r libreoffice*
libreoffice-base-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-calc:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-core:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-draw:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-gnome:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-gtk3:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-help-common:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-help-en-gb:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-help-en-us:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-help-zh-cn:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-help-zh-tw:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-impress:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-l10n-en-gb:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-l10n-en-za:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-l10n-zh-cn:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-l10n-zh-tw:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-math:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-ogltrans:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-pdfimport:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-style-breeze:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-style-colibre:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-style-elementary:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-style-tango:all/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate
libreoffice-writer:amd64/focal-security 1:6.4.7-0ubuntu0.20.04.4 uptodate

No extensions installed.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice-calc 1:6.4.7-0ubuntu0.20.04.4
ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192
Uname: Linux 5.4.0-122-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 7 05:26:52 2022
InstallationDate: Installed on 2020-01-17 (933 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: Upgraded to focal on 2020-08-01 (736 days ago)

Revision history for this message
In , Sworddragon2 (sworddragon2) wrote :

In Calc copying a field and pasting it to another field disables temporarily navigation down with Enter or to right with Tab. Clicking with the mouse on another field solves this issue until the next paste appears.

Revision history for this message
In , Owen-genat (owen-genat) wrote :

I am not sure what "field" in this report refers to, however there does appear to have been a general change in behaviour between v3.3 and v3.4 with respect to how the ENTER key is interpreted after performing a copy/paste action. This may be what this bug is referring to however until this can be clarified I am setting the status to NEEDINFO.

My understanding of problem:

1. Start Calc.
2. Enter "abc" in cell A1.
3. Copy (CTRL+C) this cell.
4. Move selection to cell B1.
5. Paste (CTRL+V) - places copied value into B1, cell is highlighted.
6. ENTER unhighlights cell B1.
7. Subsequent use of ENTER/TAB is as expected i.e., move selection either down or to the right.

Under Ubuntu 10.04 x86_64 running v3.3.0.4 OOO330m19 Build: 6 and Crunchbang 11 x86_64 running v3.3.4.1 OOO330m19 Build: 401 those steps describe the behaviour. Under Ubuntu 10.04 x86_64 running:

- v3.4.6.2 OOO340m1 Build: 602
- v3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b
- v3.6.7.2 Build ID: e183d5b
- v4.0.6.2 Build ID: 2e2573268451a50806fcd60ae2d9fe01dd0ce24
- v4.1.3.2 Build ID: 70feb7d99726f064edab4605a8ab840c50ec57a

... the behaviour is different. After step 5:

6. ENTER does not remove cell highlighting (it removes moving dashes from around A1).
7. Subsequent use of ENTER/TAB does nothing - a cursor key or mouse click is required to move the selector to another cell.

It is possible this is a bug that overrides the setting under Tools > Options > LbreOffice Calc > General > Input settings section > Press ENTER to move selection "Down".

Revision history for this message
In , Sworddragon2 (sworddragon2) wrote :

> I am not sure what "field" in this report refers to

I was refering to cell.

> 6. ENTER does not remove cell highlighting (it removes moving dashes from around A1).
> 7. Subsequent use of ENTER/TAB does nothing - a cursor key or mouse click is required to move the selector to another cell.

This is what I'm seeing too on LibreOffice 4.1.3.2.

> It is possible this is a bug that overrides the setting under Tools > Options > LbreOffice Calc > General > Input settings section > Press ENTER to move selection "Down".

"Press Enter to move selection" is enabled and the dropdown field is set to Down but the cell selection is still not moving on pressing enter after pasting something.

Revision history for this message
In , Owen-genat (owen-genat) wrote :

Thanks for responding and clarifying the "field" matter. I had the same setting for Press ENTER to move selection, so confirmed. Status set to NEW. Component set to Spreadsheet. Version set to 3.4.6 release per comment #1. Possible regression.

Revision history for this message
In , Owen-genat (owen-genat) wrote :

Summary edited for clarity.

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice (4.4.1 or later)
   https://www.libreoffice.org/download/

   *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

   *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

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)

http://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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-18

Revision history for this message
In , Sworddragon2 (sworddragon2) wrote :

I'm still able to reproduce this issue with LibreOffice 4.4.2.2 on Linux 3.19.3 (x86_64).

Revision history for this message
In , Raal (raal) wrote :

*** Bug 90970 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice
(5.1.5 or 5.2.1 https://www.libreoffice.org/download/

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

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave
a short comment that includes your version of LibreOffice and Operating System

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)

http://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: http://webchat.freenode.net/?channels=libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug-20160920

Revision history for this message
In , Emo-assenov (emo-assenov) wrote :

Reproducible in
Version: 5.4.1.2 (x64)
Build ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

** Please read this message in its entirety before responding **

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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

Revision history for this message
In , Thomas-lendo (thomas-lendo) wrote :

Still reproducible.

Version: 6.2.0.0.alpha1+
Build-ID: e33424dd887cb1a11a3dba2513ef0f4bf93a6dbe
CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3;
Gebietsschema: de-DE (de_DE.UTF-8); Calc: threaded
from today

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

Dear sworddragon2,

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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

Revision history for this message
In , Qa-admin-q (qa-admin-q) wrote :

Dear sworddragon2,

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

Revision history for this message
blueapple128 (blueapple128) wrote :
Bug Watch Updater (bug-watch-updater)
Changed in df-libreoffice:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
In , Stephane-guillou-i (stephane-guillou-i) wrote :

*** Bug 155277 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Stephane-guillou-i (stephane-guillou-i) wrote :

*** Bug 143223 has been marked as a duplicate of this bug. ***

Bug Watch Updater (bug-watch-updater)
Changed in df-libreoffice:
importance: Medium → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.