Bug 359803

Summary: KRunner offers dialog does not close on starting Kate with Kate showing its session dialog
Product: [Plasma] krunner Reporter: Friedrich W. H. Kossebau <kossebau>
Component: generalAssignee: Vishesh Handa <me>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde
Priority: NOR    
Version First Reported In: 5.5.1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Friedrich W. H. Kossebau 2016-02-25 18:48:19 UTC
When starting Kate via KRunner, by typing "kate" and selecting "Kate" application in the offers, the KRunner view with the enter field and the offers does not close immediately after selecting the "Kate" application entry. At least when using Kate with the option to show its session selection dialog on start.
Instead KRunner stays open on top of all windows (but not blocking) until Kate's session selection dialog is closed. Only then it closes as well.

(Very possibly related, so not opening a separate bug:
when instead selecting "Quit" in Kate's session selection dialog, KRunner then shows a message box with "KDEInit could not launch '/usr/bin/kate'" and only closes its view once that message is "okay"ed.)

Reproducible: Always

Steps to Reproduce:
Prerequisite:
1. Open Kate settings, select Application/Sessions page
2. For "Behaviour on Application Startup" select "Manually choose a session"
3. Accept settings

Actual problem:
1. Alt+F2
2. Enter "kate"
3. Select "Kate" from apps sections in the offer list

Actual Results:  
Kate starts and shows its session chooser dialog.
Krunner offer list is still shown, and above the dialog.
Krunner only closes its view, once a session is selected in Kate's dialog and the Kate mainwindow appears.

Expected Results:  
KRunner closes its view before the Kate session chooser dialog appears.
Comment 1 Kai Uwe Broulik 2016-04-21 19:31:46 UTC
Marking this as duplicate of the other one although it's older because I already moved that one to KIO :)

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