Alt+Arrow in gnome-shell unexpectedly switches VTs

Bug #1726608 reported by Brian Murray
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
console-setup (Ubuntu)
Fix Released
High
Unassigned
Trusty
Confirmed
Undecided
Unassigned
Xenial
Confirmed
Undecided
Unassigned
Zesty
Won't Fix
Undecided
Unassigned

Bug Description

I'm experiencing a bug similar to bug 1710637 with Ubuntu 17.10 again.

Test Case
---------
schroot -u root -c trusty-amd64
edit /etc/apt/sources.list to xenial
apt-get update
apt-get install console-setup
use alt+tab to bring up the window switcher
then use alt+arrow to switch windows

I then end up at the gdm login screen or a virtual tty.

Installing a different set of packages, via apt-get dist-upgrade, actually ended up killing my desktop session.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 14:30:16 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' b"['<email address hidden>', 'multi-monitors-add-on@spin83', '<email address hidden>', '<email address hidden>']"
 b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'terminator.desktop', 'virt-manager.desktop', 'chromium-browser.desktop', 'firefox.desktop', 'simple-scan.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2013-01-16 (1741 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 :
Revision history for this message
Brian Murray (brian-murray) wrote :

I tried using Laney's kbd.c program from the other bug and it does show K_UNICODE. Additionally, passing it FIX did fix the situation.

Changed in gnome-shell (Ubuntu):
importance: Undecided → High
summary: - Alt + Arrow to switch windows takes me to gdm
+ Alt+Arrow in gnome-shell unexpectedly switches VTs
Revision history for this message
Iain Lane (laney) wrote :

Thanks for the report, but it's a console-setup and not a gnome-shell bug. It's changing the keyboard mode under our feet.

I'm excited that you can trigger this from a chroot. The reproducer seems kind of niche, but I guess it's up to you & cyphermox whether you'd like to backport the fixes to stables (and whether they need altering along the way).

affects: gnome-shell (Ubuntu) → console-setup (Ubuntu)
Changed in console-setup (Ubuntu):
status: New → Fix Released
Revision history for this message
Iain Lane (laney) wrote :

I think those series are right, although you might not be bothered about / need to care for Trusty.

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

I'm confused. This bug was reported against 17.10 and you're saying it's already fixed? That implies Brian hadn't updated since the fix on 19 September... ?!

Revision history for this message
Iain Lane (laney) wrote :

No. In the test case given, he uses packages in a chroot from an older release which don't have the fixes that were applied in artful.

Revision history for this message
Adam Conrad (adconrad) wrote :

The real question here is why a rule in a chroot is being executed by a udev outside the chroot. WTF, udev.

Revision history for this message
Adam Conrad (adconrad) wrote :

Oh, derp. It's not the udev rule, it's the console-setup postinst.

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

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

Changed in console-setup (Ubuntu Trusty):
status: New → Confirmed
Changed in console-setup (Ubuntu Xenial):
status: New → Confirmed
Changed in console-setup (Ubuntu Zesty):
status: New → Confirmed
Revision history for this message
Stephen Early (steve-greenend) wrote :

Yes - this happened to me after running debootstrap of 16.04 in a chroot.

Revision history for this message
Alessandro Cuttin (a-f-cuttin) wrote :

I can confirm, too, that 16.04 is affected.

Changed in console-setup (Ubuntu Zesty):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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