Bug 323029

Summary:	could not change the priority of the "Open With"
Product:	[Unmaintained] kdelibs	Reporter:	TOM Harrison <l12436.tw>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED DUPLICATE
Severity:	major	CC:	frank78ac, jonan88, kde
Priority:	NOR
Version:	4.10.95
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description TOM Harrison 2013-07-31 02:09:09 UTC

since upgrade to 4.10.80.
the dolphin "Open With" priority could not be changed.
In the change window could move the priority.
but it did not save.
also keep the original priority
and even the system settings could not change.

Reproducible: Always

Comment 1 Frank Reininghaus 2013-07-31 08:52:05 UTC

Thanks for the bug report. Dolphin itself does not decide which application to use, so I guess that this is a kdelibs problem. I cannot do much testing now because I'm not at my development machine.

To make your bug report useful, please describe exactly how you tried to change the "priority".

Comment 2 TOM Harrison 2013-07-31 11:53:52 UTC

i change the settings from this window
http://i.imgur.com/yjgtMTv.png
after i post this bug, i found the system could not change too.

Comment 3 Frank Reininghaus 2013-07-31 20:07:25 UTC

I cannot reproduce the problem in master.

Comment 4 Jon Ander Peñalba 2013-07-31 20:20:21 UTC

I can reproduce the problem in master and in 4.10.5, but it doesn't happen every time.
I tried changing the priority a few times and I could notice some changes weren't being saved.

Comment 5 TOM Harrison 2013-08-01 07:24:36 UTC

this is the video about this problem.
http://www.youtube.com/watch?v=jAKlsSQreMo&feature=youtu.be
maybe this will help.

Comment 6 Kai Uwe Broulik 2013-08-01 09:06:20 UTC

I can sometimes reproduce the problem. For example XML files were by default opened with Chromium but I moved Chromium down to have Kate at the top but it didn't save properly.

Comment 7 Frank Reininghaus 2013-08-10 08:04:45 UTC

Looks like bug 321706.

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