Can't type numbers in the evolution search box

Bug #1721833 reported by Joe Barnett
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
Medium
evolution (Ubuntu)
Fix Released
Medium
Unassigned
Artful
In Progress
Medium
Unassigned

Bug Description

Trying to type numeric characters into the evolution search box is not working when using the numeric keys above the letters on the keyboard. Shift+numeric key for a special symbol works, and then numpad keys work, but the "regular" number keys don't appear to do anything.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evolution 3.26.1-1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Oct 6 10:35:25 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-21 (777 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Joe Barnett (thejoe) wrote :
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Works fine here with Ubuntu 17.10.

Revision history for this message
Musee "lae" Ullah (sleepingkyoto) wrote :

I have the same issue. I could not input 1234560 (789 functioned fine). This seems to have been introduced between 3.24.5 and 3.26.1. I'm on Arch Linux with i3 as my window manager.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in evolution (Ubuntu):
status: New → Confirmed
Revision history for this message
thatguruguy (thatguruguy) wrote :

"Works fine here with Ubuntu 17.10."

It doesn't work HERE with Ubuntu 17.10.

Revision history for this message
thatguruguy (thatguruguy) wrote :

I've noticed that this problem only exists when using Wayland; it doesn't happen when using Ubuntu on Xorg or Unity.

Revision history for this message
Joe Barnett (thejoe) wrote :

I can confirm the same as @sleepingkyoto, that 789 work fine.

Revision history for this message
luke16 (l16) wrote :

It is also happening to me on X11 with Ubuntu 17.10 running vanilla Gnome Session.
The only numbers that work are 6,7,8 and 9.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

This will be fixed in evolution 3.26.2.

Changed in evolution (Ubuntu):
status: Confirmed → Fix Released
importance: Undecided → Medium
Changed in evolution (Ubuntu Artful):
status: New → Triaged
importance: Undecided → Medium
Changed in evolution:
importance: Unknown → Medium
status: Unknown → Fix Released
Jeremy Bícha (jbicha)
Changed in evolution (Ubuntu Artful):
status: Triaged → In Progress
Revision history for this message
fermulator (fermulator) wrote :

@jbicha; how can we get this fix delivered into Ubuntu Artful stable? - this has been fixed since Nov2017, and still yet delivered into Ubuntu 17.10

Revision history for this message
Michael Neuling (mikey-neuling) wrote :

+1

The lack of updates to simple yet annoying problems in Evolution is the number one reason I'm moving to Fedora next time I install my laptop. Seems to happen every release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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