Bug 431479

Summary:	The default browser is not set from places other than the system setting menu.
Product:	[Applications] systemsettings	Reporter:	Artifeks <artifeks92>
Component:	kcm_componentchooser	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	fella, meven29, nate, nicolas.fella
Priority:	HI
Version First Reported In:	5.20.4
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Artifeks 2021-01-12 09:04:45 UTC

SUMMARY
After set the default browser from the browser itself, when you call the default browser, is called the previously set. But the menu displays which one we wanted to set. Also, if you change the default browser in this menu and click apply, then everything works correctly.

STEPS TO REPRODUCE
1. Install vivaldi, chrome, ets
2. Open browser and set "default browser" from browser
3. Open links from any

OBSERVED RESULT
The link will open in the previous browser

EXPECTED RESULT
The link will open in the new browser

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Manjaro KDE
(available in About System)
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Comment 1 Nate Graham 2021-01-13 01:41:18 UTC

What does System Settings > Applications > Default Applications say? Does it match the browser you want to be the default one?

Comment 2 Artifeks 2021-01-14 10:05:58 UTC

If you change the default browser from within the browser, then the browser does not match in the settings menu.At the same time, the browser itself thinks that it was set correctly, if you set the setting in each browser, then everyone will consider themselves set by default

Comment 3 Nate Graham 2021-01-14 16:57:44 UTC

Can confirm. Setting the default browser from within any web browser does not update the setting in the KCM. They don't seem to be looking at the same config files.

Comment 4 Méven Car 2021-02-02 11:58:00 UTC

Part of the issue comes from requiring a recent xdg-utils (https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/29) but xdg-utils is not released often to say the least, last version is 2 years old...

Comment 5 Nate Graham 2021-02-02 16:09:13 UTC

So is this an upstream issue fixed by https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/29 then?

Comment 6 Méven Car 2021-02-02 16:40:12 UTC

(In reply to Nate Graham from comment #5)
> So is this an upstream issue fixed by
> https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/29 then?

Yes, but without a release can we say "fixed upstream ?"

Comment 7 Nate Graham 2021-02-02 16:46:53 UTC

We can. And we need to focus our efforts upstream, on getting a new release! :p Keeping this bug report open won't accomplish that.