Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 582356

Summary: gentoo-systemd-integration-6 causes keyboard 's' and 'l' to activate gnome shortcuts (help and on-screen-keyboard )
Product: Gentoo Linux Reporter: Piotr Frątczak <piotr4f>
Component: [OLD] Core systemAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Severity: major    
Priority: Normal    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Package list:
Runtime testing required: ---

Description Piotr Frątczak 2016-05-07 15:57:56 UTC
After upgrade or initial install of version gentoo-systemd-integration-6 make it impossible to enter the non-capital letter 's' and 'l' which cause the activation of on-screen-keyboard and help instead. 

Reproducible: Always

Steps to Reproduce:
1. emerge gentoo-systemd-integration-6
2. press letter "s" or "l" on the keyboard either in gdm or gnome-session
Actual Results:  
gnome on-screen-keyboard 
gnome help 

Expected Results:  
letter s
letter l

to override it use:
CAPS + shift s
CAPS + shift l
or set values which are empty by default
gsettings set help 'XFNONE'
gsettings set on-screen-keyboard 'XFNONE'

or deactivate totally media-key
gsettings set active false
or mask this version and reemerge gentoo-systemd-integration
Comment 1 Piotr Frątczak 2016-05-07 18:27:05 UTC
gentoo-systemd-integration-6 - I'm not sure if that is the reason. After downgrade and restoring empty 
gsettings get help ''
settings get on-screen-keyboard ''
everything seemed fixed, but after reboot still broken
Comment 2 Mart Raudsepp gentoo-dev 2016-05-07 20:06:44 UTC
I believe this is duplicate of bug 560346 then. It would be really nice if you would be able to help track down the root cause, as I believe none of us (the gnome team) are able to reproduce, so this has been rather an annoying bug for a limited set of our users with only workarounds available, not a fix :(
Unless this bug is something different, please continue on 560346 then if you have any additional information that might help debug this issue; if this is actually something different despite the same workaround and symptoms, please re-open this one.

*** This bug has been marked as a duplicate of bug 560346 ***