I just discovered today that the Wine file association commands aren't working. When I double-click an exe file in Dolphin, nothing happens. When I right-click a txt file and try to open it in Notepad, I get an "Internal Error" message box.
If I go directly to a terminal and enter "wine file.exe" the program loads just fine. Or when I do "wine notepad file.txt" it loads. So I went to System Settings, went to the File Associations page, and found the exact commands used when those file types are accessed via Wine. Here's the result:
I tried using an alternate WINEPREFIX for the txt file and it gave me the same error, so it's an issue with Wine, not that particular configuration. Any idea what's wrong?
If I go directly to a terminal and enter "wine file.exe" the program loads just fine. Or when I do "wine notepad file.txt" it loads. So I went to System Settings, went to the File Associations page, and found the exact commands used when those file types are accessed via Wine. Here's the result:
Code:
~/.wine/drive_c/Poacher$ env WINEPREFIX="/home/darthbrandon/.wine" wine start /ProgIDOpen txtfile readme.txt getting server_pid from lock 13049 wine: cannot get pid from lock (lock isn't locked) err:process:start_wineboot failed to start wineboot, err 1359 fixme:exec:SHELL_execute flags ignored: 0x00000100 getting server_pid from lock 13049 wine: cannot get pid from lock (lock isn't locked) getting server_pid from lock 13049 wine: cannot get pid from lock (lock isn't locked) Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: Success.
Code:
~/.wine/drive_c/Poacher$ wine start /unix poacher.exe getting server_pid from lock 14196 wine: cannot get pid from lock (lock isn't locked) err:process:start_wineboot failed to start wineboot, err 1359 getting server_pid from lock 14196 wine: cannot get pid from lock (lock isn't locked) Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: Internal error.
Comment