Bug 1411099 - Hotkeys stopped working in version 5.29
Summary: Hotkeys stopped working in version 5.29
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kf5-kglobalaccel
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daniel Vrátil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-08 11:52 UTC by Vitaly
Modified: 2017-01-08 22:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-08 22:20:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vitaly 2017-01-08 11:52:11 UTC
Description of problem:
After updating kf5-* from 5.27 to 5.29 all hotkeys in all applications (both Qt/GTK) stopped working.


Version-Release number of selected component (if applicable):
kf5-* 5.29-1.fc25


How reproducible:
Always.


Steps to Reproduce:
1. Open any text editor, KWrite for example.
2. Press Ctrl+S to save file or Ctrl+F to find text.
3.

Actual results:
It will print S, F, etc. to text area instead of executing hotkey.


Expected results:
Open/Find dialog must be opened.


Additional info:

Comment 1 Raphael Groner 2017-01-08 12:08:17 UTC
I wonder why karma +10 then?

https://bodhi.fedoraproject.org/updates/FEDORA-2016-06be5d9fb4

Comment 2 Vitaly 2017-01-08 12:31:47 UTC
I don't know. Full list of packages updated yesterday (from dnf history): https://paste.fedoraproject.org/522590/78492148/

After this update hotkeys stopped working for me.

Comment 3 Vitaly 2017-01-08 14:27:42 UTC
Ctrl key is now working at all in all applications.

Comment 4 Rex Dieter 2017-01-08 14:39:28 UTC
OK, closing per comment #3

Comment 5 Rex Dieter 2017-01-08 21:29:15 UTC
Based on some irc comments, I'm guessing the "now" in comment #3 was meant as "not", so... re-opening.

Comment 6 Vitaly 2017-01-08 22:20:53 UTC
I fixed this problem. My Xorg config was damaged by unknown application or driver (I think by NVIDIA config tool). I restored it from backup and now everything works fine.


Note You need to log in before you can comment on or make changes to this bug.