I apologize if this isn't the right place to put this. STEPS TO REPRODUCE 1. Load multiple, different apps on desktop (e.g. Chrome, Firefox, PuTTY, Remmina, etc) 2. Left-click on one of the background apps to try and bring it to foreground OBSERVED RESULT Under most circumstances, I am not able to use the mouse to take the background app/window and bring it to be the foreground app/window. Also not able to bring it to foreground by clicking on the top, bottom, or side border. Just my observation, but the only time I seem to be able to make it work is if there is some type of written text in the area where I clicked. EXPECTED RESULT This functionality has worked with Windows since I can remember, and I can certainly recreate it with Windows 10 and 11. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE 6 (also able to recreate in previous versions of KDE 5) (available in About System) KDE Plasma Version: 6.0 KDE Frameworks Version: can provide more specifics if needed Qt Version: can provide more specifics if needed ADDITIONAL INFORMATION I submitted this using my work PC running Windows 11 - if more specific details are needed, just let me know and I'll provide it on my home laptop.
Does it work as expected in a new clean user account? Does this happen on X11, Wayland, or both?
Created attachment 166991 [details] attachment-2220259-0.html Hello Nate, I've been using Wayland for quite a while now. Once I'm finished with something else I'll test with a clean use account. Thanks - Dean On Mon, Mar 11, 2024 at 3:09 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=483229 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Product|Active Window Control |kwin > Resolution|--- |WAITINGFORINFO > Status|REPORTED |NEEDSINFO > Component|General |general > Assignee|zrenfire@gmail.com |kwin-bugs-null@kde.org > Version|unspecified |6.0.0 > CC| |nate@kde.org > > --- Comment #1 from Nate Graham <nate@kde.org> --- > Does it work as expected in a new clean user account? > > Does this happen on X11, Wayland, or both? > > -- > You are receiving this mail because: > You reported the bug.
Created attachment 167162 [details] attachment-3084163-0.html Sorry Nate - haven't forgot about you. I did play with the new user, and I couldn't seem to recreate it. That being said, I have only gotten to test it for about 5-10 minutes. I hope to dig more into it tonight or possibly this weekend. Dean On Mon, Mar 11, 2024 at 5:26 PM Dean Hoover <kb7qdi@gmail.com> wrote: > Hello Nate, > > I've been using Wayland for quite a while now. > > Once I'm finished with something else I'll test with a clean use account. > > Thanks - Dean > > On Mon, Mar 11, 2024 at 3:09 PM Nate Graham <bugzilla_noreply@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=483229 >> >> Nate Graham <nate@kde.org> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> Product|Active Window Control |kwin >> Resolution|--- |WAITINGFORINFO >> Status|REPORTED |NEEDSINFO >> Component|General |general >> Assignee|zrenfire@gmail.com |kwin-bugs-null@kde.org >> Version|unspecified |6.0.0 >> CC| |nate@kde.org >> >> --- Comment #1 from Nate Graham <nate@kde.org> --- >> Does it work as expected in a new clean user account? >> >> Does this happen on X11, Wayland, or both? >> >> -- >> You are receiving this mail because: >> You reported the bug. > >
No worries. If it works in a clean user account, we know it's caused by come configuration in your original user account somehow.
Hello Nate, I was definitely able to recreate it, but playing around a bit I think this might have something to do with Google Chrome. I can't recreate it if I'm using Firefox or even UnGoogled Chromium. I attached two Spectacle videos to kind of show you what I mean (if you don't get them let me know and I'll attach them to my Nextcloud or Google Drive) For some reason, Chrome extends beyond that actual window size. Not sure if this is KDE or Chrome - let me know what you think. Dean On Thu, Mar 14, 2024 at 12:31 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=483229 > > --- Comment #4 from Nate Graham <nate@kde.org> --- > No worries. If it works in a clean user account, we know it's caused by > come > configuration in your original user account somehow. > > -- > You are receiving this mail because: > You reported the bug.
Created attachment 167325 [details] attachment-3754789-0.html Let's try it over Google Drive. Also - I was able to recreate it with UnGoogled-Chromium - just much smaller area than with Google Chrome. Google-Chrome-switching-screens.webm <https://drive.google.com/file/d/1zCWYjroq-i2VWBhdVdDM950YyeJnnkUa/view?usp=drive_web> Firefox-switching-screens.webm <https://drive.google.com/file/d/1L1L0u1y2ZJhyTA_S8odceTUJ2vUXWeuw/view?usp=drive_web> On Sat, Mar 16, 2024 at 7:52 AM Dean Hoover <kb7qdi@gmail.com> wrote: > Hello Nate, > > I was definitely able to recreate it, but playing around a bit I think > this might have something to do with Google Chrome. I can't recreate it if > I'm using Firefox or even UnGoogled Chromium. > > I attached two Spectacle videos to kind of show you what I mean (if you > don't get them let me know and I'll attach them to my Nextcloud or Google > Drive) For some reason, Chrome extends beyond that actual window size. > > Not sure if this is KDE or Chrome - let me know what you think. > > Dean > > On Thu, Mar 14, 2024 at 12:31 PM Nate Graham <bugzilla_noreply@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=483229 >> >> --- Comment #4 from Nate Graham <nate@kde.org> --- >> No worries. If it works in a clean user account, we know it's caused by >> come >> configuration in your original user account somehow. >> >> -- >> You are receiving this mail because: >> You reported the bug. > >
Thanks. From those screen recordings, it looks like the problem only happens while Chrome/Chromium is running, and when it happens, it seemingly randomly affects all kinds of apps and not just Chrome/Chromium itself, right?
Created attachment 167474 [details] attachment-371693-0.html The only apps that I've been able to recreate this is Google Chrome and UnGoogled Chromium. I don't use any other Chromium-based browser, and it doesn't seem to happen with Firefox. It's almost as if the browser believes that the window is larger than it actually is. For example, the browser window might be 800x1000 but it tells the DE that it's 800x1050 so that if the mouse clicks between the 1000 and 1050 the browser window becomes the foreground instead of the actual app that they are trying to get to. Unless you think this still might be a KDE issue, I think you can close this ticket. I also submitted feedback to Google but I honestly don't think they will say or do anything about it. And now that I have a better grasp of where and when it happens, I can adjust the way I do things to mitigate the issue. Appreciate your time Nate. I've been a UNIX and Linux server user and administrator for almost 40 years, but every DE I've tried never worked well enough for me. KDE has changed my mind, and if it wasn't for a couple Windows-only apps (Cisco ASDM, Teams' ability to take control of PC, etc) I'd be 100% Linux and KDE for work and home. Keep up the great work! Dean On Mon, Mar 18, 2024 at 5:00 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=483229 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Summary|Unable to click background |Sometimes unable to bring > |app/window to foreground |background apps to the > |using mouse |front while > Chrome/Chromium > | |is running > > --- Comment #7 from Nate Graham <nate@kde.org> --- > Thanks. From those screen recordings, it looks like the problem only > happens > while Chrome/Chromium is running, and when it happens, it seemingly > randomly > affects all kinds of apps and not just Chrome/Chromium itself, right? > > -- > You are receiving this mail because: > You reported the bug.
(In reply to Dean Hoover from comment #8) > Created attachment 167474 [details] > attachment-371693-0.html > > The only apps that I've been able to recreate this is Google Chrome and > UnGoogled Chromium. I don't use any other Chromium-based browser, and it > doesn't seem to happen with Firefox. > > It's almost as if the browser believes that the window is larger than it > actually is. For example, the browser window might be 800x1000 but it > tells the DE that it's 800x1050 so that if the mouse clicks between the > 1000 and 1050 the browser window becomes the foreground instead of the > actual app that they are trying to get to. Hmm... by any chance are you using a scale factor below 100%, and is Chrome/Chromium running in native Wayland mode? If so this sounds very much like Bug 477676. > Appreciate your time Nate. I've been a UNIX and Linux server user and > administrator for almost 40 years, but every DE I've tried never worked > well enough for me. KDE has changed my mind, and if it wasn't for a couple > Windows-only apps (Cisco ASDM, Teams' ability to take control of PC, etc) > I'd be 100% Linux and KDE for work and home. Thanks for the kind words! We try hard to make it a pleasant and productive environment. :)
Created attachment 168029 [details] attachment-176288-0.html > by any chance are you using a scale factor below 100%, and is Chrome/Chromium running in native Wayland mode? I am running native Wayland on the laptop, but the scale factor is set to 100% (it was originally set to 125% by the OS when I first installed it but I changed it soon after). I read the bug you listed. Although my situation is with the scale factor at 100% I will try to sneak some time to see if lowering/raising the factor makes a dent. Dean On Mon, Apr 1, 2024 at 12:22 PM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=483229 > > --- Comment #9 from Nate Graham <nate@kde.org> --- > (In reply to Dean Hoover from comment #8) > > Created attachment 167474 [details] > > attachment-371693-0.html > > > > The only apps that I've been able to recreate this is Google Chrome and > > UnGoogled Chromium. I don't use any other Chromium-based browser, and it > > doesn't seem to happen with Firefox. > > > > It's almost as if the browser believes that the window is larger than it > > actually is. For example, the browser window might be 800x1000 but it > > tells the DE that it's 800x1050 so that if the mouse clicks between the > > 1000 and 1050 the browser window becomes the foreground instead of the > > actual app that they are trying to get to. > Hmm... by any chance are you using a scale factor below 100%, and is > Chrome/Chromium running in native Wayland mode? If so this sounds very much > like Bug 477676. > > > Appreciate your time Nate. I've been a UNIX and Linux server user and > > administrator for almost 40 years, but every DE I've tried never worked > > well enough for me. KDE has changed my mind, and if it wasn't for a > couple > > Windows-only apps (Cisco ASDM, Teams' ability to take control of PC, etc) > > I'd be 100% Linux and KDE for work and home. > Thanks for the kind words! We try hard to make it a pleasant and productive > environment. :) > > -- > You are receiving this mail because: > You reported the bug.
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!