FS#48224 - [wine-staging] produced .desktop files point to wrong wine executable
Attached to Project:
Community Packages
Opened by adderly (moisex00) - Wednesday, 17 February 2016, 20:06 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 17 March 2019, 12:51 GMT
Opened by adderly (moisex00) - Wednesday, 17 February 2016, 20:06 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 17 March 2019, 12:51 GMT
|
Details
Description:
When installing an application, the .desktop files are registered with wrong wine path. I presume this behavior will prevail for any desktop application installed with wine. I installed Evernote_5.9.6.9494.exe, and it produced the file as follows: [Desktop Entry] Name=Evernote Exec=env WINEPREFIX="/home/name/.config/wine" /build/wine-staging/pkg/wine-staging/usr/bin/wine C:\\\\Program\\ Files\\\\Evernote\\\\Evernote\\\\Evernote.exe Type=Application StartupNotify=true Comment=Evernote Path=/home/name/.config/wine/dosdevices/c:/Program Files/Evernote/Evernote/ Icon=ED36_Evernote.0 Terminal=true X-KeepTerminal=true It points to this wine executable: /build/wine-staging/pkg/wine-staging/usr/bin/wine I tried with another application :AirDroid_Desktop_Client_3rdmarket.exe. Which produces a .desktop files with the same problem. [Desktop Entry] Name=AirDroid Exec=env WINEPREFIX="/home/name/.config/wine" /build/wine-staging/pkg/wine-staging/usr/bin/wine C:\\\\windows\\\\command\\\\start.exe /Unix /home/name/.config/wine/dosdevices/c:/users/Public/Desktop/AirDroid.lnk Type=Application StartupNotify=true Path=/home/name/.config/wine/dosdevices/c:/Program Files/AirDroid Icon=10AC_AirDroid.0 Additional info: * wine-staging 1.9.2 * config and/or log files etc. Steps to reproduce: * wine Evernote*.exe/AirDriod*.exe |
This task depends upon
Closed by Laurent Carlier (lordheavy)
Sunday, 17 March 2019, 12:51 GMT
Reason for closing: No response
Sunday, 17 March 2019, 12:51 GMT
Reason for closing: No response
Comment by
Felix Yan (felixonmars) - Thursday,
18 February 2016, 07:23 GMT
wine-staging 1.9.2 was built with some issues in the PKGBUILD.
Please let me know if it still persists with wine-staging 1.9.3.