| Summary: | krunner sometimes gets positioned by KWin as if it were a normal window | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | thecaptain |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | alexander.lohnau, natalie_clarius, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.1.3 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
thecaptain
2024-08-04 03:35:07 UTC
Can you change your window-placement to "in top-left corner" and see if that changes how the issue manifests such that sometimes KRunner appears in the top-left corner rather than in random locations? If that's what happens, then the issue here is that under unknown circumstances, KRunner gets placed by the window placement mode rather than appearing in the expected location. (In reply to Nate Graham from comment #1) > Can you change your window-placement to "in top-left corner" and see if that > changes how the issue manifests such that sometimes KRunner appears in the > top-left corner rather than in random locations? > > If that's what happens, then the issue here is that under unknown > circumstances, KRunner gets placed by the window placement mode rather than > appearing in the expected location. Sure, testing now. I'll report back the next time it triggers, or in two days, whichever comes first. Thank you for the reply :) (In reply to Nate Graham from comment #1) > Can you change your window-placement to "in top-left corner" and see if that > changes how the issue manifests such that sometimes KRunner appears in the > top-left corner rather than in random locations? > > If that's what happens, then the issue here is that under unknown > circumstances, KRunner gets placed by the window placement mode rather than > appearing in the expected location. Confirmed that setting "Top left corner" causes krunner to start rendering in the top left corner sometimes. The semi-random placement before was due to it being set to "Minimal overlapping" krunner is also failing to launch on a regular basis. The cause is unknown besides these two errors that are logged each time. This may or may not be related, but both issues started occurring during the same release. ``` krunner qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x640b7b849d30 user@1000.service gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed ``` Ok, so we've figured out that the problem here is that KRunner sometimes gets positioned by KWin's normal window positioning code when it shouldn't. Is there any chance you have any window rules that could account for this? Can you reproduce the issue in a new clean user account with no customizations other than changing the window positioning to "in top-left corner"? The eglSwapBuffers error is something else; see Bug 480800. 🐛🧹 ⚠️ 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! (In reply to Nate Graham from comment #4) > Ok, so we've figured out that the problem here is that KRunner sometimes > gets positioned by KWin's normal window positioning code when it shouldn't. > > Is there any chance you have any window rules that could account for this? > > Can you reproduce the issue in a new clean user account with no > customizations other than changing the window positioning to "in top-left > corner"? > > The eglSwapBuffers error is something else; see Bug 480800. Sorry, I don't know. I don't really have the time to reset my system, or try running it in VM for a while :/ I'm just trying to pitch in a bit and provide a decent bug report now and then. I have at least 50 bugs in my notes for various pieces of open source software, and I hardly get the time to report them, as it takes me a while to get the info together. I have a few other KDE bugs that I haven't filed yet because of the time involved as well :/ Thank you for all of the hard work you do on this stuff though, been loving KDE You don't have to reset your system. Just create a new user account, log into it, change the window positioning to "in top left corner" and open KRunner a bunch of times. 🐛🧹 ⚠️ 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. |