Neither PrintScreen, SHIFT+PrintScreen, nor CTRL+PrintScreen keyboard shortcuts work on Trusty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-settings-daemon (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Running Ubuntu 14.04 64 bit with the latest updates. Version of unity-settings-
I expected PrintScreen to take a screenshot. Ditto for CTRL+PrintScreen and ALT+PrintScreen. All my settings under Keyboard Shortcuts are normal.
Everything worked for every prior release of Ubuntu with the Print key taking a screenshot. Also, neither CTRL+PrintScreen nor SHIFT+PrintScreen work at all. If you reassign the keys for taking a screenshot, to any other keys, gnome-screenshot works as expected. Assigning either of those three key/key combinations to any command does not work. ALT+PrintScreen strangely enough works without issue. Running gnome-screenshot from the terminal also works without issue. Unlike the other bugs I've seen that sound similar, I do not hear a sound at all when pressing any of those three key combinations. Toggling the magic sysrq key does nothing for this issue either.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-settings-
Uname: Linux 3.14.1-
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 23 15:13:53 2014
InstallationDate: Installed on 2014-04-17 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: unity-settings-
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
mtime.conffile.
mtime.conffile.
summary: |
- Neither Print, SHIFT+Print, nor CTRL+Print keyboard shortcuts work on - Trusty + Neither PrintScreen, SHIFT+PrintScreen, nor CTRL+PrintScreen keyboard + shortcuts work on Trusty |
description: | updated |
Also this only effects my HP dv7-4285dx laptop after fresh install, and my desktop seems to work fine. I Googled and saw that several KDE users some months ago had a similar issue. So maybe it's related to X, systemd, or something else at the low level? A lot of the users reporting the issue reported that they experienced it only on certain machines, and in every case it was a HP laptop in the dv-whatnot series. This may help trace the problem down.