Bug 461577 - Virtual keyboard not showing
Summary: Virtual keyboard not showing
Status: RESOLVED INTENTIONAL
Alias: None
Product: kwin
Classification: Plasma
Component: virtual-keyboard (other bugs)
Version First Reported In: 5.26.2
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-08 07:59 UTC by Andrei Kozlov
Modified: 2022-11-08 20:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
konsole (70.49 KB, image/png)
2022-11-08 08:13 UTC, Andrei Kozlov
Details
kate (41.80 KB, image/png)
2022-11-08 08:14 UTC, Andrei Kozlov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei Kozlov 2022-11-08 07:59:34 UTC
A touchscreen notebook. The virtual keyboard is not displayed if an application launched from konsole using a physical keyboard. Similar behavior if you run an application from krunner using a physical keyboard

STEPS TO REPRODUCE
1. Launch konsole (keyboard is displayed)
2. Launch kate from konsole using the physical keyboard

OBSERVED RESULT
Kate started, virtual keyboard is not displayed

EXPECTED RESULT
Kate started, virtual keyboard is displayed


SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.26.2
Comment 1 Andrei Kozlov 2022-11-08 08:13:19 UTC
Created attachment 153575 [details]
konsole
Comment 2 Andrei Kozlov 2022-11-08 08:14:33 UTC
Created attachment 153576 [details]
kate
Comment 3 Nate Graham 2022-11-08 17:42:27 UTC
Are you using the X11 session or the Wayland session?
Comment 4 Andrei Kozlov 2022-11-08 17:44:53 UTC
(In reply to Nate Graham from comment #3)
> Are you using the X11 session or the Wayland session?

I am using Wayland session.
Comment 5 Nate Graham 2022-11-08 17:51:28 UTC
Thanks.

In that case this is intentional; when you launch an app using a pointing device or physical keyboard, we assume you want to interact with it using those devices. If you want to use a virtual keyboard immediately upon launching an app, launch it using a touchscreen tap.
Comment 6 Andrei Kozlov 2022-11-08 18:00:29 UTC
(In reply to Nate Graham from comment #5)
> Thanks.
> 
> In that case this is intentional; when you launch an app using a pointing
> device or physical keyboard, we assume you want to interact with it using
> those devices. If you want to use a virtual keyboard immediately upon
> launching an app, launch it using a touchscreen tap.

Kate and other apps are not show fullscreen. Is it normal?
Comment 7 Nate Graham 2022-11-08 18:16:13 UTC
Yes, windows always use the configured window placement; this isn't automatically adjusted for touch use cases.
Comment 8 Andrei Kozlov 2022-11-08 20:10:36 UTC
(In reply to Nate Graham from comment #7)
> Yes, windows always use the configured window placement; this isn't
> automatically adjusted for touch use cases.

I forgot to specify this behavior in the mobile session.
Comment 9 Nate Graham 2022-11-08 20:12:24 UTC
What do you mean in the mobile session?
Comment 10 Andrei Kozlov 2022-11-08 20:15:14 UTC
(In reply to Nate Graham from comment #9)
> What do you mean in the mobile session?

Plasma Mobile session
Comment 11 Andrei Kozlov 2022-11-08 20:16:05 UTC
In Plasma Mobile session, all applications always should be fullscreen
Comment 12 Nate Graham 2022-11-08 20:17:54 UTC
It's the same thing, then; KWin doesn't do anything different here in Plasma Desktop vs Plasma mobile. If you use a physical keyboard or a pointing device to open an app, we assume that's the input you want to use, so we don't need to show a virtual keyboard.

> In Plasma Mobile session, all applications always should be fullscreen
That sounds like a topic for a different bug report, because this one was about the virtual keyboard.