Bug 354688

Summary:	Can't remove file File Association in System Settings
Product:	[Applications] systemsettings	Reporter:	Valdas <zmogas>
Component:	kcm_filetypes	Assignee:	David Faure <faure>
Status:	REPORTED ---
Severity:	normal	CC:	bhush94, bugseforuns, johannes, mathieu.tarral, piedro.kulman, plasma-bugs, samrog131, storm.anthro, w.pelser
Priority:	NOR
Version:	5.4.2
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Valdas 2015-11-01 13:17:43 UTC

When I press on a "*.asc" file then it opens in Kate. 

I want to associate that file extension with different application. So first I tried to remove it from current association:
- in System Setting -> Applications -> File Associations I searched for "asc" and I got it in "text/plain";
- then I removed "*.asc" from "File Patterns" field -> "*.asc" was gone;
- then I click on "Apply" and close System Settings;
- now tried to verify if file association is really gone -> opened System Settings and searched  for "asc" in File Associations -> it re-appeared in "text/plain".

Also I tried to simply associate that extension with different application through Krusader "Open with.." and "Always open with this application", but then (till next login) clicking on that file opens nor Kate nor newly associated application.

Reproducible: Always


Actual Results:  
Remove of File Association in System Settings is not permanent.

Expected Results:  
Setting should apply permanently.

Comment 1 Johannes Studt 2015-11-03 20:47:38 UTC

+1 here.

Dolphin 15.08.2
KF 5.15
Qt 5.5.1

1. right click on a *.pdf file, select "Open with..." -> "More..."
2. Choose "Libreoffice Writer", check "Remember this association" -> OK
3. Apply the changes

From now on *.pdf opens with Libreoffice Writer. Trying to change this fails:

1. right click on a *.pdf, select "Properties"
2. click "File type settings"
3. Move the "Libreoffice Writer" entry down, or try to delete it
4. Apply the changes

The Libreoffice Writer entry re-appears, or switches back to top position.

Comment 2 Storm Engineer 2016-03-20 05:20:08 UTC

I'm plagued by this bug for a few weeks now (at least) on Arch Linux and KDE 5 - JPG files for whatever reason got associated with Krita and this cannot be changed or removed.

Comment 3 Rog131 2016-03-20 09:44:42 UTC

Do you have the $XDG_CONFIG_HOME/mimeapps.list ?

A possible dublicate of the  Bug 354179 - File associations cannot be changed if already defined in $XDG_CONFIG_HOME/mimeapps.list : https://bugs.kde.org/show_bug.cgi?id=354179

Comment 4 piedro 2016-10-24 20:37:08 UTC

I do still have this problem in the latest ARch /KDE with all updates. 
Drives me nuts... 

thx, p.

Comment 5 Mathieu Tarral 2018-11-12 05:16:04 UTC

Hi, 2 years later and I can see a file assocition bug too.

When I tried to set the pdf type to Okular and click "Apply", It updates the changes, then I close system settings, open it again and search for the pdf type, Okular is in second position :/

Can you guys look into it ?

Comment 6 Storm Engineer 2018-11-14 08:35:11 UTC

I would love to hear from the devs about the status of this as well.

It's a real pain that sometimes things will open with the corresponding Windows application under Wine instead of the properly installed corresponding Linux application.

Comment 7 Patrick Silva 2019-03-29 14:29:28 UTC

I can't reproduce following the steps provided by the reporter.
I also can't reproduce the problem with pdf files described in comment 5.

Operating System: Arch Linux 
KDE Plasma Version: 5.15.3
KDE Frameworks Version: 5.56.0
Qt Version: 5.12.2

Comment 8 Walther Pelser 2019-12-08 11:17:49 UTC

In the last weeks I have the same problem. Syremsetting5 cannot change the file endings at the end of the prozess. It changes the file in ~/.local/mime/application/vnd.lotus-1-2-3.xml for instance, but this takes no effect. Expected behaviour was: the local file should override the settings in /usr/share/mime/application/vnd.lotus-1-2-3 in this example, but this does not happen. It seems, that that the changed userdefined mime types are not read again by systemsettings5 to make them work.

Comment 9 Walther Pelser 2019-12-09 11:10:47 UTC

It seems only affect to the filetype *.123. See Bug # 414742, maybe if this bug is solved this bug is solved too?