Alt + Tab then Alt + Right / Left arrow logs me out

Bug #1716415 reported by Brian Murray
This bug report is a duplicate of:  Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

One of my systems if I use Alt + Tab to launch the window switcher and then use Alt + Right or Left arrow to switch windows I either receive a tty or get the gdm lock screen. Neither behavior is what I'd expect - the key stroke moving through the window list. This seems to work on another system of mine and certainly did work on this system (otherwise I wouldn't be using the key stroke) so perhaps a package was updated and I haven't rebooted yet?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Sep 11 07:32:15 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-01-16 (1698 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Brian Murray (brian-murray) wrote :
tags: added: gnome-17.10
Revision history for this message
Brian Murray (brian-murray) wrote :

After a reboot of my desktop, the key stroke no longer causes the tty switching. I'll keep an eye for any changes / updates that cause it again.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote : Re: [Bug 1716415] Re: Alt + Tab then Alt + Right / Left arrow logs me out

On Wed, Sep 13, 2017 at 01:02:14AM -0000, Daniel van Vugt wrote:
> ** Changed in: gnome-shell (Ubuntu)
> Status: New => Incomplete

Why is this incomplete? I recall it happening during more than one
session and it seems like a rather horrible bug to me (although I might
be biased).

--
Brian Murray

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Because in comment #2 suggested you could not reproduce the problem any more. Generally if there's a chance that some update has fixed a bug then the best approach is to set it to incomplete and see if the problem reoccurs in the following 60 days. That way it closes itself rather than adding to the backlog.

But if you want it open then no problem.

Changed in gnome-shell (Ubuntu):
status: Incomplete → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Duplicate of bug 1508146 maybe?

Revision history for this message
Joe (joemugen) wrote :

I'm experiencing this problem since months, the only "one time" fix when it occurs I found is :

sudo sh -c 'dumpkeys |grep -v cr_Console |loadkeys'

Until the next reboot...
But it's better than nothing, right?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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