Bug 360144

Summary: Activities KCM: Activity configuration window cannot be focussed
Product: [Applications] systemsettings Reporter: Jonathan Marten <jjm>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: aspotashev
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Jonathan Marten 2016-03-05 20:57:37 UTC
When running the "kcm_activities" module (through systemsetting5 or using "kcmshell5 kcm_activities", the first "Activities" tab lists all of the configured activities.  To the right of each of them is a "configure" (spanner) and a "remove" (cross) button.

Clicking on the "configure" button appears to do nothing.  In reality it has opened an "Activity settings" window, but behind the initial window and unfocussed.  Moveing the initial window aside reveals this window, but it will not take focus and will not accept any interaction apart from the title bar buttons.

The message "kcmshell5[setFocus]: GeneralTab: Set focus called" is printed on stderr.


Reproducible: Always

Steps to Reproduce:
1.  Run "kcmshell5 kcm_activities" or open the appropriate module via systemsettings5.
2.  Click on the "configure" button of any activity.
3.  Move the initial window aside.


Actual Results:  
Hidden and unfocussable window appears as described.


Expected Results:  
It should be possible to focus and interact with the window that opens.


Actual systemsettings5 version: "systemsettings 5.6.90"

Not sure whether the bug classification is correct, but there is no component here for "kcm_activities" and no appropriate component under plasmashell either.

Window behaviour settings: Policy = Focus Follows Mouse - Mouse Precedence
Delay focus by = 0ms
Focus stealing prevention = Low
Raising windows = Raise on hover, delayed 550ms
Comment 1 Jonathan Marten 2016-04-17 12:54:02 UTC
Possibly similar to bug #355310
Comment 2 Jonathan Marten 2016-05-05 07:44:03 UTC
This now appears to have been fixed, as a result of commit ed53baa2 to kde-cli-tools.