Summary: | Dialog boxes in wrong location and wrong size | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | CCG <geneegossett2635599> |
Component: | rules | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | REOPENED --- | ||
Severity: | normal | CC: | isma.af, kde, nate, uhhadd |
Priority: | NOR | ||
Version First Reported In: | 6.1.5 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
CCG
2024-09-25 10:46:51 UTC
The screenshots show that you have a heavily customized Plasma setup, and I suspect one of those customizations is causing this — for example, window rules. Can you create a new clean user account and see if the problem happens there? If it does not, this indicates there's a strong change one of the customizations is to blame. In that case, please try to figure out which one it is. Pretty sure it's theme related and not customization related. I suspect this cause I had Garuda, RebornOs, and CachyOS installed and in Cachy this did not happen. The only difference is that in Reborn and Garuda I installed Utterly-Sweet Global Themen then switched to Vivid -Magna-Dark and I had the issue before switching to Magna. In Cachy I only install Vivid-Magna-Dark and never got the issue. As a test I just installed another copy of Garuda and set it up like I normally do, but this time I left the default theme and only changed the icons and cursors and it's behaving as it should so far. The only thing I am running into and I've seen before is trying to add my two desktop widgets. I try to drag them to the desktop and I get red stop symbol and the screen blinks off for a second and then comes back. When I've seen it in the past for some reason it just corrected itself. OK I finished running my test and it looks to be in part to resizing various components. All was looking good til I stretched system settings a little and went into Configure Special Application Settings and set it to use the size I had stretched System Settings to. Once I did that the dialog boxes became like you see in the screenshots I posted. I went back in removed the custom size and the dialog boxes went back to normal. Seems odd that that would cause the issue, but I have to go by what I observed. I had a feeling this was caused by a broken window rule. Solution: fix your window rule. :) I have slightly stretched both System Settings and Desktop Folder Settings and set them to their particular Virtual Desktop, set their custom size, and their custom position from Plasma 5.0 and even in Plasma 6.0 and this was not happening. This is something new since 6.1. That tells me something is linked that wasn't before. That needs a looking into. Actually NOT resolved and is a bug. So you're saying you had a window rule that behaved in a certain way, and then after upgrading to Plasma 6.1, it behaved in a different way? Is that right? Yes. Maybe it's better if I do a video to show what is exactly happening. That way we both can avoid misunderstanding due to language differences. Give me til this time tomorrow to get one made for you. Thanks OK just set size, virtual desktop, and position and it did what you see in my above screenshots. If remove the window rules the boxes go back to being where they are suppose to be. Applications menu upper left corner, devices popup back in the upper right corner, and the drop down for shutdown or switch goes back to being only twice as wide as the lock screen text. Also if I add the size, position, virtual desktop if I plug in a flash drive the devices dialog box only opens on the desktop that I have the system settings panel assigned to as well as the copy / move dialog instead of them being on all desktops like they normally are. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME. This is marked resolved. Something about workframe? I see nothing explaining what was causing the issue, nor what steps were involved to fix the issue. I'd like to know that I can once again be able to assign say system settings to only my main virtual desktop and not have the copy / move dialog only available on that virtual desktop because of assigning system settings to open only on that desktop, or if a assign a custom size to system settings / desktop & wallpaper application launcher won't be made larger and or moved to the center of the screen along with other system dialog boxes. Thanks The problem remains the same: you've got a broken window rule that's too broad in scope, or not applying the right properties. On a feature that with without issue until plasma 6 or 6.1, and happens in at least Garuda, Arch, Reborn, CachyOS, BigLinux? You may be right but it's still something under the hood causing it. See the new screenshot with explanation below it. https://i.imgur.com/rtKkaXe.png Now if I actually applied those the dialog boxes would go haywire. All I'm getting at is the settings are nothing different than I have always done. I did a fresh install of RebornOS and ran a couple of test. I narrowed the issue down to setting Desktop & Wallpaper to a custom size specific desktop, and specific position. The above described behavior seen to be cause only by this Plasma component being set this way. I did a fresh install of RebornOS and ran a couple of test. I narrowed the issue down to rightclicking the desktop selecting Desktop & Wallpaper and setting it to a custom size, a specific desktop, and a specific position under More, Configure Special Application Settings. The above described behavior seems to be caused only by this Plasma component being set this way. Sorry for the repost but I noticed on the forum that the post above this one needed to be edited and there is no editing here. I hope that gives you a better understanding of what is going on. |