Bug 498697 - Window titlebar context menu items cut off
Summary: Window titlebar context menu items cut off
Status: RESOLVED DUPLICATE of bug 498111
Alias: None
Product: kwin
Classification: Plasma
Component: core (other bugs)
Version First Reported In: 6.2.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-15 16:33 UTC by in+zam14owa
Modified: 2025-07-02 09:59 UTC (History)
4 users (show)

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


Attachments
Video of the issue (1.32 MB, video/x-matroska)
2025-01-15 16:33 UTC, in+zam14owa
Details
Screenshot of display configuration (271.46 KB, image/png)
2025-01-15 18:33 UTC, in+zam14owa
Details
Font configuration (163.29 KB, image/png)
2025-01-15 19:03 UTC, in+zam14owa
Details
Display config screenshots with checkmark or cross (3.21 MB, application/gzip)
2025-02-24 13:58 UTC, in+zam14owa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description in+zam14owa 2025-01-15 16:33:20 UTC
Created attachment 177380 [details]
Video of the issue

Often the menu that appears when you rightclick a window is only partially rendered. 

STEPS TO REPRODUCE
1.  Open any application
2.  Right click its titlebar

OBSERVED RESULT

This menu is rendered properly, but if you hover over an item that has a submenu (Desktops>, More Actions>), it is only rendered partially until you hover out and then back in again. See video.

This happens almost always if just logged into Plasma, and afterwards it will be fine right away. It does sometimes come back during the session though.

EXPECTED RESULT

Submenu is rendered properly.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma:  Archlinux
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1

ADDITIONAL INFORMATION

Not 6.2.5 specific, happened in previous versions as well.
Comment 1 fanzhuyifan 2025-01-15 17:27:07 UTC
Is this on x11 or wayland? What global scale are you using? Does this happen when all the global scale is set to 100%?
Comment 2 in+zam14owa 2025-01-15 18:33:43 UTC
Created attachment 177382 [details]
Screenshot of display configuration
Comment 3 in+zam14owa 2025-01-15 18:34:51 UTC
(In reply to fanzhuyifan from comment #1)
> Is this on x11 or wayland? What global scale are you using? Does this happen
> when all the global scale is set to 100%?

Wayland. Scale is 200% but also happens on 100%.

The issue can be 100% reproduced when changing something in the display configuration. It will render incorrectly once and then is fine after that. I have 3 monitors connected, see screenshot.
Comment 4 fanzhuyifan 2025-01-15 18:41:59 UTC
(In reply to krims0n32 from comment #3)
> (In reply to fanzhuyifan from comment #1)
> > Is this on x11 or wayland? What global scale are you using? Does this happen
> > when all the global scale is set to 100%?
> 
> Wayland. Scale is 200% but also happens on 100%.
> 
> The issue can be 100% reproduced when changing something in the display
> configuration. It will render incorrectly once and then is fine after that.
> I have 3 monitors connected, see screenshot.

Thanks for your information! Unfortunately I cannot seem to reproduce. Here are some more questions:

- What style are you using? Does this happen with the default breeze/oxygen styles?
- What font size are you using?
- Could you be more precise about 1 example display configuration change that causes the issue? For those of us without 3 monitors, could you reproduce when there are only 2 displays, or only 1?
- When you trigger the bug, do you see anything in `journalctl -b --since -2m` ?
Comment 5 in+zam14owa 2025-01-15 19:03:17 UTC
Created attachment 177383 [details]
Font configuration
Comment 6 in+zam14owa 2025-01-15 19:06:45 UTC
(In reply to fanzhuyifan from comment #4)
> (In reply to krims0n32 from comment #3)
> > (In reply to fanzhuyifan from comment #1)
> > > Is this on x11 or wayland? What global scale are you using? Does this happen
> > > when all the global scale is set to 100%?
> > 
> > Wayland. Scale is 200% but also happens on 100%.
> > 
> > The issue can be 100% reproduced when changing something in the display
> > configuration. It will render incorrectly once and then is fine after that.
> > I have 3 monitors connected, see screenshot.
> 
> Thanks for your information! Unfortunately I cannot seem to reproduce. Here
> are some more questions:
> 
> - What style are you using? Does this happen with the default breeze/oxygen
> styles?

Yes,  I'm using Breeze Dark.

> - What font size are you using?

See screenshot.

> - Could you be more precise about 1 example display configuration change
> that causes the issue? For those of us without 3 monitors, could you
> reproduce when there are only 2 displays, or only 1?

So it seems to only happen with 3 monitors connected, with two or one I cannot reproduce it. It happens 100% of the time when changing the scale for all screens from 100% to 200% or vice-versa, but only with 3 monitors connected.

> - When you trigger the bug, do you see anything in `journalctl -b --since
> -2m` ?

I do not see anything specific when the issue occurs in the logs.
Comment 7 TraceyC 2025-01-15 19:58:32 UTC
I was seeing this on Plasma 6.2.5 with a laptop connected to two external monitors. It is always seen after the first login after reboot.
I think I was also able to reproduce if I disabled and then re-enabled the second external monitor.

- What style are you using? Does this happen with the default breeze/oxygen styles?
     Breeze Dark
- What font size are you using?
     10 pt
- Could you be more precise about 1 example display configuration change that causes the issue? For those of us without 3 monitors, could you reproduce when there are only 2 displays, or only 1?
     I also don't see this on this or another laptop with only the internal or internal + 1 external display

I am not able to reproduce this right now. My system now has Frameworks 6.10.0 if that makes a difference
Comment 8 TraceyC 2025-01-15 21:17:54 UTC
I was just testing another bug and saw this again
I had rebooted, switched to X11, logged out, logged into Wayland, and changed the built-in display from 100% to 150%
Comment 9 TraceyC 2025-01-15 21:18:02 UTC
.
Comment 10 David Redondo 2025-01-16 09:19:25 UTC
Maybe related to 498446?
Comment 11 Vlad Zahorodnii 2025-01-16 11:09:30 UTC
(In reply to David Redondo from comment #10)
> Maybe related to 498446?

it could be
Comment 12 in+zam14owa 2025-02-22 09:44:47 UTC
Still happening in 6.3.1. I understand a three monitor setup is uncommon .. Can I do anything to help debug this? It is pretty annoying.
Comment 13 Vlad Zahorodnii 2025-02-23 16:45:30 UTC
(In reply to krims0n32 from comment #12)
> Still happening in 6.3.1. I understand a three monitor setup is uncommon ..
> Can I do anything to help debug this? It is pretty annoying.

If you can, please try to find what combination of settings (font, widget style, output scale factor, etc) likely causes this issue. Also, please check if it happens in a new user account. We need some way to reproduce the issue.
Comment 14 in+zam14owa 2025-02-24 13:56:09 UTC
Okay I spent a couple of hours debugging and found some interesting stuff. 

Firstly, I could not reproduce the issue 100% of the time anymore when changing some settings in display configuration (scaling, refresh rate, etc.). So something changed there after Plasma >= 6.3. I can however reproduce the issue 100% of the time after changing the font in Plasma (doesn't matter which font I use). So something changed there.

Anyway, after some digging I found the issue is caused not by how many monitors are connected but *how* they are arranged in Plasma. I am able to reproduce the issue 100% of the time on a *dual monitor* setup as well so that should make debugging this a lot easier. It seems to happen when the monitor that wayland or the system sees as "primary" (DP-1 in my case) does not come first in the layout. E.g. if I put that monitor on the far left in the Plasma display configuration, the issue disappears. If I put it on the right, it comes back. If I put it on top, no issue. If I put it on the bottom, the issue is there. Toggling "Primary" in the display configuration does not have any effect.

I made a bunch of screenshots of the display configuration and marked them with a green checkmark if the issue does not occur, and a red cross when the issue does occur. The monitor that ends with serial # 3101 is my "primary" monitor, connected to DP-1.

Stuff I ruled out:
- created a new user, issue occurs there as well
- it is not scaling related, 170%, 100%, 200% all show the issue
- not theme or widget related, tried various styles and window decorations

This should make it a lot easier to debug I think. Let me know if I need to do further testing :)
Comment 15 in+zam14owa 2025-02-24 13:58:46 UTC
Created attachment 178808 [details]
Display config screenshots with checkmark or cross
Comment 16 in+zam14owa 2025-07-02 09:23:34 UTC
So a couple of months later I decided to give this another attempt and I cannot reproduce this issue anymore.

KDE Plasma: 6.4.1
KDE Frameworks: 6.15.0
Qt version: 6.9.1

Very pleased with this :)
Comment 17 Vlad Zahorodnii 2025-07-02 09:59:56 UTC
Yeah, it was fixed in 6.4.0

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