You are not logged in.

#1 2024-03-12 15:41:59

Felixoid
Member
Registered: 2012-05-23
Posts: 33

Broken Firefox and some other behaviors after updating to Plasma 6

Hello.

After upgrading to plasma 6.0.1-1, Firefox (and so far only it) remains inactive when I open any link.

For example, clicking the link in any application (Slack, terminal) or opening it as a command highlights the icon in the Icons Task manager. But it does not activate the window itself.

I've checked it with a new profile, and it behaves the same way.

I am completely lost. There are no such issues anywhere in the wild so far.

update 1: there are other issues too. For example, slack's notifications don't activate the window. But the telegram's notifications work. And chromium works as well, it is activated by the links

Last edited by Felixoid (2024-03-12 16:25:42)

Offline

#2 2024-03-12 16:50:41

rmDuha
Member
Registered: 2014-01-23
Posts: 23

Re: Broken Firefox and some other behaviors after updating to Plasma 6

Are you using wayland now and before X11?

Offline

#3 2024-03-12 17:14:30

Felixoid
Member
Registered: 2012-05-23
Posts: 33

Re: Broken Firefox and some other behaviors after updating to Plasma 6

hmm, that's right. The default protocol has changed from X11

Offline

#4 2024-03-12 17:55:11

rmDuha
Member
Registered: 2014-01-23
Posts: 23

Re: Broken Firefox and some other behaviors after updating to Plasma 6

Not super sure how all this works, but looking at https://bugs.kde.org/show_bug.cgi?id=461421 it seems the application needs to support xdg-activation.

I can reproduce with some applications, like element + firefox, while it works for others like neochat+firefox.

Maybe slack wayland fixes the issue.

Last edited by rmDuha (2024-03-12 18:40:18)

Offline

#5 2024-03-12 18:49:58

Felixoid
Member
Registered: 2012-05-23
Posts: 33

Re: Broken Firefox and some other behaviors after updating to Plasma 6

It doesn't even work when I use

xdg-open http://localhost

Offline

Board footer

Powered by FluxBB