SUMMARY Since the 6.1.3 update, I've been having issues with krunner sometimes deciding to display in random-ish locations on the screen. Usually in the same general vicinity on subsequent activations once I've seen it display in the wrong spot once, but always a little bit different, and will later start displaying in totally different areas. This is in a wayland session. Not sure if it's related, but I have the window manager set to do random window placement. I'm going to set it to center placement and see if the problem persists. (I tried this before, when krunner was refusing to launch frequently after the 6.1.3 release, but it didn't resolve those issues.. it only just occurred to me to try it again.) STEPS TO REPRODUCE 1. ??? Not sure 2. Activate krunner 3. It displays in the wrong location OBSERVED RESULT krunner is in the wrong location EXPECTED RESULT krunner displays at the top of the screen in the center where my main toolbar is located SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Unstable (so, basically arch), 6.9.12-1-MANJARO (64-bit) KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Latest nvidia 555 driver installed, running two 4k OLED screens via an RTX 3090 (the machine has two RTX 3090s installed, with an nvlink bridge) Intel i9-13900K Wayland session, with as many wayland-ey things enabled as possible Both displays are attached via HDMI 2.1 cables, with VRR disabled, 4k at 2.0 scaling factor, HDR enabled, refresh rate set to 120Hz, and VRR/G-Sync disabled on the screen's built in settings as well.
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 30 days. Closing as RESOLVED WORKSFORME.