GNOME Bugzilla – Bug 595007
arrow keys mostly do nothing
Last modified: 2009-09-16 05:33:13 UTC
I'm here to say that pressing an arrow key should always do something. It often does nothing. E.g., click on one of the cells in the spreadsheet. Its borders become thicker, meaning it is the current cell. Now press an arrow key. One would e.g., think a neighbor cell would then become the current cell, but instead nothing happens. I don't care what you make them do, but they should at least do something. Yes, when entering text, they move around. But in some other contexts, they do nothing. I'm talking about the four arrow keys on every PC 101 etc. keyboard. Yes I saw bug 137424.
Thanks for reporting this bug. This problem existed in one of the recent releases. That has been fixed in the current development version. (When you select a cell and use the arrow keys the selected cell is moved about.)
I found the reference. The bug existed in 1.9.11 (and possibly 1.9.10) and should be fixed in 1.9.12. If you are using a version other than 1.9.11 or 1.9.10 please reopen this bug.
$ apt-cache policy gnumeric gnumeric: Installed: 1.9.12-1 Candidate: 1.9.12-1 Version table: *** 1.9.12-1 0 500 http://ftp.tw.debian.org unstable/main Packages
I cannot replicate this in that version: $ apt-cache policy gnumeric gnumeric: Installed: 1.9.12-1 Candidate: 1.9.12-1 Version table: *** 1.9.12-1 0 990 http://debian.yorku.ca sid/main Packages 100 /var/lib/dpkg/status
Hmm, which version of libgoffice are you using? $ apt-cache policy libgoffice-0-8 libgoffice-0-8: Installed: 0.7.12-1 Candidate: 0.7.12-1 Version table: *** 0.7.12-1 0 990 http://debian.yorku.ca sid/main Packages 100 /var/lib/dpkg/status
Yes, same versions as you guys. But today... I can't reproduce it! Don't know why. Sorry. Closing.
Scroll Lock? (Specifically GDK_MOD5_MASK.) Gnumeric is one of the very few programs that recognize Scroll Lock and changes behaviour. Arrow keys scroll instead of move, for example.
I recall the arrow keys didn't do anything. So that must not be whatever it was that happened. OK, I'll reopen if it happens again.
Chances are that you had encountered the bug reported in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=546559
Probably... Ah, I should have reported downstream in the first place!
No you reported in teh right place. That bug was fixed by the upstream developers (Jean in this case) anyways. It just haqppened that the downstream report had an important detail.