Bug 19392

Summary:	xdg-mime does not support KDE4
Product:	Portland	Reporter:	Pino Toscano <toscano.pino>
Component:	xdg-utils	Assignee:	Fathi Boudra <fabo>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium	CC:	pablo
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Pino Toscano 2009-01-04 17:33:27 UTC

xdg-mime strictly refers to KDE3:
- uses `kbuildsycoca`; it is `kbuildsycoca4` in KDE4
- uses `kfile` to get the MIME type of a file; should be `kmimetypefinder` in KDE4
- writes the local application associations for MIME types to $KDEHOME/share/config/profilerc (with '.kde' hardcoded, even!, instead of using `kde(4)-config --localprefix`); this should be in the common ~/.local/share/applications/mimeapps.list (as discussed some time ago by D. Faure and A. Larsson on the xdg list, IIRC)
- uses `ktradertest` to check the default application associated with a MIME type; should be `ktraderclient --mimetype application/pdf --servicetype Application`

Comment 1 Rex Dieter 2009-01-04 18:01:00 UTC

many kde4-related issues should already be addressed (in cvs) while fixing bug #16212
 
I'll double check those you raise here.

Comment 2 Fathi Boudra 2009-07-28 06:22:17 UTC

I fixed ktraderclient/ktraderclient on CVS today.

Comment 3 Fathi Boudra 2009-07-28 06:22:43 UTC

I mean ktradertest->ktraderclient :)

Comment 4 Fathi Boudra 2009-07-28 14:18:14 UTC

fixed in CVS: kfile/KDE3 and kmimetypefinder/KDE4

Comment 5 Fathi Boudra 2009-07-28 14:28:50 UTC

fixed in CVS: kbuilsycoca4/KDE4 and kbuildsycoca/KDE3

Comment 6 Pablo Castellano (pablog) 2010-01-23 07:59:03 UTC

Looks like this bug is resolved.

Maybe the only missing thing would be use "kde(4)-config --localprefix" instead of using directly "$HOME/.kde/..." which is used now. But now at least ".kde" is not hardcoded in $KDEDIR.

I would close this bug, because xdg-mime now supports KDE4.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.