Bug 387651

Summary:	Plasma does not remember settings for open odt files
Product:	[I don't know] kde	Reporter:	jmarinho.73
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	nate
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description jmarinho.73 2017-12-06 16:30:09 UTC

I Have Kde-Neon 5.11.4 installed and when I open an .odt file it always open it with Okular instead of LO Writer. I change this behavior on Settings --> Applications --> File associations and in Dolphin --> Riht Click on an .odt file --> Properties with no luck. At first it seems that the behavior changes but at next reboot system opens odt files with Okular again.
It only happens with .odt files, not ods or odp ones, and I think it is because when I installed Kde-Neon on my computer a week ago, I opened an odt file that I have, with some notes about what I use to do (configurations and install software) after a fresh install. I did prior to install any additional software of that comes installed by default and without LO Writer installed on my system Okular opens that file. That's why now Okular is the default app for opening that files and I can't change it because I think there is a bug and the system does not rembember  the new file association.

Comment 1 jmarinho.73 2017-12-07 09:34:34 UTC

Further information:
Sometimes when I try to promote Libreoffice Writer at first place for opening odt files, the setting was not saved when I press "Apply". I have to try several times. What works instead is to send down Okular to the second place, but how I said before, this setting does not remains after reboots

Comment 2 jmarinho.73 2017-12-14 16:48:17 UTC

After some days I have observed that this bug seems solved on my computer. I don't know if it is because of some update or what. Since three or four days, when I start my system and try to open an .odt file it opens with LO Writer as it should and this behavior remains the same for this last days. Perhaps this bug might be closed but I don't find where I can do that so I'm going to mark it as solved. If the bug reappears I'll reopen it.

Comment 3 Nate Graham 2017-12-14 17:01:48 UTC

Thanks for the update!