Switching between files in Nautilus using keyboard pointers leads to incorrectly chosen file.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nautilus (Ubuntu) |
New
|
Low
|
Unassigned |
Bug Description
## Summary
Switching between files in Nautilus using keyboard pointers leads to incorrectly chosen file.
Unfortunately I was unable to get debug log from the terminal.
## Prerequisites
Ubuntu 18.04 Desktop version is instilled, with GNOME nautilus 3.26.3, nautilus-sendto 3.8.6.
## Steps to reproduce
1) Open nautilus (by clicking on nautilus icon, or by typing "nautilus . &" in a terminal
2) Open a folder with many files that have similar names
(reproduced on:
* lectures with file names {1..10}-{01..20} "name of the lecture"
* pictures, with names as follows DSC{00000.
3) Select a file in the end of a row and press "->" (right) keyboard pointer, to (presumably) navigate to the next row. (I also noticed, that if the issue is not reproduced easily, zooming in/out in the folder increases the probability of the bug)
## Actual result
If the last file in a row is selected and right pointer button is pressed on the keyboard (sometimes) selection jumps not to the next row, but 2-5 rows ahead.
In the screenshot attached, it jumped from a file named "2-01 Introduction.mp3" to file named "3-08 An Implicit Agreement.mp3"
# Expected result
The selection should jump to the next row, regardless of file names, zoom or other factors.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSign
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 21 23:20:13 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
b'org.
b'org.
b'org.
b'org.
InstallationDate: Installed on 2018-05-24 (28 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
Thank you for your bug report, the issue seems simlar to bug #1774744