| Summary: | Virtual keyboard not showing | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Andrei Kozlov <akozlov> |
| Component: | virtual-keyboard | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.26.2 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
konsole
kate |
||
|
Description
Andrei Kozlov
2022-11-08 07:59:34 UTC
Created attachment 153575 [details]
konsole
Created attachment 153576 [details]
kate
Are you using the X11 session or the Wayland session? (In reply to Nate Graham from comment #3) > Are you using the X11 session or the Wayland session? I am using Wayland session. 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. (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? Yes, windows always use the configured window placement; this isn't automatically adjusted for touch use cases. (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. What do you mean in the mobile session? (In reply to Nate Graham from comment #9) > What do you mean in the mobile session? Plasma Mobile session In Plasma Mobile session, all applications always should be fullscreen 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.
|