| Summary: | Startup menu misplaced and drag and drop broken after screen configuration change | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Torsten Römer <dode> |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | bhush94, jan.pavlicek, justin.zobel, mgraesslin, notmart, plasma-bugs |
| Priority: | NOR | ||
| Version: | 5.2.1 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Misplaced startup menu after connecting external screen
Misplaced notification after connecting external screen |
||
|
Description
Torsten Römer
2015-03-23 20:31:31 UTC
Created attachment 91708 [details]
Misplaced startup menu after connecting external screen
I can only partially reproduce: if i put 2 screens of different resolution in the same position as the screenshot, with the smallest screen on the right, and (important) the two screen aligned on the bottom (the empty area of the screenshot at the top) if the smallest screen has a panel taller than the panel of the biggest screen, the popups on the bigger screen will result bottom aligned to the panel of the smallest screen, leaving a small gap. can you please look at the panel's struts? Investigation shows that the root problem is _NET_WORKAREA not being multi-screen aware. This is a problem in the protocol and rather difficult to fix unfortunately. What could be done is: * setting multi screen aware property in KWin * reading this property in KWindowSystem * provide an API in KWindowSystem which can be used by PlasmaDialog I just would like to add that the same issue occurs with notifications, I added a screenshot. If I can be of any help like testing patches please let me know! Created attachment 91828 [details]
Misplaced notification after connecting external screen
I just like to add that the issues with drag and drop are not related, since they occur also after a clean (re)start, I don't know yet if it simply is the mouse or the bluetooth connection. *** Bug 350085 has been marked as a duplicate of this bug. *** It seems to be a Qt issue, probably in the xcb platform integration: after a screen is activated, the corresponding QScreen* is there and its geometry is correct. However, availableGeometry() is a QRect(0, 0, 0x0) causing this problem. only after plamashell is restarted, the qscreen has the proper availableGeometry(). I've just tested this on plasmashell 5.20.2 and I can't replicate the issue. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks. 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |