| Summary: | File Association Isn't Respected | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | vindicator <nroycea+kde> |
| Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kdelibs-bugs-null, meven29, nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.81.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
vindicator
2021-04-21 20:43:37 UTC
> 3. Change file association property, adding chrome to the list, but dropping it to the bottom.
How did you do that exactly ?
Which application did you use, did you hit apply ?
I don't reproduce this bug neither from the file association kcm (in systemsettings) or from the file dialog properties, type association sub-dialog.
Wow, okay, I have no idea what is going on, but I was setting things up so I could record a video for it, and I tested it again without making any changes, but only double-clicking on the readme file, and it opened in kate. I also went back to the original activity I was working in, and it opened fine there as well. I also removed the Chrome entry in file-association properties, and it also opened in kate with no issues. No clue what happened there. I had been changing the file-association properties in dolphin (right-mouse->properties->general->file-type-options). Again, nothing changed, as I was still in that same session as yesterday (no reboot, no logout, no closing of kate/chrome/dolphin, ...). I just woke up, saw your email, switched to another activity which was blank so I could record the process I did, tried clicking the file, and it opened just fine in kate. Bizarre. > Again, nothing changed, as I was still in that same session as yesterday (no reboot, > no logout, no closing of kate/chrome/dolphin, ...). I just woke up, saw your email, > switched to another activity which was blank so I could record the process I did, tried clicking the file, and it opened just fine in kate.
> Bizarre.
This can happen when the cache is being updated handled by kservice or its new state hasn't propagated yet, a race condition basically.
I'm familiar with race conditions. However it doesn't explain how it happened to begin with when chrome was NEVER in the list (kate, librewriter, notepad) from the start, until I added it to test if adding then removing it would make a difference. Besides, I would figure race conditions are typically quick, like in ms, or however long it takes for a thread to release hold of whatever it's got locked. Not something that wouldn't go on for an hour, or need multiple hours to release. Not a huge deal or anything. Just an annoyance (just select open-with for the file to force it). Should it happen again, I hope to remember to start up a video capture for evidence. |