Bug 183153 - Cannot configure file associations
Summary: Cannot configure file associations
Status: CLOSED FIXED
Alias: None
Product: kde-windows
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: KDE-Windows
URL:
Keywords:
: 245358 279497 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-02-04 11:37 UTC by Spinus
Modified: 2012-03-02 09:05 UTC (History)
5 users (show)

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 Spinus 2009-02-04 11:37:14 UTC
Version:           4.0.2-1 (using KDE 4.2.0)
OS:                MS Windows
Installed from:    MS Windows

I want to associate swriter.exe to file type like .odt/.doc. I go to systemsettings->file associations, select "msword" mime type and then I add a new application: I must enter manually the location of swriter because KDE4 doesn't know registered application present on windows. After selecting the application and pressing OK, the dialog for selecting application gives an error "c:\programs\OpenOffice.org\program\swriter.exe not found"

I've tried with other applications, but the issue is the same!

I've also tried using dolphin/konqueror and clicking on "file->open with->other...": in this case the native windows dialog appears; I can select swriter and open the file, but if I select "Always use the selected program to open this kind of file" the association is not saved.
Comment 1 Tom 2009-02-04 15:43:33 UTC
I'm having similar problems.  I'm also using KDE v4.2, and I'm on Windows Vista SP1.

Here are some details on the problems I encountered:

When I try to load a text file into Kate from within the KDE environment (I used Dolphin): "Error launching C:/Program Files/KDE/share/applications/kde4/kate.desktop. Either KLauncher is not running anymore, or it failed to start the application."

So I tried to create an association in Windows.  My first problem was that Windows doesn't know of the Kate application.  I think that the KDE apps should be registered with Windows.

Now I've created an association between text file (*.txt) and Kate in Windows.  However, when I open a text file from the Windows shell it creates a completely new session of Kate ('new' in that this new session doesn't even know of my settings).



Comment 2 David Faure 2009-02-10 00:23:57 UTC
I can't debug this, it works on linux.
All I can say to the kde-windows developers is: look for the KStandardDirs::findExe() call in kopenwithdialog.cpp. If it fails on a valid path, I recommend starting by adding some unit tests in kdecore/tests/kstandarddirstest.cpp (there's a testFindExe already).
Comment 3 chosunsk 2010-01-01 23:44:35 UTC
I can confirm this as well with kde-windows 4.3.4.

However, it seems that some things have been improved.  The associated program opens fine, but the filepath given to it from dolphin is screwed up.  For instance, associating a spreadsheet (i.e. D:\spreadsheet.xls) for excel starts up excel, but it provides this following message:

'\D:\spreadsheet.xls' could not be found.

I think if the path was missing the first "\", then excel might have worked.
Comment 4 Andrew 2011-08-07 00:26:00 UTC
*** Bug 279497 has been marked as a duplicate of this bug. ***
Comment 5 Patrick Spendrin 2012-03-01 01:03:39 UTC
Git commit f7afd61f07a26085f4683977009840291ddf336e by Patrick Spendrin.
Committed on 01/03/2012 at 01:59.
Pushed by sengels into branch 'KDE/4.8'.

fix configuration of file associations using full paths
this doesn't fix yet that spaces should be handled correctly.

M  +4    -0    kio/kfile/kopenwithdialog.cpp

http://commits.kde.org/kdelibs/f7afd61f07a26085f4683977009840291ddf336e
Comment 6 Patrick Spendrin 2012-03-01 01:06:14 UTC
Since KDE 4.8.1 is tagged today, I still need to see if I want to backport that fix to 4.8.0 or if I will simply wait for our 4.8.1 binaries.
Comment 7 Patrick Spendrin 2012-03-02 09:05:31 UTC
*** Bug 245358 has been marked as a duplicate of this bug. ***