Bug 294112

Summary:	SVG files get open in web browser despite file association being set for Inkscape
Product:	[Frameworks and Libraries] kdelibs	Reporter:	Ctibor Brančík <ctibor.brancik>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	jacobrdalton
Priority:	NOR
Version:	4.8
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:

Description Ctibor Brančík 2012-02-14 22:43:26 UTC

Version:           4.8 (using KDE 4.8.0) 
OS:                Linux

My SVG files are opened in web browser. I use chromium as a default browser set in system-settings.

I have SVG files assigned to Inkscape in file association configuration screen (both compressed and uncompressed variant). I can see Inkscape on top of the programs when I right click SVG file a navigate to "Open with" menu. I have quite a few SVG files, happens with all of those I have tried recently.

Reproducible: Always

Steps to Reproduce:
1. Set chromium as your default browser.
2. Confirm SVG files are assigned to Inkscape.
3. Click on SVG file to open it in Inkscape.

Actual Results:  
File is opened in Chromium instead of Inkscape.

Expected Results:  
File should be opened in Inkscape or any other application actualy associated with this file type.

Changing back to the default in the browser configuration makes SVGs open in Inkscape well.

Comment 1 Jekyll Wu 2012-02-18 08:36:35 UTC


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

Comment 2 Jacob Dalton 2012-09-26 20:13:13 UTC

I'm also affected by this bug. KDE 4.8.5 (on Kubuntu 12.04). Local html and svg files are opened by default browser set in System Settings -> Default Applications -> Web Browser regardless of settings in File Associations. I had to set the default to 'in application based on contents of URL' but now I can't open remote files in applications like Quassel.

Comment 3 Jekyll Wu 2012-09-26 20:23:19 UTC

Jacob, if you have read this bug report carefully, you should have known this is a duplicate and the problem has been fixed in KDE SC 4.9

Comment 4 Jacob Dalton 2012-09-26 20:33:29 UTC

My apologies I glossed the duplicate report and saw someone report it fixed in 4.8.3, but obviously it wasn't.