Bug 474910 - Virtual keyboard too large for screen
Summary: Virtual keyboard too large for screen
Status: RESOLVED DUPLICATE of bug 440571
Alias: None
Product: kwin
Classification: Plasma
Component: virtual-keyboard (show other bugs)
Version: 5.27.8
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-26 16:52 UTC by rob.dyck
Modified: 2023-10-25 21:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Scren image (2.67 MB, image/jpeg)
2023-09-27 22:27 UTC, rob.dyck
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rob.dyck 2023-09-26 16:52:09 UTC
Summary
I have a convertible laptop. When in tablet mode ( actually either mode ) if the virtual keyboard is invoked, its right side extends beyond the screen.

STEPS TO REPRODUCE
1. Enable virtual keyboard
2. Tap on field that requires text input


OBSERVED RESULT
The virtual keyboard appears but is unusable because part of the right side is off the screen. It also covers the panel on the right side of the screen.


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 rob.dyck 2023-09-26 16:58:33 UTC
Linux 6.4.15
Fedora 38
Plasma 5.27.8
Frameworks 5.109
QT 5.15.10
Comment 2 rob.dyck 2023-09-26 17:14:20 UTC
Plasmashell dies when virtual keyboard is dismissed. Plasama shell actually dies often with no apparent triggers.
Comment 3 Nate Graham 2023-09-27 21:54:51 UTC
Can you attach a screenshot that shows the issue?
Comment 4 rob.dyck 2023-09-27 22:27:44 UTC
Created attachment 161922 [details]
Scren image

Spectacle and the virtual keyboard seem to be mutually exclusive. I am attaching a photo.
Comment 5 Nate Graham 2023-09-28 19:03:04 UTC
Aha, this.

*** This bug has been marked as a duplicate of bug 459000 ***
Comment 6 Nate Graham 2023-10-25 21:15:53 UTC

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