From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on sa.local.altlinux.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU autolearn=ham autolearn_force=no version=3.4.1 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=matos-sorge.com; s=mail; t=1491820869; bh=EfuvNFW95LphvS1jCfwANcE6x/3p92zVO19beZu+CEI=; h=To:From:Subject:Date:From; b=WJUgiV4dmi3QBoxvwu1JVCgfN1bYSbrOkmYsi2PjUr4pYPSklI9rKEF/x6ePFtmhQ VqJe8s8vYyDgHTBMjytwG130cx53jwCZkR5If1Z/+D31f8O2Kx1Iwyj1Epvg1ciBUj OpUkVpnqoPRdAzV7cwyUU5H8aF4w8opwQPQ32HJTQSwJrzAQOD6oVWSyN3CTOXirac 4dzWKzUb8jlweXBQ2zxYa+Fs4C4vV4fy8MhWwAGZZeMmaJKSMANxtj6VLmZEQoVkM4 mt9mDPBFWNYU5ud0wrI+0I1pSPKSMIJBl5EbjKkAKHYYgq+//Dc2vzdiBjKNQs4jke Kk6JSFhMw8ShA== To: kbd@lists.altlinux.org From: Paulo Matos Message-ID: <56fe2dea-8f25-49c6-3e06-47a408554f55@matos-sorge.com> Date: Mon, 10 Apr 2017 12:41:08 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [kbd] Backspace code not being passed on to apps X-BeenThere: kbd@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Linux console tools development discussion List-Id: Linux console tools development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Apr 2017 10:41:11 -0000 Archived-At: List-Archive: Hello, I hope this is the correct place to ask this question. Please keep reading (I understand that you have rolled your eyes as soon as you saw the 'backspace' word). Long story short, the kernel is not passing on backspace information to the system. Kernel is 4.10.8-200.fc25.x86_64. During normal running operation after my disk filled up and fedora failed to upgrade backspace stopped working. However, I can't tell for certain it was because disk space filled up. It just suddenly happened. xev, showkeys and evtest do not show any key code for backspace. journalctl does not show unknown key message and I used wireshark to prove that usb does send keycode showing this is not a hardware problem. So, when I press backspace 0x81 usb endpoint sends 0x2a to the kernel or whoever receives these messages from the usb device (my point is that the code gets into the software from the usb device). From this point onward nothing seems to happen to this code. My question is, what should my steps be in order to diagnose what's happening with the key inside the kernel? Kind regards, -- Paulo Matos