Bug 314383

Summary: incorrect entries in kde4 directory prevents opening files
Product: [I don't know] kde Reporter: Philip Aston <philip.aston>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED FIXED    
Severity: minor CC: nate, rdieter
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Philip Aston 2013-02-03 21:30:16 UTC
Fedora Core 17, kde loaded from yum:  There is a consistent mistake in the /usr/share/applications/kde4 directory. The file references are kde4-{filename} where they should be kde4/{filename}. Until this is corrected (I have been doing this manually) it is in some cases impossible to open a file directly from file explorer. (There is also a mistake in fc itself, incorrect references in /usr/share/applications/mimetypes,info, see https://bugs.freedesktop.org/show_bug.cgi?id=59007   )

Reproducible: Always

Steps to Reproduce:
1. Try to open a *.doc or *.html from a file explorer
2.
3.
Actual Results:  
There is no application available

Expected Results:  
Opened the file with a default application
Comment 1 Andrew Crouthamel 2018-11-09 01:04:43 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-20 03:58:30 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Nate Graham 2020-09-28 22:42:06 UTC
No response; assuming it was fixed since then.