- discover isn't running - click appstream uri in browser - discover starts - no focus ALSO: no needs-attention highlight in the taskbar the no-focus bit might well be focus stealing prevention kicking in, in which case there must be a needs-attention highlight (ideally of course discover would come to front) when doing the same with discover already open it still won't come to foreground, but have have the needs-attention highlight ¯\_(ツ)_/¯
I can reproduce, on Wayland. On X11 it does get the attention highlight but it doesn't raise. QWindow::raise() is being called, I'm not sure what else should happen. Will investigate.
I just realised you mean when the application starts. Could it be that your KWin is broken? it seems to work for me...
Created attachment 111365 [details] video of 5.12.0 in a vm tried in a new VM. it's actually somewhat more complicated. what I am seeing is only happening iff the previous discover was closed while it was minimized. i.e. - start discover - minimize - right click on task bar - close - xdg-run appstream uri this way it is 100% reproducible. additionally the window never gets raised if the window was already open. the attached video should show both behaviors
Can reproduce with `xdg-open [appstream URI]` Cannot reproduce when opening an appstream link from Firefox.
Can reproduce steps in Comment 3 on X in terminal, Chromium and Firefox - but cannot reproduce on Wayland - Discover always comes to front Plasma: 5.12.4 Apps: 17.12.3 Frameworks: 5.45.0 Qt: 5.10.1 Kernel: 4.14.34-1-MANJARO OS: Netrunner Rolling Video: Intel 4400 Driver: xf86-video-intel 1:2.99.917+823+gd9bf46e4-1 Screen: 1600x900 wayland-protocols 1.13-1 wayland 1.14.0-1
Assigning to kwin, I just checked and raise is definitely being called, I have no idea why it happens. For easier debugging, just try running discover, put it behind another window and call "plasma-discover appstream://org.kde.kolf.desktop".
FWIW, this won't work on wayland because wayland doesn't understand ::raise(). I'm not sure why it worked.
On wayland we (currently) focus new toplevels. If discover isn't running, it'll take focus. If it is, nothing will happen (for now at least)
This is not a bug in KWin. It's rather expected behavior of focus (and raising) protection. You need to provide a KStartupInfo to discover (by using for example KRun), so that KWin can know that it's legit to pass focus to the window. If you launch from Krunner it works after all. Passing back to discover.
So firefox should use KRun? :/ That's how we have things never work.
This was fixed recently and is working now!
I'm not sure if this is the same issue, but Discover starts minimized when I click on "Install/View in desktop store" buttons in the following link https://snapcraft.io/telegram-desktop Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Graphics Platform: X11
That's extremely odd. Minimized? I wasn't aware that that was even possible... Either way, it would be a different issue. Does it only happen for snap links, or any appstream links? What about if you open the link manually with `plasma-discover --application appstream://orgkde.discover.snap`?
@Patrick. Definitely not the same issue. Please reopen a new bug if you can reproduce. Please check the value of Visibility within [Window] of your ~/.config/discoverrc.
Weirdy I no longer can reproduce the bug. I will open a new bug report if it occurs again. Thanks Nate and Aleix.