Bug 322575 - Dolphin cannot open python, sh, lua, etc, files.
Summary: Dolphin cannot open python, sh, lua, etc, files.
Status: RESOLVED DUPLICATE of bug 275405
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 4.10.5
Platform: Arch Linux Linux
: NOR major
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-19 15:06 UTC by SaburoutaMishima
Modified: 2013-07-19 15:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SaburoutaMishima 2013-07-19 15:06:54 UTC
Any text file with an executable bit cannot be opened with the left mouse button or enter. It does not matter what preferences the user sets. It does not matter what program is set to open the file. Even if the "executable" tag ( re: <sub-class-of type="application/x-executable"/> ) part of the freedesktop.org.xml is manually stripped from the configuration, it does not matter. It does not matter what default file associations are set IN DOLPHIN. No matter what the user does, the user's preferences are 100% ignored by Dolphin.

Reproducible: Always

Steps to Reproduce:
1.Open dolphin
2.Open any text file with 'x' permission for the current user
Actual Results:  
Nothing. Literally nothing.

Expected Results:  
Anything. Especially the file opening.

There are several fixes floating around out there, but they only seem to work for "*.sh" files. Python and LUA files, for example, seem to be unfixable. Furthermore, several of the fixes require manually editing files that no one should be manually editing, or require being able to disable executable permissions which is not possible in certain situations (ie, not all filesystems support normal permissions granularity).

I feel a file manager should be able to open files.
Comment 1 Frank Reininghaus 2013-07-19 15:14:09 UTC
Thanks for the bug report. This issue has been reported already.

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