Bug 199326

Summary: System Settings should write default application changes for non-KDE apps
Product: [Applications] systemsettings Reporter: Dotan Cohen <kde-2011.08>
Component: kcm_componentchooserAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: CONFIRMED ---    
Severity: normal CC: 1i5t5.duncan, bugseforuns, devin.inspiredby, exp.wez, kde, luigi.toscano, mayazcherquoi, nate, rdieter, redhen898-online
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Unspecified   
See Also: https://bugs.kde.org/show_bug.cgi?id=397953
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: System Settings - Default Application - File Association - text / html fixes Chrome default browser status

Description Dotan Cohen 2009-07-07 19:35:39 UTC
Version:            (using KDE 4.2.90)
Installed from:    Ubuntu Packages

System Settings should write default application changes to a place for non-KDE apps to use. Currently, only KDE apps are affected by System Settings changes.

If this is a WONTFIX, then the name System Settings is misleading and should be changed. It is expected that, as the name implies, settings are system-wide (at least for the user).
Comment 1 redhen898-online 2009-07-07 19:59:01 UTC
I have a serious issue on my Debian Lenny system, running KDE 3.5.1

It might be an OOo issue. But ONLY from inside OOo, the system does not recognize Firefox as my system default browser. I have changed the path settings several different ways within the KControl, and this does not solve the issue. 
 
The KDE system/environment DOES recognize Firefox as the default browser to open web addresses and links from inside all other KDE and non-KDE programs --- e.g. Thunderbird, audio and video programs, and so on. 

But no matter what I do, clicking on links embedded in OOo writer documents ALWAYS raises the Konqueror browser, the use of which I want to LIMIT ONLY to system files and desktop windows.

This problem has existed for me since I switched to Debian Etch in 2007, and has persisted with my recent upgrade to Debian Lenny.  It's been more than a year. I have tried using KDE Control to fix this problem ---- and it does NOT WORK!!!!
Comment 2 Dotan Cohen 2009-11-30 14:26:56 UTC
*** Bug 197727 has been marked as a duplicate of this bug. ***
Comment 3 Dotan Cohen 2009-11-30 14:29:19 UTC
System Settings should write locale changes to .bash_profile as well, as mentioned in bug # 82009. I don't mark this as a dupe as this bug requests not only locale changes but default application changes as well.

Thanks.
Comment 4 Duncan 2009-12-01 02:13:28 UTC
Indeed.  Taking a hint from the way the Prince thing was handled, I've taken to referring to it something like this:

"'The application formerly known as kcontrol' (generically aka 'system settings', even tho system settings is not only way to generic to be descriptive, but it controls not system settings, but kde settings, so  kcontrol is way more accurate in any case, when I can use it to configure my boot services, /then/ it might arguably be 'system settings', until then, it's kcontrol, or 'the application formerly known as kcontrol')."

Of course, I'm forced to do something similar with "The application formerly known as ksysguard" as well, since there's all sorts of "system monitor" plasmoids, etc, non of which are actually "the application formerly known as ksysguard" plasmoids, as it doesn't appear to have one...  These generic names are useless for what names are /for/, actually identifying something.  That's a problem.  If I wanted functionality descriptions, there's a menu option for that.  There's a reason I don't have that checked.  I want application names, and I want them to usefully identify the application, not be so generic as to be almost useless.

So consider this a request to either change the name back, or to support every distribution and platform that kde runs on system settings (including Gentoo, what I run), thus making the name accurate, even if that still won't solve the generic aspect.
Comment 5 Nate Graham 2018-11-26 05:51:38 UTC
*** Bug 394835 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2018-11-26 05:54:23 UTC
Looks like we need to have it do `sudo update-alternatives --config x-www-browser` (or equivalent)
Comment 7 Luigi Toscano 2019-01-24 13:06:03 UTC
(In reply to Nate Graham from comment #6)
> Looks like we need to have it do `sudo update-alternatives --config
> x-www-browser` (or equivalent)

That's a distribution-specific setting, so I don't think it's the right solution.
Comment 8 Nate Graham 2020-01-22 15:57:41 UTC
*** Bug 372415 has been marked as a duplicate of this bug. ***
Comment 9 Johannes Kühnel 2020-05-10 17:16:25 UTC
Created attachment 128341 [details]
System Settings - Default Application - File Association - text / html fixes Chrome default browser status
Comment 10 Johannes Kühnel 2020-05-10 17:19:26 UTC
Since Bug #394835 got marked as a duplicate of this, I just discovered, that manually changing Chrome to the first position in the File Associations -> text -> html list solved the problem of Chrome not recognizing itself as the default browser (see attachment in comment #9).
Maybe setting the file association with the default browser is a possible fix for this issue?