top of page

cedzlabs

Public·75 members

Wine 1.7.24 Released!



Edit: Due to the fact that this article is old, the installation instructions may not work anymore. In order to successfully install the latest version of Wine, please access the wine tag and open the latest article (the one on top).




Wine 1.7.24 Released!



The latest version available is Wine 1.7.22, which has been released a while ago, coming with support for Unicode bracketing pairs, got support for geographical information, received improved internet cookie support and bug-fixes for the already known issues.


Because it will be soon available via PPA, installing Wine 1.7.22 on the listed Ubuntu, Linux Mint, LXLE, Pinguy OS, Peppermint and Elementary OS systems is easy. All you have to do is add the ppa to your system, update the local repository index and install the wine1.7 and winetricks packages. Like this:


This overlay allows you to build latest git version of mesa and wine with the gallium nine patches. Wine has to translate DirectX => OpenGL => Gallium, which add complications and brings inefficiency. Thanks to the gallium nine state tracker we simply skip the OpenGL translation. More info here: -wine-games-with-open-source-drivers-d3d9-aka-gallium-nine/


Latest wine version is currently 1.7.26 while latest version available in gentoo repositories is only 1.7.21. This overlay allows you to build latest version of wine with pulseaudio, pipelight (compholio) and gstreamer support.


Description:Ubuntu 14.04.1 LTSRelease:14.04wine: Installed: 1:1.6.2-0ubuntu4 Candidate: 1:1.6.2-0ubuntu4 Version table: *** 1:1.6.2-0ubuntu4 0 500 trusty/universe amd64 Packages 100 /var/lib/dpkg/status


ProblemType: BugDistroRelease: Ubuntu 14.04Package: wine 1:1.6.2-0ubuntu4ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2Uname: Linux 3.13.0-30-generic x86_64ApportVersion: 2.14.1-0ubuntu3.2Architecture: amd64CurrentDesktop: UnityDate: Tue Aug 5 20:52:11 2014InstallationDate: Installed on 2014-05-03 (94 days ago)InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)SourcePackage: wine1.6UpgradeStatus: Upgraded to trusty on 2014-05-31 (66 days ago)


I think, wine should use a separate directory for the desktop or there shouldbe a way to disable such integrations before building wine. For example, Iwant to use a kicker menu extension for KDE which shows the start menu andsome other dirs and do not want wine to try integrating itself to windowmanager.


Confirming. As far as I can tell, if you run winecfg and go to DesktopIntegration tab, and click on Desktop under shell folders, and uncheck the LinkTo box, then only the Linux compatible icon is put on the Desktop, while the.lnk file is put into the Desktop folder in wine's drive_c/windows/profiles


I suggested that, but unfortunately the developers can't reproduce this issue asfar as I can tell. Actually if you have binfmt_misc setup properly on yoursystem, you can use the .lnk files. So IMHO, wine should just drop .desktopicon creation and change the icon for the .lnk files.


The reason wine puts both the Freedesktop icon and the Window icon is due towinecfg having the windows desktop set to the same location as the Linuxdesktop (/Desktop).. Either we need to change the default location tosomewhere else, or (better yet) we should intercept .lnk file creation andput .lnk files to /.wine/drive_c/windows/Desktop while everything else goesto the linux desktop...


Yes, but the .lnk files would not work correctly for prefixes other than the default. Also, the desktop environment would probably have to create a winelib process to thumbnail the .lnk files, which could be expensive.


(In reply to comment #21)> Yes, but the .lnk files would not work correctly for prefixes other than the> default. Also, the desktop environment would probably have to create a winelib> process to thumbnail the .lnk files, which could be expensive.


Applications that install .lnk files to the public desktop end up putting those files under /.wine/drive_c/users/Public/Desktop, from which winemenubuilder generates a .desktop file in /Desktop. All is well.


But some applications (eg. WinRAR) want to install .lnk files to the user's desktop, which is /.wine/drive_c/users/user/Desktop, but that isn't a directory, it's just a symlink to /Desktop. So the .lnk file goes onto the real desktop instead of the hidden one.


The selection of where to save the .lnk happen in shell32's IShellLink's IPersistFile COM interface, before winemenubuilder is launched. By the time winemenubuilder runs, the .lnk file already exists in the wrong place.


It would be possible for winemenubuilder to move or delete the .lnk file after it generates the .desktop file, but then we'd lose track of the .lnk .desktop mapping which winemenubuilder can do in order to delete .desktop files when the corresponding .lnk files are gone (because eg. the application was uninstalled). Some more intelligent Wine desktops /Desktop synchronization might be necessary.


The only thing I can think of that would fix this is to virtualize the filesystem - eg. use a FUSE module that merges /.wine/drive_c/users/user/Desktop with /Desktop when reading, but write .lnk files to /.wine/drive_c/users/user/Desktop and everything else to /Desktop.


so when some application want to write .lnk file to:/.wine/drive_c/users/user/Desktophandle it and redirect to:/.wine/drive_c/users/Public/Desktopand when uninstaller will want to delete it from:/.wine/drive_c/users/user/Desktophandle again and redirect to:/.wine/drive_c/users/Public/Desktop


(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/Desktopand Wine instead writes to:/.wine/drive_c/users/Public/Desktopthe application still thinks it wrote to:/.wine/drive_c/users/user/Desktopand on uninstall tries to delete the .lnk from:/.wine/drive_c/users/user/Desktopwhere it isn't.


Pre-packaged .lnk files that get just copied into place would bypass shell32's IShellLink's IPersistFile_Save, and winemenubuilder won't get invoked to build .desktop files. Such files also imply that you can't choose where to install the application, since that affects the .lnk contents?


Still present in Notepad++ 6.1.1 using Fedora 16 x86_64 with wine 1.5.1.I'm not sure if any ideas on this have changed from Gnome3/Unity/OtherDE? with new method of not showing the files. Is this a large issue any more (for certain D.E.)? Has this move changed ideology for .lnk files being a viewable issue?


(In reply to comment #40)> Still present in Notepad++ 6.1.1 using Fedora 16 x86_64 with wine 1.5.1.> I'm not sure if any ideas on this have changed from Gnome3/Unity/OtherDE? with> new method of not showing the files. Is this a large issue any more (for> certain D.E.)? Has this move changed ideology for .lnk files being a viewable> issue?


(In reply to comment #29)> (In reply to comment #28)> > Perhaps we could move the .lnk's from the 'user' desktop to the 'public'> > desktop, which would keep it off the 'real' desktop, but also allow keeping> > track of it to remove the .desktop for later removal?>> 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.>> The only thing I can think of that would fix this is to virtualize the> filesystem - eg. use a FUSE module that merges> /.wine/drive_c/users/user/Desktop with /Desktop when reading, but write .lnk> files to /.wine/drive_c/users/user/Desktop and everything else to /Desktop.


As for the link tracking, the same thing happens in Windows when one moves the .lnk file from their personal start menu folder or desktop to the public one. IMHO, it should just be considered expected behaviour for the links to be manually removed from the user's desktop when an app is uninstalled. That or do a forced check of the user's desktop for a .desktop file in the wine uninstaller tool, though I think the manual removal idea is better, personally.


That way it could be mounted with the loopback driver already in the kernel and reads/writes would just take place to the mount point. It would make managing things easier because the user could create an fstab-like file for wine to read (or just do it in winecfg) to specify the mount point and path to the file containing wine's filesystem -- That's the one thing I've always disliked about wine was having the filesystem default to being under my home directory.


Rather, I dislike that it defaults to being in .wine under my home directory. I'd be OK with it being inside a hidden file, because it's a single file, rather than a whole folder that some tools (grep -R, find, etc) would then search through.


Also, if the filesystem is virtualized from inside of a single file, then the user's desktop can be an actual folder and wine can track links to that between it and the real /Desktop. In addition it solves a lot of issues with multiple users in the linux system wanting to share a single prefix (could move the prefix out of /.wine and into /home/.wine or /home/wine as well as allowing one to have and manage multiple prefixes from within winecfg could become easier)...


About

Welcome to the group! You can connect with other members, ge...
bottom of page