Version: unspecified (using Devel) OS: Linux In 4.7 the windows keep the "demands attention" state when opened on a different workspace (e.g. via a shortcut and a workspace assigned via window rules), even after activating them. Reproducible: Always Steps to Reproduce: 1) Add a window rule to open an application (e.g. firefox) on a given workspace 2) Switch to a different workspace 3) Open the application 4) The window in the taskbar has the "demands attention" design (flashes grey on Air theme) 5) Activate this application (click on the taskbar entry) Actual Results: 6) The application entry in the taskbar still has the demands attention design (grey) This is a regression since 4.6 Expected Results: The application entry in the taskbar has the "active" design, as it was the case up to 4.6.3 according to xprop, the demands attention flag is not set on the window. KDE is 4.7 from svn/git (day after tag), Qt is 4.7, Theme is Air for netbooks
*** Bug 283230 has been marked as a duplicate of this bug. ***
Victor, can you add the steps to reproduce with a single desktop/workspace setup?
You can find them in the Bug 283230: Steps to Reproduce: Launch an app, for example Krusader. While the application loads, start clicking on some already opened window, until the Krusader loads. Actual Results: Because you where clicking on on another window, Krusader opened in the background and demanded attention when it was ready - its entry in the taskbar flashed 3 time. But if then switch to that window, the highlight doesn't go away. Expected Results: After you switch to the window that demanded attention - remove the highlight on its entry in the taskbar.
bug 275835 may be related to the current one.
Can confirm with 4.7.2
*** This bug has been confirmed by popular vote. ***
Still present in 4.7.4
On my KDE 4.7.4, I mostly have the "demands attention" bug when I launch Amarok, which might be due to the fact that it needs some time to load and I often start more programs during that time. Maybe the current discussion about cursor movements in Bug 275469 is also relevant here.
Hello, I am the bugreporter of an identical bugreport. Alexander Kiselyov told me about other bugreports identical as mine, so I create this post to link all of them so someone of the admins can merge them. https://bugs.kde.org/show_bug.cgi?id=286948 https://bugs.kde.org/show_bug.cgi?id=275835 https://bugs.kde.org/show_bug.cgi?id=274020
*** This bug has been marked as a duplicate of bug 275835 ***