Bug 302549 - Dolphin open files with wrong association
Summary: Dolphin open files with wrong association
Status: RESOLVED DUPLICATE of bug 291177
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 2.0
Platform: unspecified Linux
: NOR major
Target Milestone: ---
Assignee: Frank Reininghaus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-26 08:22 UTC by thomi_ch
Modified: 2012-06-26 12:09 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thomi_ch 2012-06-26 08:22:35 UTC
Hello
I using KDE 4.8.4 on Kubuntu 12.04:
LSB Version:    core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch                   
Distributor ID: Ubuntu
Description:    Ubuntu 12.04 LTS
Release:        12.04
Codename:       precise

The problem is: Opening a xml file with double click will start Firefox instead of Kate, which is the default application for xml files: http://i.imgur.com/m4Iov.png

Same problem is with .mwb (MySQL Workbench) files, they will be opened with Ark instead of MySQL Workbench:
http://i.imgur.com/QD42H.png
http://i.imgur.com/D4fjK.png

The strange thing for .mwb files is that it's type is "ZIP Archive": http://i.imgur.com/Y09SU.png

The .mwb behavior can be a miss configured file type association, but the xml issue is a bug since KDE 4.8.x.

Btw. you can test it with kde-open your-file.xml...

Thanks for help

Kind Regards
thomi

Reproducible: Always

Steps to Reproduce:
1. open Dolphin
2. double click a xml file
3. Firefox will start

Other steps to reproduce
1. open konsole
2. run command: kde-open your-file.xml
3. Firefox will start


Expected Results:  
Dolphin/kde-open should use the default associated application to open the xml file.
Comment 1 Jekyll Wu 2012-06-26 12:09:44 UTC

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