Lotro problems [Solved]

[Otomo]

Hi,

I recently migrated from Kubuntu to Sabayon 64 bits (updated until now), and all my wine games keep on running the same except one, Lord of the Rings Online. I read that a year ago Gentoo user (as is logical) had this problem too, but it was solved with new 32 bits libs version. So I don't know what happens, but I suspect is the same problem. Anyway I hope someone in this forum could bring some light to this problem. I attached the output:

http://pastebin.com/HEzumG9f

Thanks in advance

[Fitzcarraldo]

You need to use WINE with the 32-bit WINEARCH if you have a multilib (32-bit and 64-bit) WINE installation (the default if you have installed 64-bit SL). I also recommend that you use a WINEPREFIX to ring-fence the 32-bit Windows application (see the thread Wine is wonderful is you do not know what is a WINEPREFIX).

If I have WINE built with both win32 and win64 USE flags (the default for 64-bit multilib SL), if I don't assign WINEARCH=win32 and install a 32-bit Windows application then WINE creates a $WINEPREFIX/Program Files (86)/ directory as well a $WINEPREFIX/Program Files/ directory, and installs the 32-bit Windows application's directory under $WINEPREFIX/Program Files (86)/. However the 32-bit Windows application will not run and I get an error message:

Code: Select all

wine: WINEARCH set to win32 but <WINEPREFIX> is a 64-bit installation.

If I have WINE built with both win32 and win64 USE flags, if I do assign WINEARCH=win32 and install a 32-bit Windows application then WINE does not create a $WINEPREFIX/Program Files (86)/ directory, only a $WINEPREFIX/Program Files/ directory, and installs the 32-bit Windows application's directory under $WINEPREFIX/Program Files/. In this case I do not have any error messages and no problems running the 32-bit application. As evidence, below I show what happens when I install a 32-bit Windows application (WinMd5Sum), run it successfully, reboot and run it successfully again.

Code: Select all

$ cd
$ pwd
/home/fitzcarraldo
$ export WINEPREFIX=$HOME/.wine-winmd5sum
$ export WINEARCH=win32
$ winecfg
wine: created the configuration directory '/home/fitzcarraldo/.wine-winmd5sum'
fixme:system:SetProcessDPIAware stub!
fixme:iphlpapi:NotifyAddrChange (Handle 0x90fe914, overlapped 0x90fe918): stub
wine: configuration in '/home/fitzcarraldo/.wine-winmd5sum' has been updated.
fixme:mixer:ALSA_MixerInit No master control found on HD-Audio Generic, disabling mixer
$ cd .wine-winmd5sum/drive_c/
$ cp ~/Downloads/Install-winMd5Sum.exe .
$ # Now I'm going to install the 32-bit Windows application:
$ wine ./Install-winMd5Sum.exe
$ # It installed OK. Now I'm going to launch the application:
$ wine ./Program\ Files/winMd5Sum/winMd5Sum.exe

Reboot, and run the application again to prove it still works:

Code: Select all

$ cd
$ pwd
/home/fitzcarraldo
$ export WINEPREFIX=$HOME/.wine-winmd5sum
$ export WINEARCH=win32
$ wine .wine-winmd5sum/drive_c/Program\ Files/winMd5Sum/winMd5Sum.exe

[Otomo]

Thank you very much for all the info. Yes I know about wineprefix. I proceeded to erase my .wine-lotro wine prefix, and I reinstalled it again using export WINEARCH=win32.

For launching this game I use PyLotro (http://www.lotrolinux.com/download.php), so to being sure of using export WINEARCH=win32 when the game is executed, I launch Pylotro from bash after using this command too, but I don't know if it is enought, because the game still refuse to run

[Fitzcarraldo]

If you used the export command in the same terminal window before launching your script then I would expect the environment variable WINEARCH to be known by that script.

It's difficult for me to advise you further because I don't play the game myself and had never heard of pylotro. I wonder if it would be worth you trying to install pylotro using the Portage ebuild given in Gentoo Bugzilla Bug Report No. 302337? Perhaps the ebuild would configure something that the script you downloaded yourself does not. To try and install it, you would need to use a Portage local overlay, as follows:

All the commands below must be done as root user (hence the hash prompt shown in the steps below). Open a Konsole/Terminal window and log in as the root user.

1. Synchronise with the Portage repositories those ebuilds on your PC that are in the Portage tree:

Code: Select all

# emerge --sync

2. Add the Sabayon overlay:

Code: Select all

# layman -a sabayon

If it is already added, synchronise with the Sabayon overlay repository those ebuilds on your PC that are in the Sabayon overlay:

Code: Select all

# layman -S

3. Edit /etc/make.conf and make sure it has the following lines in it at the end of the file:

Code: Select all

PORTDIR_OVERLAY="${PORTDIR_OVERLAY} /usr/local/portage/"
ACCEPT_LICENSE="*"

(Delete the line PORTDIR_OVERLAY="/usr/local/portage/" if already in the file.)

4. Set up the directories for the local overlay:

Code: Select all

# mkdir -p /usr/local/portage/games-rpg/pylotro/files

5. Stop Portage nagging about a missing name for your local overlay:

Code: Select all

# mkdir /usr/local/portage/profiles
# echo "local_overlay" > /usr/local/portage/profiles/repo_name

6. Go to Gentoo Bugzilla Bug Report No. 302337 and save the file pylotro-0.1.11.ebuild to your Desktop.

7. Copy the file into the correct directory (I see from the link you gave that the current version of pylotro is 0.1.14, so just rename the ebuild when you copy it):

Code: Select all

# cd /usr/local/portage/games-rpg/pylotro
# cp /home/fitzcarraldo/Desktop/pylotro-0.1.11.ebuild /usr/local/portage/games-rpg/pylotro/pylotro-0.1.14.ebuild

(Obviously replace "fitzcarraldo" with your user name.)

8. Generate the manifest:

Code: Select all

# ebuild pylotro-0.1.14.ebuild manifest

9. Merge (install) the package:

Code: Select all

# emerge -1v pylotro

10. Tell Entropy what you did via Portage:

Code: Select all

# equo rescue spmsync

I have not tried it myself, so do not know if it will install. But it's worth a shot. I don't know what pylotro is supposed to do, so you could try it with and without setting WINEARCH=win32 to see what happens.

If you still have no luck, another thing you could try is to install WINE with only win32 libraries, and then re-install the game to see if that works:

Code: Select all

# USE="-win64 win32" emerge -1v wine
# equo rescue spmsync

As you would have previously performed Step 1, the emerge command above would install version 1.3.11 of WINE, which is not yet in the Entropy repository. That in itself may help.

[Otomo]

As I suspected that Pylotro isn't the problem I test it using other python script that launches it in console with the same results. I will do further tests when a new 32 bit libs arrive or a new FGLRX driver. Also the next week I will keep on searching for solutions in different forums of Wine, Gentoo etc

If I found a solution I will post it here as soon as I get it. Thanks for all the help.

[Otomo]

I get more info thanks to this post http://ubuntuforums.org/archive/index.php/t-1477025.html. So I focused to Pulseaudio instead GPU drivers or 32bits compatibility libraries.

The problem was that pulseaudio had the Default Sink in Default or Amd HDMI audio (I don't remember, but I think the Default option try first the AMD option, due to it don't check the Phonon configuration yet), so I check the Internal Audio option and problem solved. Other applications don't have problem when pulseaudio switched automatically from on option to another but it seems here it caused the Segmentation Fault. Here it is a screenshot of that option in the PulseAudio device chooser applet:



UPDATE: This solution let me without sound in that game. It's curious that if I change that options again the game starts anyway unless I reboot the system.