Bug 380133

Summary: Cannot see/change default browser settings
Product: [Applications] systemsettings Reporter: Anguo <kde_bugs>
Component: kcm_componentchooserAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: ckakman, nate
Priority: NOR    
Version: 5.8.6   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Anguo 2017-05-24 03:41:58 UTC 
In KDE systemsettings > Personalization > Applications > Default applications > Web browser,
there are two settings:
A) "in an application based on the contents of the URL".
B) "in the following browser".

There are two problems with the interface:
1- if A) is selected, then the name of the default browser is not visible.

2- It is not possible to change the default browser and keep A) selected.
To do so, the workaround is to select B), type in the browser name, save, then select A) again, save again. When coming back later to the same screen, the first problem occurs again.

http://linux.overshoot.tv/wiki/default_browser_kde
Comment 1 Anguo 2017-05-24 03:49:59 UTC 
Logically, the settings should be split into two different settings:

- One setting to select the default browser.
- One setting to select default action, with A) as above and B) reading: "in the default browser".
Comment 2 Anguo 2017-05-24 04:56:08 UTC 
Where are the relevant settings saved?
I checked ~/.config/systemsettingsrc  but it does not appear to be there.
Comment 3 Kayra Akman 2018-05-02 10:14:14 UTC 
While dealing with Bug 393727 I have noticed the issue described in this bug report is valid for Plasma 5.12 on Kubuntu 18.04.

I have Firefox and Falkon installed on my system. When I choose Falkon "in the following application" drop-down of Default Applications > Web Browser, links open in Falkon as expected. If I choose the "in an application based on the contents of the URL" option, links open in Firefox.
Comment 4 Nate Graham 2018-11-26 06:02:10 UTC 

*** This bug has been marked as a duplicate of bug 100016 ***