https://bugs.winehq.org/show_bug.cgi?id=42297
Bug ID: 42297 Summary: Gecko does not install itself in 2.0rc6 Product: Wine-gecko Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gecko-unknown Assignee: jacek@codeweavers.com Reporter: proveit@tutamail.com Distribution: ---
I'm using the latest version of Wine in the development branch (2.0rc6). This bug occurs on Linux Mint Mate 32-bit. The bug is simple. In the past, when running any program in a development branch version of Wine, Wine always prompted me to install gecko and mono when I first run a program.
The prompting is expected behavior: "WineHQ does not at present package wine-gecko or wine-mono. When creating a new wine prefix, you will be asked if you want to download those components. For best compatibility, it is recommended to click Yes here." (Source: https://wiki.winehq.org/Ubuntu)
The instructions from the Gecko wiki page (https://wiki.winehq.org/Gecko) to manually install Gecko also does not work. The page says to download the .msi file manually (wine_gecko-2.47-x86.msi in my case) and copy it to /usr/share/wine/gecko. Not only does the directory wine not exist in /usr/share in a standard installation of the development branch from PPA (sudo apt-get install --install-recommends winehq-devel), but even when I create the wine/gecko directory under /usr/share, copying the .msi file there seems to do nothing when I run a program in a clean wine prefix.
In other words, gecko can't be installed at all in the latest version of Wine development branch. The automatic install fails, and so does the manual install.
https://bugs.winehq.org/show_bug.cgi?id=42297
proveit@tutamail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Mint
https://bugs.winehq.org/show_bug.cgi?id=42297
--- Comment #1 from Bruno Jesus 00cpxxx@gmail.com --- After downloading the package once correctly wine will no longer prompt, it will always automatically install while the prefix is being created.
To double check if the package is installed or not you can use "wine uninstaller". In a clean prefix uninstaller should show only Wine Mono and Wine Gecko with their respective versions.
https://bugs.winehq.org/show_bug.cgi?id=42297
--- Comment #2 from proveit@tutamail.com --- Well, that is precisely the bug for me; Wine doesn't automatically install gecko and mono while the prefix is being created. I tested it on a new computer that had never had Wine installed, and Wine immediately prompted me to install Gecko and Mono as soon as a new prefix was created, so the problem isn't universal.
However, I seem to have done something to the computer with the bug that makes Wine NOT prompt me even on a clean prefix, which is the strange part. Since it's a clean prefix, it could not possibly have gecko or mono installed.
It's the exact same version of Wine on both computers: 2.0rc6. Have I simply changed a setting accidentally that blocks the prompt on newly created prefixes?
https://bugs.winehq.org/show_bug.cgi?id=42297
--- Comment #3 from Nikolay Sivov bunglehead@gmail.com --- It prompts you to download gecko and mono, not to install them if they are already downloaded. Removing your wineprefix does not remove gecko or mono packages that were already downloded on first ever run.
https://bugs.winehq.org/show_bug.cgi?id=42297
--- Comment #4 from proveit@tutamail.com --- Hmm, I didn't know that. I knew wine-gecko and wine-mono packages installed from official repository were independent from wine prefixes, but I thought the prompt from Wine HQ development version, which doesn't use official repository packages, would install gecko and mono inside the prefix itself. If they're not inside the prefix, where are they?
https://bugs.winehq.org/show_bug.cgi?id=42297
--- Comment #5 from Bruno Jesus 00cpxxx@gmail.com --- They are stored in a folder inside your home folder, at least for me in Debian:
bruno@Note:~$ ls ~/.cache/wine wine_gecko-1.8-x86.msi wine_gecko-2.40-x86.msi wine-mono-4.5.6.msi wine_gecko-2.21-x86.msi wine_gecko-2.47-x86.msi wine-mono-4.6.3.msi wine_gecko-2.24-x86.msi wine-mono-0.0.8.msi wine-mono-4.6.4.msi wine_gecko-2.34-x86.msi wine-mono-4.5.2.msi wine_gecko-2.36-x86.msi wine-mono-4.5.4.msi
Then when a new prefix is created wine checks if you already have the current gecko/mono version downloaded, if yes then it will auto install, if not it will prompt for download and store in this folder.
Did you check wine uninstaller?
https://bugs.winehq.org/show_bug.cgi?id=42297
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #6 from winetest@luukku.com --- Bruno you should be safe to remove those old packages.
I think wine doesnt prompt to download mono and gecko if the 1st prefix with new wine and new mono/gecko is canceled. It only asks for once.
https://bugs.winehq.org/show_bug.cgi?id=42297
proveit@tutamail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #7 from proveit@tutamail.com --- Bruno, I just checked it now on a second clean prefix. Looks like it is indeed there even though the second prefix never prompted me. This bug was a misunderstanding on my part. I marked it solved.
https://bugs.winehq.org/show_bug.cgi?id=42297
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Bruno Jesus 00cpxxx@gmail.com --- (In reply to proveit from comment #7)
Bruno, I just checked it now on a second clean prefix. Looks like it is indeed there even though the second prefix never prompted me. This bug was a misunderstanding on my part. I marked it solved.
This sort of bug is always useful so the documentation can be made more clear to reduce other possible similar issues.
(In reply to winetest from comment #6)
Bruno you should be safe to remove those old packages.
I test many old Wine versions so those packages are installed by then.
https://bugs.winehq.org/show_bug.cgi?id=42297
--- Comment #9 from proveit@tutamail.com --- Bruno, exactly how do you test old Wine versions? I've been looking for a way to test Wine (package from my official repositories) and Wine HQ's PPA (development branch) without having to remove the packages between tests. I believe there is some conflict between those packages, so I have never had more than one version of Wine installed on the system at once.
https://bugs.winehq.org/show_bug.cgi?id=42297
--- Comment #10 from Bruno Jesus 00cpxxx@gmail.com --- (In reply to proveit from comment #9)
Bruno, exactly how do you test old Wine versions? I've been looking for a way to test Wine (package from my official repositories) and Wine HQ's PPA (development branch) without having to remove the packages between tests. I believe there is some conflict between those packages, so I have never had more than one version of Wine installed on the system at once.
Basically I used to compile Wine and "make install" at different places, I choose random versions as time passed (some stable, some development). Currently the easiest way to do it is using PlayOnLinux IMO, you can install almost any Wine version. But some PlayOnLinux Wine versions includes custom patches that may or may not affect what you are trying to test so you have to be careful.
-
wine-bugs＠winehq.org