Comment 35 for bug 1353024

Revision history for this message
In , Damjan Jovanovic (damjan-jov) wrote :

(In reply to comment #30)
> > The application tells shell32 to write the .lnk file to a specific
> > C:\path\to\file.lnk location and remembers that location. Any attempt to move
> > or rename the .lnk after that - even to the other desktop - loses that file and
> > stops the application from deleting it on uninstall.
>
> so when some application want to write .lnk file to:
> ~/.wine/drive_c/users/user/Desktop
> handle it and redirect to:
> ~/.wine/drive_c/users/Public/Desktop
> and when uninstaller will want to delete it from:
> ~/.wine/drive_c/users/user/Desktop
> handle again and redirect to:
> ~/.wine/drive_c/users/Public/Desktop
>
> Can it work just like that?

If the application wants to write .lnk file to:
~/.wine/drive_c/users/user/Desktop
and Wine instead writes to:
~/.wine/drive_c/users/Public/Desktop
the application still thinks it wrote to:
~/.wine/drive_c/users/user/Desktop
and on uninstall tries to delete the .lnk from:
~/.wine/drive_c/users/user/Desktop
where it isn't.