Bug 485770

Summary: Menus displayed off-screen
Product: [Plasma] kwin Reporter: pallaswept <pallaswept>
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: normal CC: christoph, pallaswept
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Inaccessible menus in Kate
Display configuration suspected to trigger this bug

Description pallaswept 2024-04-19 02:13:18 UTC
Created attachment 168661 [details]
Inaccessible menus in Kate

SUMMARY

Attempted to set the language of a file, found the menu to be taller than the monitor, with a scrollbar button visible at the bottom, but not at the top, so the top of the menu was never accessible. Screenshot attached for reference.

I suspect this is another case of my monitor layout causing problems. The monitors are of different resolutions and do not share a base line. See second screenshot attached. The way this is behaving, kate on my lower and smaller 1080p monitor, mistakenly assumes that the top of the monitor, is where the top of the desktop is.


STEPS TO REPRODUCE
1. Arrange monitors as illustrated (? assuming this is necessary)
2. Start Kate
3. Open a tall menu

OBSERVED RESULT

Inaccessible menus

EXPECTED RESULT

Accessible menus (cropped to appropriate size, scroll buttons present, etc)


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Tumbleweed
(available in About System)
KDE Plasma Version:  6.0.3
KDE Frameworks Version:  6.1.0
Qt Version:  6.7.0
Comment 1 pallaswept 2024-04-19 02:14:07 UTC
Created attachment 168662 [details]
Display configuration suspected to trigger this bug
Comment 2 pallaswept 2024-04-19 02:17:36 UTC
Testing this on the second, larger, topmost display, I notice that the opposite issue occurs - the menus do not expand to the full available height of the monitor, instead stopping short, and the use of the scroll buttons causes the menu to scroll and then the menu re-sizes itself out from under the mouse. Very glitchy.
Comment 3 Christoph Cullmann 2024-06-16 22:37:19 UTC
Hi, that is outside of our hands, if that needs to be improved, one must report that upstream to Qt.
Comment 4 pallaswept 2024-06-17 06:52:26 UTC
(In reply to Christoph Cullmann from comment #3)
> Hi, that is outside of our hands, if that needs to be improved, one must report that upstream to Qt.

Thanks for looking at this for us Christoph!

I had a feeling that this might be upstream, as this issue appears to effect various apps, eg https://bugs.kde.org/show_bug.cgi?id=468794

I took a look at Qt's bug reporting, but they ask for a lot of info that's a bit above my capacity as an end-user. I am really not tooled to give them things like example code to reproduce. They're pretty clear that the quality (or lack thereof) that I could provide would result in a low likelihood of a fix.

I wonder if maybe a KDE dev might be able to push this upstream? I'll do whatever I can as far as user testing goes. I'm keen to help out (obviously, I'm here!) but I think I'd do more harm than good by being the one to raise this to Qt.
Comment 5 Bug Janitor Service 2024-07-02 03:47:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Christoph Cullmann 2024-09-15 15:59:15 UTC
There seems to have be done some work for Wayland: https://bugreports.qt.io/browse/QTBUG-87303

I think the compositor must do that, will pass to KWin, they can still dispatch that to the right thing.
Comment 7 pallaswept 2024-09-15 19:59:09 UTC
Thanks for chasing that up for us Christoph!

Reading this Qt bug makes me more confident that 468794 is the same bug as this one. I hope someone could take a look. I imagine there may be quite a number of dupe/semi-dupe bugs about this.
Comment 8 Vlad Zahorodnii 2024-09-23 09:12:07 UTC
(In reply to Christoph Cullmann from comment #6)
> There seems to have be done some work for Wayland:
> https://bugreports.qt.io/browse/QTBUG-87303
> 
> I think the compositor must do that, will pass to KWin, they can still
> dispatch that to the right thing.

Yeah, the client may need to set resize constraint adjustments.