WineHQ
Category: Main Games Online (MMORPG) Games Lord of the Rings Online Update 9, Against the Shadow

Lord of the Rings Online


**** OBSOLETE **** 

Lord of the rings online as of December 17th, 2012.

Application Details:

Version: Update 9, Against the Shadow
License: Free to use
URL: http://www.lotro.com/
Votes: Marked as obsolete
Latest Rating: Gold
Latest Wine Version Tested: 1.5.28

Maintainers: About Maintainership

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Nothing

What does not

Game

Workarounds

What was not tested

Everything due to crash

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

wine: Unhandled page fault on write access to 0x00000034 at address 0x6d3e62 (thread 0029)

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowArch Linux x86_64Apr 28 20131.5.28Yes Yes GoldBjörn Bidar 
ShowUbuntu 12.10 "Quantal" amd64 (+ variants like Kubuntu)Feb 26 20131.5.24Yes Yes GoldSteven Wilson 
ShowLinux Mint 14 "Nadia" x86_64Feb 09 20131.5.23Yes Yes GoldErik Wroblewski 
ShowUbuntu 11.10 "Oneiric" i386 (+ variants like Kubuntu)Jan 25 20131.5.21Yes Yes Goldan anonymous user 
ShowLinux Mint 14 "Nadia" x86_64Jan 10 20131.5.21Yes Yes SilverErik Wroblewski 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs

HowTo / Notes

Test Data

This page is now considered Outdated. Please move onto Update 12

Please add the following informations to the test:

-  GPU

-  driver name + version

-  kernel version

-  desktop environment if needed

distribution

Getting Started

If you need any basic help read first the manpage of wine (eg. man wine) or the Wine User Guide or Wine FAQ. If this don't helps please ad basic informations like distribution, distribution version (if exist) and wine version. Please add case relevant informations like GPU driver version  if needed.

Got error? Read this please

As of October 15th, 2012, with the release of Riders of Rohan, this game is broken on versions of wine prior 1.5.18 , resulting in this error:

wine: Unhandled page fault on write access to 0x00000034 at address 0x6d3fd2 (thread 0024)

If your distrubtion dosn't ship an actual wine version you need to build yourself.

For instructions on building wine, see below.  However, note that this is a quite advanced task.

These Binaries are outdated use with care:

UPDATE:  Prebuilt binaries for the following distributions can be downloaded from the links below.  Note that these are not packages (.deb, .rpm, etc.), see install instructions below.

To install, extract the archive some place, like /home/username/local/wine-1.5.15-lotro. Example:

mkdir -p ${HOME}/local/wine-1.5.15-lotro
cd ${HOME}/local/wine-1.5.15-lotro
tar xf path/wine-1.5.15-1-x86_64.pkg.tar.xz

Now, start pylotro and go to Tools --> Options, check "Advanced Options" and enter /home/username/local/wine-1.5.15-lotro/bin/wine in "Wine Binary" text box. Obviously, replace "username" with your own.

wine: Call from 0x7b83bcb2 to unimplemented function d3d11.dll.D3D11CreateDevice, aborting

 This bug has been found to affect lord of the rings online with wine version 1.5.20

 To get around it, go into winecfg add d3d11.dll to overrides and disable it through the edit option.

Game freezes after  selecting acharacter *

Currently GNU-TLS breaks the game if  enabled while building possible workarounds are:

  1. Build wine without GNU-TLS support.
  2. Remove the GNUTLS(32) package ((lib32-)gnutls or such).

*('*** Error in `lotroclient.exe': malloc(): memory corruption: 0xe1002160 ***' or such)

Standard LOTRO wine installation
Throughout this tutorial I’ll assume you know how to open a terminal and run commands (lines beginning with $, but don’t include the $). You should also check to see how much video memory you have. This will come in handy later. If unsure, don’t worry about it.


Before we get started

Note to 64 bit Gnome users*:

A new error may occur with the newer releases of 64 bit Gnome desktops (including Unity). The message is:
“64bit Error “p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory”

It occurs after logging in. The only known solution found so far is here:
http://askubuntu.com/questions/127848/wine-cant-find-gnome-keyring-pkcs11-so

I still had problems after applying this solution.
The solution I found was to try a non-Gnome desktop. Switching from unity to kde-standard worked for me.  You could also switch to the 32 bit version of Ubuntu or whichever distro you use.

Getting Started

First chose a folder for your prefix and do this:

$ export WINEPREFIX=<your PREFIX>

. Then install 'corefonts' with winetricks (without the ingame store won't work):

$ winetricks corefonts
Grab the LOTRO installer

Note: If you already have LOTRO installed somewhere you can copy the ‘Turbine/The Lord of the Rings Online’ directory into your ‘.wine/drive_c’ folder (Default location is ‘Program Files’). Then skip ahead to ‘Install missing splash screens’

Now use one the standard LOTRO installers.
You can grab either Low or High resolution installer.

Low resolution:
$ wget http://content.turbine.com/sites/clientdl/lotro/lotrostandard.exe

High resolution:
$ wget http://content.turbine.com/sites/clientdl/lotro/lotrohigh.exe

LOTRO installation (skip if you are ‘already installed’)

If you have the full installer you can start it directly using wine.
$ wine LOTROSetup.exe

If you are using the standard LOTRO installer you can start it by prefixing the wine command with ‘GC_DONT_GC=1’.

eg (highress installer=
lotrohigh.exe,standard installer=lotrostandard.exe)
$ GC_DONT_GC=1 $installer

Note: If the downloader freezes at some point just kill the process (ctrl+c in the terminal) and start the downloader again. If you don’t remove any files it should resume the download and continue.

During the installation be sure to uncheck ‘create desktop icon’,  ‘README’, the subscription, and the ‘Load Lord Of The Rings Online’ options ( Currently TurbineLauncher fails when trying to load it. We’ll be using the 3rd party client ‘Pylotro’ to load the game instead.)

Install missing splash screens

Without these you would normally see grey splash screen with white crosshatches during game load or when teleporting. Normally the TurbineLauncher would grab these. But since it doesn't work we have to download them ourselves.

These images need to be installed into “Turbine/The Lord of the Rings Online/raw/en/logo”.

First:

32bit prefix:
$ cd ${WINEPREFIX:-~/.wine}/dosdevices/c:/Program\ Files/Turbine/The\ Lord\ of\ the\ Rings\ Online/raw/en/logo

64bit prefix (NOTE: I recommed to install Lotro in an 32Bit Prefix, WINEARCH=win32)
$ cd ${WINEPREFIX:-~/.wine}/drive_c/Program\ Files\ \(x86\)/Turbine/The\ Lord\ of\ the\ Rings\ Online/raw/en/logo

Now download the splash screens (I have a script to simplify this)
Note: This script defaults to english if you omit the language. ‘fr’ and ‘de’ also available.

$ wget https://sites.google.com/site/leeslinuxblog/lotrosplashme.sh
$ bash lotrosplashme.sh en

Install pylotro

There’s three ways we can do this. One is installing using the source. The second  is the windows exe in wine. The third is installing via Ubuntu PPA if you use Ubuntu or via AUR if you use Arch. Preferably use the windows version as it has consistently less problems.

Install windows exe in Wine

Download the windows exe file:
$ wget http://www.mcgillsociety.org/PyLotRO/pylotro-setup.exe


Install from source

Make sure you have python2) and python2-pyqt4 installed.

Download the source: (pylotro website is no more)
$ wget  http://ppa.launchpad.net/ajackson-bcs/ppa/ubuntu/pool/main/p/pylotro/pylotro_0.1.15precise.tar.gz


Unzip source & cd to the directory:
$ unzip PyLotRO-0.1.15.zip;cd PyLotRO
Run setup.py.

Via sudo
$ sudo python setup.py install

Or if sudo won't work via su:
$ su -c “python setup.py install”



Install using Ubuntu PPA

$ sudo add-apt-repository ppa:ajackson-bcs/ppa
$ sudo apt-get update;sudo apt-get install -y pylotro

Configure PyLotRO to run LOTRO

(Can be done via wizard or manually)

Wizard: (may not work with 64bit. Use ‘manually’)
1. Click ‘Tools’
2. Click ‘Settings Wizard’.
3. Select ‘Lord of the Rings Online’ and click ‘Find Games’.
4. Select “C:\Program Files\Turbine\The Lord of the Rings Online”
5. Click Apply.

Manually:
1. Click ‘Tools’ on the menu bar.
2. Click ‘Options’.
3. Choose Game directory.
(32bit prefix: <$WINEPREFIX>/dosdevices/c:/Program Files/Turbine/The Lord of the Rings Online
64bit prefix: <$WINEPREFIX>/dosdevices/c:/Program Files (x86)/Turbine/The Lord of the Rings Online)
4. (optional) Enable ‘High-Res Graphics’.
5. Save the settings.

Pylotro should now fill right up with the Realm list, news, languages, etc.

Patch the game data

1. Click ‘Tools’ on menu bar.
2. Click ‘Patch’.
3. Click ‘Start’ (This can take a while).
4. When finished, click ‘Exit’.

Run LOTRO!

Select realm and login!

In the future simply load Pylotro to play the game :)

Notes

If the game ever gives you an error saying you don’t have the latest version of the client installed, simply run ‘Patch’ from the Tools menu in Pylotro

You may also get errors regarding your audio. This is normal. If you don't have sound, Go to ‘Options->Audio’ and select your 'Sound Playback' device. You can ignore the error's in the PyLotRO output window, or you can try configuring your sound in winecfg.

Fixes/Tweaks

At this point you should be able to sign in and play the game. But its normal for some performance issues to manifest here. Here are some tweaks/fixes you can try.

Set the correct video memory size in the Registry.

1. Open regedit:

2. Browse to  HKEY_CURRENT_USER/Software/Wine/Direct3D/
(if this key does not exist, see ‘Missing Direct3D registry branch’ below)

3. Edit or create a key called ‘VideoMemorySize’.
Set ‘VideoMemorySize’ to the amount of video memory you have (1gb == 1024).

Missing Direct3D registry branch:

1. Right click Wine key in HKEY_CURRENT_USER\Software\
2. Click New->key
3. Enter ‘Direct3D’
4. Right click the ‘Direct3D’ key
5. Click New->String Value
6. Type ‘VideoMemorySize’
7. Right click ‘VideoMemorySize’, then modify
8. Enter amount of video memory (1024 == 1gb)


Game Tweaks

Tweaking the game:

Setting the video memory size usually fixes most performance issues. However there is a list of things you can do to try to kick the performance up an extra notch. Of course these are just suggestions. They are all optional.

Disable desktop 3D effects

The 3D desktop features can cause some performance issues in the game. Logging out and changing your Desktop session, or disabling 3D desktop effects can greatly increase game performance.

Choose a ‘Graphics Quality’ in Options->Graphics

It’s common for the auto detection to misdetect the card since there is a wine api in the middle of everything. Select this manually to get the quality you want. (I chose ‘very high’ for my 1gb Nvidia card)

Increase ‘Texture Cache Size’ in Options->Adv. Graphics

You can increase this to improve the game performance by increasing the amount of system memory used for graphics resources. This can decrease load times and in turn increase game performance.

Enable ‘Triple Buffering’ in Options->Adv. Graphics

For video cards with extra memory you can use this setting to slightly increase rendering performance.

Disable ‘Player Mesh Combining’ in Options->Adv. Graphics

This feature not only uses up more system memory, but also video memory. Saving a little video memory can always help game performance.

Disable ‘Distant Imposters’ in Options->Adv. Graphics

This option simply allows trees and other objects to render over distant scenery. Can be disabled to increase game performance.

Enable OpenGL Render

Since December 2011 Lotro has an OpenGL Render you can use it bychanging "GraphicsCore" in "$WINEPREFIX/dosdevices/c:/users/$USER/My Documents/The Lord of the Rings Online/UserPreferences.ini" to "OpenGL".



Comments

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Possible 12.0.1 problem - Turbine Launcher hanging
by William Magill on Tuesday November 26th 2013, 18:57
There seems to be some issue with 12.0.1 which I don't believe it was present in the base 12.0 release. (I have just moved, so I was off-line for a bit at Launch.)

At any rate. PyLotRO patches and will launch the game with no problems.

However, trying to launch the game directly using the Turbine Launcher as I had been doing "almost works." The Launcher gets started and then hangs on "Downloading "EN Loading Screen 2".

Using CrossOver 13.0 -- which is a recent update (12 November) as well, so at the moment, I don't know which might be the problem. (I had been running the 13.0 beta with no problem, but this was the first run with the released version.)

The only indication of WINE version in the release notes is for Crossover 12.5 (13 August 2013) which was WINE 1.6
Description is wrong
by William Magill on Tuesday November 26th 2013, 18:43
The current version of LOTRO is -
Update 12: Helm's Deep

Released on 20 November 2013.
RE: Description is wrong
by Michael Davenport on Tuesday November 26th 2013, 18:46
We will probably want to submit a new version. This page is getting large.
Can't start the game
by abelthorne on Saturday October 26th 2013, 5:24
I created a new wineprefix, copied the game dir from a Windows install (downloaded through Steam) and installed PyLotRO Windows.

It seems that my problem is that I can't patch the game. When patching from PyLotRO after my first "installation", it downloads a few files, updates the patchclient.dll (from 3.0.0 to 3.0.1) and ends with the following error: "Failed to check data: E_FAIL(0x80004005)"
If I try again to patch, it doesn't download anything, just displays the same error.
When running TurbineLauncher, it seems to download the splash screens and then tries to update the game but is stuck at 55 % and displays an error "The request could not be sent". It then retries indefinitely with 60 seconds between each try. In Nautilus file manager, at the end of each try, I can see a file "client_surface.dat.jrnl" appearing and disappearing immediately.

When trying to login from PyLotRO, it triggers a 201 error, which seems to indicates that some files are missing.

Any idea?
RE: Can't start the game
by William Magill on Saturday October 26th 2013, 12:19
Don't use PyLotRO, although I haven't seen any problems with it...

The new Launcher -- which you download from steam, can be launched directly and it will do all of the patching.

On the Mac, the Steam install is in
~Library/Application Support/Steam/SteamApps/common/Lord of the rings Online/
(I don't have Steam installed under WINE.)

In a Wine Bottle, the Turbine Distribution has the file:
Program Files/Turbine/The Lord of the Rings Online/TurbineLauncher.exe

You can launch: "TurbineLauncher.exe" directly and skip PyLotRO.
RE: Can't start the game
by abelthorne on Saturday October 26th 2013, 12:26
Welll, that's what I tried (see description of my problem). It seems that it can't download some files as it gets stuck at 55 % ans continuously tries to continue with no luck (and error message about a failed request).
RE: Can't start the game
by William Magill on Saturday October 26th 2013, 12:28
Duh... re-reading your original message...
.... "known bug"

With the Turbine Launcher, when you hit the wall -- 55-70%; simply quit the launcher and try again. It will "start over" and verify it has patched the earlier "stuff" then start where it left-off with the update.

The PyLotRO problem (4005) is "server down." This can be a communications problem or that the patch server really is down.

support.turbine.com/ics/support/KBAnswer.asp?questionID=244&hitOffset=51+16+10
RE: Can't start the game
by abelthorne on Saturday October 26th 2013, 12:49
Mmm, ok. Will try to restart it until it works. But can it come from somewhere else I didn't check, i.e. having to open ports on my router or such (which I've never had to do but maybe this has changed)?
RE: Can't start the game
by William Magill on Saturday October 26th 2013, 13:18
No port changes that I am aware of...
Patching takes place via HTML - to patch.loro.com or moria.lotro.com

That is the only "quirk" I am aware of -- if you are running any "anti-malware" software, which gets into the data stream for ALL HTML requests.
It is deadly... if nothing else it causes time outs; which often manifest themselves as server unreachability.
RE: Can't start the game
by abelthorne on Sunday October 27th 2013, 8:13
I suspect the problem comes from somewhere else. Yesterday, I updated the game on Windows as I couldn't on Linux.

First, I noticed that the 55 % step didn't seem to download files but updating them or preparing them (took a few seconds). After this, the updater jumps to 88 % and starts to download thausends of files. It doesn't get to this point on Linux and I wonder if the problem is related to locked files or such that it can't update and stops.

Then: after updating the game, I copied the whole LotRO dir on Linux. When trying to start it, the launcher gets to the same point: "can't send request", stuck at 55 % and such. As the game is up to date, it obviously doesn't try to update anything, it's just stuck...
(When trying PyLotRO again, same error message about missing files.)

patch.lotro.com isn't down, I can ping it. For some reason, it seems that the Turbin Launcher with Wine can't access the server or it can't find a list of files to check if they're up to date. Could it come from a specific version of Wine (using 1.7.4) ?
RE: Can't start the game
by dimitris on Wednesday October 30th 2013, 12:48
if u are using wine 1.7.4 or 1.7.5 u need to patch it
see here
bugs.winehq.org/show_bug.cgi?id=34812
RE: Can't start the game
by abelthorne on Wednesday October 30th 2013, 15:53
Ok, problem solved.

I don't know how to patch Wine/use patched version but I tried to reinstall the game with PlayOnLinux so that I can select another Wine version and the game works fine with 1.6. Didn't even try PyLotRO, the Turbine Launcher patches and runs the game fine.
BSOD following 11.3 update
by William Magill on Friday August 30th 2013, 13:41
It has been noted that many users have been getting the Blue Sceren of Death (BSOD) immediately following login.

For those users, the "fix" has apparently been to switch to OpenGL in the UserPreferences.ini file.

I have no other details at this time.
Turbine Launcher now works "flawlessly"
by William Magill on Sunday August 4th 2013, 21:07
With CrossOver 12.5 RC 0 -- which contains "the shipped version of Wine 1.6" -- the Turbine launcher can be launched directly. (No PyLotRO necessary). It patches, and loads the news, then launches the game... all very nicely.

TurbineLauncher.exe -- buried down in the usual place...
RE: Turbine Launcher now works
by Chuck on Friday August 30th 2013, 13:07
i'm using native wine1.6 and the launcher just pauses forever downloading the splashscreens. is this normal? i could careless about downloading them all the time.
RE: Turbine Launcher now works
by Björn Bidar on Friday August 30th 2013, 13:14
Yes using the native launcher is a thing of luck, as I already said:
its a joke that both the blizzard and the turbine launcher use Qt but only the blizzard one works really without any issue.
RE: Turbine Launcher now works
by William Magill on Friday August 30th 2013, 13:37
The answer is simple...

Visit the file: .../The Lord of the Rings Online/DownloadFilesList.xml

Examine the pathnames... they are all written with backslashes -- "\"

Change them to forward slashes "/" and the problem goes away!
RE: Turbine Launcher now works
by William Magill on Friday August 30th 2013, 13:38
Note that this file is replaced at every "patch" (update).
RE: Turbine Launcher now works
by Chuck on Saturday November 16th 2013, 22:33
it's now trying to download visual c++ and install it, work around?
Url for "News"
by William Magill on Sunday August 4th 2013, 20:57
Has anyone picked up the URL for "News" since the Forums Update this week?
Reason for Out of Memory Crashes
by Björn Bidar on Friday August 2nd 2013, 19:52
As lotro posts:
fixme:toolhelp:Heap32ListFirst : stub
when starting maybe its the reasons why we get this?
RE: Reason for Out of Memory Crashes
by William Magill on Sunday August 4th 2013, 21:01
During the extended downtime of Valentines Day (14 February), Turbine installed extensive new monitor software on the servers. Subsequently they have apparently discovered MANY issues previously undetected to be causing many of what were assumed to be memory leaks.
"The problems are not what they appear to be."

Supposedly 11.3 will have a great many fixes to the Game Engine to correct these issues.

I expect 11.3 to hit Bullroarer either late next week (8-10 August) or the following week.

Keep your fingers crossed.
New Depency
by Björn Bidar on Sunday July 28th 2013, 14:32
I found why the store won't works: it needs corefonts as depency or the browser window will stay white. I updated the guide about this.
RE: New Depency
by Björn Bidar on Sunday July 28th 2013, 17:00
After I done this it worked for a few but now I get the same result as before...
Update 11.2 issues
by William Magill on Thursday July 25th 2013, 19:10
Anyone having issues with Yesterday's patch - 11.2 - (Wednesday 24 July).
There were significant changes to the Launcher.

However, there is nothing "noteworthy" in the Release notes.

The Mac Client (which has been the test bed for this new launcher) has worked fine for me so far since the patch.

However, trying to run via Crossover and PyLotRO is "interesting." I have just begun to investigate, so this is only a partial report.


PyLotRO "patches" as one would expect ... up to a point.
It ends with the following dialog:
======
Self patch required. Program will restart.

Connecting to patch.lotro.com:80

Checking files...
files to patch: 1 bytes to download: 0
Patching files:

Downloading patchclient.dllFile in use. It will be self patched.

Self patch required. Program will restart.

*** Finished ***
======
The above is "normal" and routine. What happens next is not.

At this point PyLotro (itself still running) launches the "LOTRO Patcher" to do the rest of the patching...
which promptly complains (after downloading the 30 transition screens):

To run this application, you first must install one of the following versions of the .Net framework:
v2.0.50727
Contact your application publisher for instrunctions about obtaining the appropriate version of the .Net Framework.
===

Now, you cannot get "patch" to do anything more than respond: "*** Finished ***" - which is not surprising as the patchclient.dll has been modified... actually, in this case, it is deleted.
===========
Copying an old copy of the patchclient.dll in place allows a patch run to begin, which again launches the LOTRO client directly at the same place as above.
This time (unless I missed it before) after downloading the 30 transition screens the LOTRO client begins:

Downloading Microsoft Visual C++ 2005 Redistributable package (x86)...

which it apparently successfully installs.

One is then able to go through the login process and launch the game...

However, after selecting your server, you get the infamous "cannot patch."

At one point the LOTRO Launcher also attempted to install: Microsoft DirectX 9.0 2009.8 Redistributable.

So, a bit more experimentation is needed to find the missing parts.
RE: Update 11.2 issues
by Björn Bidar on Thursday July 25th 2013, 19:31
I have the same issue. But the launcer is a total joke, sometimes it runs some times it doesn't. How could two programs that use the same techniques run in the other opposites of quality. There's the blizzard launcher that runs fine and there's the Turbine Launcher which is total crap.
RE: Update 11.2 issues
by Björn Bidar on Thursday July 25th 2013, 19:44
If want to avoid the launcher we need to do something how we call the patchlient.
RE: Update 11.2 issues
by dimitris on Friday July 26th 2013, 5:17
sorry to hear pylotro has problem.

i am using sny's launcher for quite some time without problem.

here is the url.

bmx-chemnitz.de/~mfr/LOTRO/

all it needs is make sure that the game folder is same as in the script or modify it.

hope it helps.
RE: Update 11.2 issues
by Björn Bidar on Friday July 26th 2013, 9:29
the script use the same way to patch so it has the same issue
RE: Update 11.2 issues
by dimitris on Friday July 26th 2013, 9:48
it worked fine for installation.
RE: Update 11.2 issues
by dimitris on Friday July 26th 2013, 9:51
forgot to add my prefix was created with

winetricks win7 windowmanagerdecorated=n ddr=opengl videomemorysize=1024 corefonts
RE: Update 11.2 issues
by William Magill on Friday July 26th 2013, 8:03
A " brief" work-around.... DO IT OVER AGAIN! (and again - 3 times)

1- install a new "patchclient.dll"

2- Patch via PyLotro until "Finished"

3- Allow spawned launcher to run until it hangs.
(note that PyLotRO can be killed while the Turbine Launcher is running)

4- kill (x-off) the Turbine Launcher

5- launch PyLotRO again and Patch again

6- This time PyLotRO will patch to completion.

7- Use PyLotRO to login to game.
RE: Update 11.2 issues
by dimitris on Friday July 26th 2013, 9:23
all this for not putting correct path for the gameDir variable in sny's script ?


oldDir=`pwd`
gameDir=`/xxxxxx"$0"`
cd "$gameDir"
RE: Update 11.2 issues
by dimitris on Saturday July 27th 2013, 0:22
this is output from sny's script , in case u still think its not working

Welcome to the CLI launcher for LOTRO v1.0rc2.
(C) 2007-2011 by SNy

Reading launcher configuration...
--2013-07-27 08:12:46-- moria.gls.lotro.com/GLS.DataCenterServer/Service.asmx
Resolving moria.gls.lotro.com (moria.gls.lotro.com)... 74.201.102.12
Connecting to moria.gls.lotro.com (moria.gls.lotro.com)|74.201.102.12|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 9245 (9.0K) [text/xml]
Saving to: ‘.launcher/GLSDataCenter.config’

100%[================================================================================================================================================>] 9,245 --.-K/s in 0.1s

2013-07-27 08:12:47 (62.6 KB/s) - ‘.launcher/GLSDataCenter.config’ saved [9245/9245]

--2013-07-27 08:12:47-- gls.lotro.com/launcher/lotro/lotrolauncher.server.config.xml
Resolving gls.lotro.com (gls.lotro.com)... 74.201.102.12
Connecting to gls.lotro.com (gls.lotro.com)|74.201.102.12|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7265 (7.1K) [text/xml]
Saving to: ‘.launcher/launcher.config’

100%[================================================================================================================================================>] 7,265 --.-K/s in 0.1s

2013-07-27 08:12:47 (50.7 KB/s) - ‘.launcher/launcher.config’ saved [7265/7265]


Do you want to check for updates (y/N)? y
Checking for updates...
Connecting to patch.lotro.com:80
Checking files...files to patch: 1 bytes to download: 0
Patching files:
Downloading patchclient.dllFile in use. It will be self patched.

Self patch required. Program will restart.
Connecting to patch.lotro.com:80
checking data...data patches: 0 bytes to download: 0
unlock: 0 empty: 0
result code: 0x00000000
Patching data:

Data patching complete.
All patching complete.

Please enter your account details now.
account: xxxxxx
password:
Requesting GLS authentication ticket...
--2013-07-27 08:13:10-- gls-auth.lotro.com/GLS.AuthServer/Service.asmx
Resolving gls-auth.lotro.com (gls-auth.lotro.com)... 74.201.102.12
Connecting to gls-auth.lotro.com (gls-auth.lotro.com)|74.201.102.12|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2511 (2.5K) [text/xml]
Saving to: ‘.launcher/GLSAuthServer.config’

100%[================================================================================================================================================>] 2,511 --.-K/s in 0s

2013-07-27 08:13:11 (36.8 MB/s) - ‘.launcher/GLSAuthServer.config’ saved [2511/2511]

Logged in.

The following servers are available:
0: Meneldor
1: Crickhollow
2: Withywindle
3: Silverlode
4: Firefoot
5: Windfola
6: Gladden
7: Arkenstone
8: Riddermark
9: Dwarrowdelf
10: Vilya
11: Imladris
12: Elendilmir
13: Landroval [EN-RE]
14: Brandywine
15: Gwaihir [DE]
16: Nimrodel
17: Vanyar [DE]
18: Evernight
19: Eldar
20: Anduin [DE]
21: Sirannon [FR]
22: Maiar [DE]
23: Belegaer [DE-RP]
24: Laurelin [EN-RP]
25: Gilrain
26: Morthond [DE]
27: Estel [FR-RP]
28: Snowbourn
Your choice (enter the number on the left)? 16
--2013-07-27 08:13:21-- gls.lotro.com/GLS.DataCenterServer/StatusServer.aspx?s=10.68.84.56
Resolving gls.lotro.com (gls.lotro.com)... 74.201.102.12
Connecting to gls.lotro.com (gls.lotro.com)|74.201.102.12|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1156 (1.1K) [text/xml]
Saving to: ‘.launcher/server.config’

100%[================================================================================================================================================>] 1,156 --.-K/s in 0s

2013-07-27 08:13:21 (195 MB/s) - ‘.launcher/server.config’ saved [1156/1156]


Connecting to world login queue for realm Nimrodel...
--2013-07-27 08:13:21-- gls.lotro.com/GLS.AuthServer/LoginQueue.aspx
Resolving gls.lotro.com (gls.lotro.com)... 74.201.102.12
Connecting to gls.lotro.com (gls.lotro.com)|74.201.102.12|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 322 [text/xml]
Saving to: ‘.launcher/WorldQueue.config’

100%[================================================================================================================================================>] 322 --.-K/s in 0s

2013-07-27 08:13:22 (55.5 MB/s) - ‘.launcher/WorldQueue.config’ saved [322/322]

Ready. Now starting the client...
[ dim32@Saturn ~]$




$ ps -eaf
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 08:06 ? 00:00:02 /sbin/init
root 2 0 0 08:06 ? 00:00:00 [kthreadd]
root 3 2 0 08:06 ? 00:00:00 [ksoftirqd/0]
root 5 2 0 08:06 ? 00:00:00 [kworker/0:0H]
root 7 2 0 08:06 ? 00:00:00 [migration/0]
root 8 2 0 08:06 ? 00:00:00 [rcu_preempt]
root 9 2 0 08:06 ? 00:00:00 [rcu_bh]
root 10 2 0 08:06 ? 00:00:00 [rcu_sched]
root 11 2 0 08:06 ? 00:00:00 [watchdog/0]
root 12 2 0 08:06 ? 00:00:00 [watchdog/1]
root 13 2 0 08:06 ? 00:00:00 [migration/1]
root 14 2 0 08:06 ? 00:00:00 [ksoftirqd/1]
root 16 2 0 08:06 ? 00:00:00 [kworker/1:0H]
root 17 2 0 08:06 ? 00:00:00 [watchdog/2]
root 18 2 0 08:06 ? 00:00:00 [migration/2]
root 19 2 0 08:06 ? 00:00:00 [ksoftirqd/2]
root 21 2 0 08:06 ? 00:00:00 [kworker/2:0H]
root 22 2 0 08:06 ? 00:00:00 [watchdog/3]
root 23 2 0 08:06 ? 00:00:00 [migration/3]
root 24 2 0 08:06 ? 00:00:00 [ksoftirqd/3]
root 26 2 0 08:06 ? 00:00:00 [kworker/3:0H]
root 27 2 0 08:06 ? 00:00:00 [khelper]
root 28 2 0 08:06 ? 00:00:00 [kdevtmpfs]
root 29 2 0 08:06 ? 00:00:00 [netns]
root 30 2 0 08:06 ? 00:00:00 [writeback]
root 31 2 0 08:06 ? 00:00:00 [bioset]
root 32 2 0 08:06 ? 00:00:00 [kworker/u13:0]
root 33 2 0 08:06 ? 00:00:00 [kblockd]
root 34 2 0 08:06 ? 00:00:00 [md]
root 35 2 0 08:06 ? 00:00:00 [devfreq_wq]
root 36 2 0 08:06 ? 00:00:00 [kworker/2:1]
root 37 2 0 08:06 ? 00:00:00 [khungtaskd]
root 38 2 0 08:06 ? 00:00:00 [kswapd0]
root 39 2 0 08:06 ? 00:00:00 [ksmd]
root 40 2 0 08:06 ? 00:00:00 [khugepaged]
root 41 2 0 08:06 ? 00:00:00 [fsnotify_mark]
root 42 2 0 08:06 ? 00:00:00 [crypto]
root 55 2 0 08:06 ? 00:00:00 [kthrotld]
root 56 2 0 08:06 ? 00:00:00 [iscsi_eh]
root 57 2 0 08:06 ? 00:00:00 [kworker/0:1]
root 58 2 0 08:06 ? 00:00:00 [kworker/1:1]
root 59 2 0 08:06 ? 00:00:00 [kworker/3:1]
root 60 2 0 08:06 ? 00:00:00 [scsi_eh_0]
root 61 2 0 08:06 ? 00:00:00 [scsi_eh_1]
root 62 2 0 08:06 ? 00:00:00 [scsi_eh_2]
root 63 2 0 08:06 ? 00:00:00 [scsi_eh_3]
root 64 2 0 08:06 ? 00:00:00 [scsi_eh_4]
root 65 2 0 08:06 ? 00:00:00 [scsi_eh_5]
root 66 2 0 08:06 ? 00:00:00 [kworker/u12:1]
root 68 2 0 08:06 ? 00:00:00 [target_completi]
root 73 2 0 08:06 ? 00:00:00 [tmr-rd_mcp]
root 74 2 0 08:06 ? 00:00:00 [exec-osm]
root 75 2 0 08:06 ? 00:00:00 [dm_bufio_cache]
root 76 2 0 08:06 ? 00:00:00 [kworker/3:2]
root 77 2 0 08:06 ? 00:00:00 [deferwq]
root 78 2 0 08:06 ? 00:00:00 [kworker/u12:7]
root 79 2 0 08:06 ? 00:00:00 [charger_manager]
root 82 2 0 08:06 ? 00:00:00 [jbd2/sda3-8]
root 83 2 0 08:06 ? 00:00:00 [ext4-rsv-conver]
root 84 2 0 08:06 ? 00:00:00 [ext4-unrsv-conv]
root 95 1 0 08:06 ? 00:00:00 /usr/lib/systemd/systemd-journald
root 112 2 0 08:06 ? 00:00:00 [kworker/0:2]
root 115 2 0 08:06 ? 00:00:00 [kworker/1:2]
root 127 1 0 08:06 ? 00:00:00 /usr/lib/systemd/systemd-udevd
root 151 2 0 08:06 ? 00:00:00 [khubd]
root 155 2 0 08:06 ? 00:00:00 [ttm_swap]
root 160 2 0 08:06 ? 00:00:00 [kworker/2:2]
root 166 2 0 08:06 ? 00:00:00 [jbd2/sda2-8]
root 167 2 0 08:06 ? 00:00:00 [ext4-rsv-conver]
root 168 2 0 08:06 ? 00:00:00 [ext4-unrsv-conv]
root 172 2 0 08:06 ? 00:00:00 [scsi_eh_6]
root 173 2 0 08:06 ? 00:00:00 [usb-storage]
root 189 2 0 08:06 ? 00:00:00 [rc0]
root 201 1 0 08:06 ? 00:00:00 /usr/lib/systemd/systemd-logind
dbus 202 1 0 08:06 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
root 205 1 0 08:06 ? 00:00:00 /sbin/dhcpcd -q -b
root 209 1 0 08:06 tty1 00:00:00 /sbin/agetty --noclear tty1
root 210 1 0 08:06 ? 00:00:00 /usr/bin/kdm -nodaemon
ntp 214 1 0 08:06 ? 00:00:00 /usr/bin/ntpd -s
root 230 2 0 08:06 ? 00:00:00 [kworker/u13:2]
root 243 210 1 08:06 tty7 00:00:06 /usr/bin/X -br -novtswitch -quiet :0 vt7 -nolisten tcp -auth /var/run/xauth/A:0-nEEawa
root 277 2 0 08:06 ? 00:00:00 [kdvb-ca-1:0]
root 285 210 0 08:06 ? 00:00:00 -:0
root 287 1 0 08:06 ? 00:00:00 /usr/bin/ntpd -s
dim32 335 1 0 08:06 ? 00:00:00 /usr/lib/systemd/systemd --user
dim32 336 335 0 08:06 ? 00:00:00 (sd-pam)
dim32 337 285 0 08:06 ? 00:00:00 /bin/sh /usr/bin/startkde
dim32 346 1 0 08:06 ? 00:00:00 dbus-launch --sh-syntax --exit-with-session
dim32 347 1 0 08:06 ? 00:00:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
dim32 352 1 1 08:06 ? 00:00:05 /usr/bin/pulseaudio --start
rtkit 353 1 0 08:06 ? 00:00:00 /usr/lib/rtkit/rtkit-daemon
polkitd 358 1 0 08:06 ? 00:00:00 /usr/lib/polkit-1/polkitd --no-debug
dim32 392 1 0 08:06 ? 00:00:00 /usr/bin/gpg-agent -s --daemon --pinentry-program /usr/bin/pinentry-qt4 --write-env-file
dim32 395 1 0 08:06 ? 00:00:00 /usr/bin/ssh-agent -s
root 409 1 0 08:06 ? 00:00:00 /usr/lib/kde4/libexec/start_kdeinit +kcminit_startup
dim32 410 1 0 08:06 ? 00:00:00 kdeinit4: kdeinit4 Running...
dim32 411 410 0 08:06 ? 00:00:00 kdeinit4: klauncher [kdeinit] --fd=9
dim32 413 1 0 08:06 ? 00:00:00 kdeinit4: kded4 [kdeinit]
dim32 424 1 0 08:06 ? 00:00:00 kdeinit4: kglobalaccel [kdeinit]
dim32 428 1 0 08:06 ? 00:00:00 /usr/bin/kactivitymanagerd
root 429 1 0 08:06 ? 00:00:00 /usr/lib/upower/upowerd
dim32 430 337 0 08:06 ? 00:00:00 kwrapper4 ksmserver
dim32 431 410 0 08:06 ? 00:00:00 kdeinit4: ksmserver [kdeinit]
root 493 1 0 08:07 ? 00:00:00 /usr/lib/udisks2/udisksd --no-debug
dim32 500 1 0 08:07 ? 00:00:00 /usr/bin/knotify4
dim32 531 431 1 08:07 ? 00:00:07 kwin -session 10c5cf7475000137482405100000005560000_1374872113_1408
dim32 541 1 1 08:07 ? 00:00:05 kdeinit4: plasma-desktop [kdeinit]
dim32 545 541 0 08:07 ? 00:00:00 ksysguardd
dim32 569 1 0 08:07 ? 00:00:00 /usr/bin/kuiserver
dim32 571 1 0 08:07 ? 00:00:00 /usr/bin/akonadi_control
dim32 573 571 0 08:07 ? 00:00:00 akonadiserver
dim32 575 573 0 08:07 ? 00:00:00 /usr/bin/mysqld --defaults-file=/home/dim32/.local/share/akonadi/mysql.conf --datadir=/home/dim32/.local/share/akonadi/db_data/ --socket=/
dim32 599 1 0 08:07 ? 00:00:00 kdeinit4: krunner [kdeinit]
dim32 616 1 0 08:07 ? 00:00:00 kdeinit4: kmix [kdeinit] -session 10c5cf7475000137482406200000
dim32 619 1 0 08:07 ? 00:00:00 /usr/bin/nepomukcontroller -session 10c5cf7475000137482406200000005560030_1374872112_987793
dim32 635 1 0 08:07 ? 00:00:00 /usr/bin/korgac --icon korgac
dim32 640 1 0 08:07 ? 00:00:00 /usr/lib/kde4/libexec/polkit-kde-authentication-agent-1
dim32 641 1 0 08:07 ? 00:00:00 kdeinit4: klipper [kdeinit]
dim32 682 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_akonotes_resource akonadi_akonotes_resource_0
dim32 683 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_akonotes_resource akonadi_akonotes_resource_1
dim32 684 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_akonotes_resource akonadi_akonotes_resource_2
dim32 685 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_akonotes_resource akonadi_akonotes_resource_3
dim32 686 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_akonotes_resource akonadi_akonotes_resource_4
dim32 687 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_archivemail_agent --identifier akonadi_archivemail_agent
dim32 688 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_0
dim32 689 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_1
dim32 690 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_2
dim32 693 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_3
dim32 696 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_ical_resource akonadi_ical_resource_0
dim32 697 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_ical_resource akonadi_ical_resource_1
dim32 700 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_ical_resource akonadi_ical_resource_2
dim32 701 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_ical_resource akonadi_ical_resource_3
dim32 704 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_ical_resource akonadi_ical_resource_4
dim32 707 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_maildir_resource akonadi_maildir_resource_0
dim32 708 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_agent_launcher akonadi_maildir_resource akonadi_maildir_resource_1
dim32 709 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agent
dim32 722 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_mailfilter_agent --identifier akonadi_mailfilter_agent
dim32 751 571 0 08:07 ? 00:00:00 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder
dim32 798 410 1 08:11 ? 00:00:03 /usr/lib/chromium/chromium
dim32 800 798 0 08:11 ? 00:00:00 /usr/lib/chromium/chromium
dim32 801 798 0 08:11 ? 00:00:00 /usr/lib/chromium/chromium-sandbox /usr/lib/chromium/chromium --type=zygote
dim32 802 801 0 08:11 ? 00:00:00 /usr/lib/chromium/chromium --type=zygote
dim32 808 802 0 08:11 ? 00:00:00 /usr/lib/chromium/nacl_helper_bootstrap /usr/lib/chromium/nacl_helper --reserved_at_zero=0x0000000040000000 --r_debug=0x0000000040000000
dim32 809 802 0 08:11 ? 00:00:00 /usr/lib/chromium/chromium --type=zygote
dim32 844 1 0 08:11 ? 00:00:00 /usr/lib/uim/uim-helper-server
dim32 854 809 0 08:11 ? 00:00:01 /usr/lib/chromium/chromium --type=renderer --lang=en-US --force-fieldtrials=ForceCompositingMode/disable/InfiniteCache/No/Prefetch/Content
dim32 918 809 0 08:11 ? 00:00:02 /usr/lib/chromium/chromium --type=renderer --lang=en-US --force-fieldtrials=ForceCompositingMode/disable/InfiniteCache/No/Prefetch/Content
dim32 977 1 0 08:12 ? 00:00:01 kdeinit4: konsole [kdeinit]
dim32 979 977 0 08:12 pts/1 00:00:00 /bin/bash
dim32 1150 1 26 08:13 pts/1 00:00:36 lotroclient.exe -a 2CKYF39WZQAHHNWC9NLDCQPEK -h 74.201.107.56:9004 --glsticketdirect 7BpqIoM/UpU/GEDGX1N7noGgP/Ukhen/XDwJX4886FW4Ug9GK9kYD
dim32 1153 1 5 08:13 ? 00:00:07 /usr/local/bin/wineserver
dim32 1159 1 0 08:13 ? 00:00:00 C:\windows\system32\services.exe
dim32 1163 1 0 08:13 ? 00:00:00 C:\windows\system32\winedevice.exe MountMgr
dim32 1171 1 0 08:13 ? 00:00:00 C:\windows\system32\plugplay.exe
dim32 1178 1 0 08:13 ? 00:00:00 C:\windows\system32\explorer.exe /desktop
dim32 1208 410 2 08:14 ? 00:00:02 kdeinit4: kate [kdeinit] -b
root 1226 2 0 08:15 ? 00:00:00 [kworker/1:0]
dim32 1229 979 0 08:15 pts/1 00:00:00 ps -eaf
[ dim32@Saturn ~]$ [8:62:571681:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 12167
PyLOTRO patch for Python 2.7+
by JK Wood on Monday July 1st 2013, 20:51
I've created a patch that allows you to continue using native PyLOTRO to run LOTRO. You can find it at slackbuilds.org/slackbuilds/14.0/games/PyLotRO/HTTPSConnectionFix.patch
LotRO + Wine - DirectX Issue
by Najam Ansari on Monday June 17th 2013, 12:09
Hello everyone!

I am trying to run LotRO on Fedora 18. My version of Wine is 1.5.31. When I try to run the game using PyLotro (either native or in wine) I get the following error:

"The game encountered a fatal DirectX issue while attempting to start. Try a different screen resolution or bit depth. If that doesn't work, try new video drivers.[128]"

I must confess that I am using built-in Intel HD Graphics although I have been told that should not be the problem.

Stuff I have tried:

- Changing the screen resolution in Wine configuration (from 1366x768 to 1024x768)
- Reducing the bit depth (from 96 to 72)
- Updating my drivers

Any help would be greatly appreciated. I'm setting up LotRO in preparation for the Online Games course at Coursera
RE: LotRO + Wine - DirectX Issue
by Michael Davenport on Tuesday June 18th 2013, 11:55
Can you give us specifics on what graphics adapter you have?

There are several iterations of Intel HD graphics.
RE: LotRO + Wine - DirectX Issue
by Najam Ansari on Tuesday June 18th 2013, 12:38
Sure, it's from the Intel G41 Express Chipset line which has the Intel ® Graphics Media Accelerator X4500 Graphics Controller on board.
RE: LotRO + Wine - DirectX Issue
by Don Koch on Tuesday June 18th 2013, 19:15
I don't think the Intel chip has a depth of 96. In any case, try setting it to 32 or 24 bit depth.
RE: LotRO + Wine - DirectX Issue
by dimitris on Friday June 21st 2013, 13:04
have u got S3 Texture Compression library for Mesa ?
with the radeon driver is needed and probaply is needed for intel.
so package should be something like libtxc_dxtn or lib32-libtxc_dxtn
RE: LotRO + Wine - DirectX Issue
by Najam Ansari on Friday June 21st 2013, 13:22
I don't think I have either of these. I tried looking for both of them using

sudo whereis libtxc_dxtn
sudo whereis lib32-libtxc_dxtn

while at the root prompt.
RE: LotRO + Wine - DirectX Issue
by dimitris on Friday June 21st 2013, 13:40
i haven't used fedora for some time but i think this link will help
rpmfind.net/linux/rpm2html/search.php?query=libtxc_dxtn
RE: LotRO + Wine - DirectX Issue
by Najam Ansari on Saturday June 22nd 2013, 15:57
So I finally managed to get to the root of the problem: Overlapping x86 and x64 drivers! Fedora had (probably) installed some x64 drivers when I set it up on my system and while configuring wine, I installed the x86 ones.

I removed both x86 and x64 drivers video drivers and then installed only x86 ones. That seems to have solved the earlier issue.

BUT! Now I get Game Error 129:

"Hardware texture compression support was not detected. This video card feature is required to run the game."

I am not sure what the capabilities of the Intel G41 Graphics Chipset are but I am certain that they should be sufficient (considering the minimum required is a 64MB NVIDIA Geforce 3 Ref: support.turbine.com/ics/support/kbanswer.asp?deptID=24001&task=knowledge&questionID=434)
RE: LotRO + Wine - DirectX Issue
by dimitris on Sunday June 23rd 2013, 1:20
did u install the 32-bit of libtxc_dxtn ? rpmfind.net//linux/RPM/rpmfusion/free/fedora/18/i386/libtxc_dxtn-1.0.0-2.fc17.i686.html

what is the output of
glxinfo |grep -i s3
RE: LotRO + Wine - DirectX Issue
by Najam Ansari on Sunday June 23rd 2013, 14:09
Yessir I did!

After that, I looked up the error shown in the Pylotro console and tried figuring out how to solve it. Based on what I read (on a lot of different forums), I tried reinstalling my drivers. Now I seem to have messed up things even more and glxinfo is not working.

glxinfo returns:$ glxinfo
name of display: :0.0
Error: couldn't find RGB GLX visual or fbconfig
Error: couldn't find RGB GLX visual or fbconfig

glxgears returns:$ glxgears
Error: couldn't get an RGB, Double-buffered visual

Which is weird, because in my Xorg.0.log I can see that everything is loading up correctly (pretty much). I have put it up here: pastebin.com/d1RtLTVi
RE: LotRO + Wine - DirectX Issue
by dimitris on Sunday June 23rd 2013, 16:08
[ 18.028] (II) LoadModule: "intel"
[ 18.028] (WW) Warning, couldn't open module intel
[ 18.028] (II) UnloadModule: "intel"
[ 18.028] (II) Unloading intel
[ 18.028] (EE) Failed to load module "intel" (module does not exist, 0)
[ 18.029] (II) LoadModule: "vesa"
[ 18.029] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 18.029] (II) Module vesa: vendor="X.Org Foundation"
[ 18.029] compiled for 1.12.99.902, module version = 2.3.2
[ 18.029] Module class: X.Org Video Driver
[ 18.029] ABI class: X.Org Video Driver, version 13.0

thats from your logs.

perhaps this will help.

ask.fedoraproject.org/question/24736/how-to-install-intel-linux-graphics-drivers-using-the-official-installer/
LotRO, Wine and Play on Linux
by Erik Wroblewski on Friday June 14th 2013, 22:17
Hello guys. Yesterday, I had formated my PC, wiping it clean of its Windows 8 install, and installed an Ubuntu 13.04. After all the dist-upgrade things, was time to put Lotro to work.

My first trouble was about finding an “older” Wine version, like 1.5.28 and after it, the 64bit Error “p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/ gnome-keyring-pkcs11.so... bug. PyLotro gave me the error message and no fun, because Lotro Would not load.

Back to this forum, I was shocked to see that the documentation changed a bit but even more shocked to see that so many people was having trouble with Lotro. After some reading, I saw some people talking about Play on Linux and Lotro, and I just thought: why not give it a try?

Well, I confess I got surprised by the result, the game works flawlessly, no bug, glitch or error message, I played a lot and the game wont even suffer from minor lags. I know this is a “pure Wine” place, but for those who cant put Lotro to work with a pure Wine install, I wish to share how I done it (wont post it in the top because it is not a “only-Wine setting):

1 – Install Play on Linux from Ubuntu Repository;
2 – Install Wine 1.5.28 x86 in Play on Linux;
3 – Create e new Bottle with Wine 1.5.28;
4 – Install DirectX 9, MSCoreFonts and DotNET 3.5 in it;
5 – Configure the OpenAL32 Override for this Bottle;
6 – Configure your Video Memory Size;
7 – Install Lotro in this Bottle;
8 – Install PyLotro.exe in the same Bottle (I was unable to start the game by using the default game client);
9 – Configure the game path (Wizard/Find Games)
10 – Patch the game (leave it patching and go shopping or something like this, it will take a lot of time to patch it, I dont know why);
11 – Play the game.

I had set the render to OpenGL in game preferences file. The game performance is amazing, the only one thing that is still a problem is toggle from full screen to window: it will “crash” you GUI, but changing to a CLI window and back to GUI will fix it without crashing the game. Even the “in-game store” is working perfectly, and since I am not using a 64-bit Wine, no gnome-related bugs to bother me.

Obviously, anyone with some Wine knowledge could do all of it without Play on Linux, but since I am a newbie-rating Linux/Wine user, it was a lot easier to take this approach.

I could easily give a platinum rating to the game right now.

My PC: Dell XPS 8300, Intel i7 3.4 GHz, 8Gb RAM, Radeon HD 6450 1Gb. Ubuntu 13,04 64-bits, Linux Kernel 3.8.0-25-generic, ATI Catalyst Driver ver. 9.012 (Ubuntu reppo), OpenGL 4.2.12002.
RE: LotRO, Wine and Play on Linux
by Björn Bidar on Saturday June 15th 2013, 5:01
unneeded: Directx9, .NET 3.5, OpenAL32 override (especially if you use pulseaudio)
Problems with lotro Update 11
by William Magill on Wednesday May 29th 2013, 17:52
People need to realize that the LOTRO client, first with Update 10 and now with Update 11 has gotten worse! It has significant problems, not the least of which are simply patching and launching the client.

It is not at all clear what is happening currently at Turbine. "Blue names" have been strangely silent for the past couple of weeks. The "Update 11.0.1 Known Issues" post was taken down ... without any of them being fixed.

The Current LOTRO distribution (Update 11) uses the SAME launcher as was release with the Mac Client in July of 2012... and which still has ALL of the same bugs that were reported at that time -- none of them have been fixed. It was clearly a contract programming job with deliverables written by non-technical lawyers; and no one within Turbine is interested enough in the issues to fix them.

The issues with DX10 and DX11 are still broken -- it is recommended by Turbine support that you "drop back" to DX9 to resolve the problems. The forums imply that the "real problem" here is some recent bad update from Microsoft for certain graphics drivers, and recommends rolling back certain graphics driver updates. (No, I don't have any details.)

The "scheduled" update to Forums.lotro.com -- originally "announced" for "Mid-May," has been "delayed" until sometime in June... for unknown (but obvious) reasons. Turbine still has "back end" problems -- their recent "bonus points" sale has had people complaining constantly that they can't complete transactions -- you have to force an update of your billing (credit card) information) at myaccount.turbine.com so that PlaySpan gets the update. You can't create/change it via the store.

While it is possible that WINE has problems, I have not seen any evidence to that effect. I'm still running Crossover on the Mac -- Version 12.2.1 with no problems. CrossOver is now based on Wine 1.5.15. And I'm using the same old Windows version of PyLotRO.
RE: Problems with lotro Update 11
by Björn Bidar on Wednesday May 29th 2013, 17:55
Yes this was what I meant in long for.
PS: Please use follow the comment line.
RE: Problems with lotro Update 11
by Michael Davenport on Thursday May 30th 2013, 7:02
I'd like to mention that just because you are not experiencing issues, our latest posters are.

So I do have reason to believe we might be outdated as far as documentation goes.

Am I not making sense? If the people here have followed our documentation and have not been able to get the game running, then resort to playonlinux which does work. I think that's a problem.

On the other hand, turbine is creating what seems to be all of the problems.
RE: Problems with lotro Update 11
by Björn Bidar on Thursday May 30th 2013, 7:19
Only one person had gotten it running via Playonlinux and this person hadn't posted a report that is so that we could help him.
RE: Problems with lotro Update 11
by Michael Davenport on Thursday May 30th 2013, 7:46
And the rest have not been able to get it running.
New problems
by Michael Davenport on Wednesday May 29th 2013, 7:57
It's evident with all the new problems everyone is facing with the latest versions of wine and lotro, that our documentation is no longer entirely relevant.

When playonlinux is needed to actually play the game, although it apparently doesn't work in some cases, the documentation is clearly out of date.
RE: New problems
by Björn Bidar on Wednesday May 29th 2013, 8:11
There's no time where playonlinux is needed to play the game. The documentation is except some cases actual (dependencies and such).
The problem is the game brings more and more bugs in recent versions.
RE: New problems
by dimitris on Wednesday May 29th 2013, 9:49
playonlinux isn't needed..
curennly i am with
[ dim32@Saturn ~]$ wine --version
wine-1.5.31
and as i have posted in turbine's forums i have been using
mesa-git for quite some time
currently with
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD BARTS
OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.0 (git-cdad129)
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)

the main problem is the memory leak...
RE: New problems
by Björn Bidar on Wednesday May 29th 2013, 10:39
Its may a similar error like I posted in the Notes. But I think its related to your GPU driver. Do you sing Dx3d or OpenGL render?
RE: New problems
by dimitris on Wednesday May 29th 2013, 10:58
i am using the opengl render.
and as for prefix
export WINEPREFIX="$HOME/.lotro"
winetricks win7 windowmanagerdecorated=n ddr=opengl videomemorysize=1024 corefonts

for launcher i am using sny's launcher.
RE: New problems
by Björn Bidar on Wednesday May 29th 2013, 11:03
To you have gnutls installed or is your wine build with it?
RE: New problems
by dimitris on Wednesday May 29th 2013, 11:13
i made a new partition for 32-bit arch
gnutls for some strange reason works perfect while in 64 with multilib it doesn't.
RE: New problems
by Michael Davenport on Wednesday May 29th 2013, 12:11
I'm saying that because our documentation is outdated currently, people are resorting to trying playonlinux.
RE: New problems
by Björn Bidar on Wednesday May 29th 2013, 12:21
Than say me were is out of date? Beside that people try all the time using PlayonLinux cause they get a nice gui. I'm using my shell scripts as in this case it makes running win32 appliactions easyer and allows me to write a shell script for this in less then 5 lines.
RE: New problems
by Michael Davenport on Wednesday May 29th 2013, 16:04
That's great, but please tell me how many instances in the past 2 months have people not been able to get lotro running.
RE: New problems
by Björn Bidar on Wednesday May 29th 2013, 16:20
Many but most times it were bugs which I can't reproduce.
playonlinux 4.2.1
by Koray Ozcan on Wednesday May 29th 2013, 3:21
wine version: 1.5.28-TERA
Virtual drive : LOTRO x64
Virtual windows: winxp
İnstall Components: dxfullsetup, ie6, dx_36, pylotrosetup.exe

pylotrosetup.exe ( www.mcgillsociety.org/PyLotRO/pylotro-setup.exe )
RE: playonlinux 4.2.1
by Michael Davenport on Wednesday May 29th 2013, 7:36
What is this for?
RE: playonlinux 4.2.1
by Björn Bidar on Wednesday May 29th 2013, 7:40
Whats your problem? We don't support play on Linux, please use plain Wine if you want help.
RE: playonlinux 4.2.1
by Koray Ozcan on Thursday May 30th 2013, 6:02
lotrolauncher.script the game does not start. lotro works with PlayOnLinux
RE: playonlinux 4.2.1
by Björn Bidar on Thursday May 30th 2013, 7:22
What does it say? You need to be more detailed.
Whitg lotrolauncher.script you which launcher? Pylotro should start just fine what ever you use.
Game won't start
by Neal van Veen on Saturday May 18th 2013, 12:07
After the last update was released, the patcher failed at something and after several reinstalls (and subsequents patchings) the game won't start and the screen stays blank after logging in and launching in PyLOTRO. Anyone experiencing something similar?
RE: Game won't start
by Neal van Veen on Saturday May 18th 2013, 12:10
Forgot to add, I'm running Ubuntu 13.04 with Wine 1.5.30.
RE: Game won't start
by Michael Davenport on Wednesday May 29th 2013, 7:51
You're going to need to add what hardware you're running, and any proprietary drivers you are currently using.
New launcher... possible to run directly?
by steelsnake on Friday May 17th 2013, 20:19
Just curious, the new launcher seems to at least start up but then hangs at "Initializing". Any idea if it's possible to run this directly and ditch PyLotRO?
RE: New launcher... possible to run directly?
by Björn Bidar on Friday May 17th 2013, 20:21
try I again sometimes it works sometimes not.
RE: New launcher... possible to run directly?
by William Magill on Saturday May 18th 2013, 11:31
There are several answers.

First is -- Turbine still has patch-server problems. They acknowledge these in their Twitter Feed and in the login bulletin (back on 13 May), indicating that they would make an announcement when the problems were fixed. ... no announcement has been made. Which implies that they have not "fixed" anything, only that the problem "went away."

Frequently, one needs to simply quit the launcher and re-start it. I've had this happen with PyLotRO as well -- if you watch the patch process, you will see it hang while trying to contact the patch server.

Off the top of my head, I don't remember the other situations, but this seems to still be the issue based on Forum postings.
patchclient.dll is gone
by ReCon on Friday May 17th 2013, 4:08
Greetings everbody,

since the last bigger patch, also my patchlient.dll is gone. Actually for me it isn't possible to patch lotro anymore (pylotro cannot find the patchlient.dll). Due to the smaller update which was pushed into game yesterday (I guess?) I'm not able to play anymore due to version mismatch.

Does anybody else have this problem, too?

ReCon
RE: patchclient.dll is gone
by Björn Bidar on Friday May 17th 2013, 5:15
RE: patchclient.dll is gone
by ReCon on Friday May 17th 2013, 5:22
Awesome, thanks a lot, I will test it later.

I thought to myself, that something went wrong here ...
RE: patchclient.dll is gone
by William Magill on Friday May 17th 2013, 10:07
There is a copy sitting at:

www.mcgillsociety.org/PyLotRO/index.html
Heavy problems
by ReCon on Wednesday May 15th 2013, 1:02
Greetings everbody,

for me the game doesn't start with WINE Version higher than 1.5.28. It seems that this has something to do with the gnome-keyring problem as already mentioned from some other users in the comments section. I've also tried another desktop environment (like KDE) but this doesn't solve the problem for now ...

With 1.5.28 and lower (tested 1.5.28 and 1.5.25) the game does start, but I have no sound (tested on openSUSE 12.3 x64), even with winealsa and winepulse driver.

At least the game is working fine with the latest Crossover version from Codeweavers.
Does anybody else have such problems? Are there any solutions out there?

Thanks.
RE: Heavy problems
by ReCon on Wednesday May 15th 2013, 1:24
I have to add, that the sound with WINE versions >1.5.29 works at the intro and the Turbine logo at start up. In game I have no sound at all, even if the right sound device is choosen in the options of the game.
RE: Heavy problems
by Björn Bidar on Wednesday May 15th 2013, 6:48
Is your wine build with OpenAL, since Lotro uses OpenAL for every soundout except of the intro video which is bink video.
RE: Heavy problems
by ReCon on Wednesday May 15th 2013, 6:57
Yes, openAL is enabled so far. You haven't this issues?

A override or native DDL is needed here?!
RE: Heavy problems
by Björn Bidar on Wednesday May 15th 2013, 7:03
I'm using Arch Linux with wine-1.5.28 (1.5.29 is incompatible with rgl which I use to play wow, don't tested for version 1.5.30). Everything is fine.
RE: Heavy problems
by Steven Wilson on Monday May 20th 2013, 20:03
I switched from 1.5.30 to 1.5.28 and now pylotro crashes every time I run it! I was hoping your comment would help me get pylotro to work but it did not help.
The workaround for the game
by Koray Ozcan on Friday May 10th 2013, 2:01
install playonlinux

new virtual drive, wine 1.5.28, vcrun2005, vcrun2003, DxFull, Dx_36, pylotro-setup.exe(windows version)

pylotro open. select lotro wine folder. run the game.
RE: The workaround for the game
by Björn Bidar on Friday May 10th 2013, 2:05
all extra depends except pylotro are not needed.
RE: The workaround for the game
by Steven Wilson on Saturday May 11th 2013, 18:51
No matter which version of wine I use wine crashes when useing Playonlinux!
RE: The workaround for the game
by Steven Wilson on Sunday May 12th 2013, 9:18
I also tried deleting the VD and creating a 32 bit drive but lotrostandard.exe would not run. I trried opening a konsle via configure menu but got: Warning: Could not start program '/home/steve7233/.PlayOnLinux//tmp/env_bash2' with arguments '/home/steve7233/.PlayOnLinux//tmp/env_bash2'. Any one have any ideas?
RE: The workaround for the game
by MB on Thursday May 23rd 2013, 10:24
I got it working on Playonlinux with Ubuntu 12.10 64 bit (32-bit wine XP, 1.5.30), just following the build instructions.

Actually, a lot easier to get up than it used to be.
Gnome-keyring-pkcs11.so returns even worse than before
by Steven Wilson on Sunday May 5th 2013, 20:32
It seems that wine 1.5.29 has reintroduced the gnome-keyering-pkcs11.so bug! Now runing KDE dosn't stop the problem!

steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~$ WINEARCH=win32 WINEPREFIX=$HOME/LOTRO wine $HOME/LOTRO/drive_c/'Program Files'/PyLotRO/pylotro.exe
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:system:SetProcessDPIAware stub!
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files\\PyLotRO\\qt4_plugins\\imageformats\\qsvg4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
fixme:win:FlashWindowEx 0x32e5bc
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:imm:ImmReleaseContext (0x1007a, (nil)): stub
fixme:msvcrt:__clean_type_info_names_internal (0x1d1b01e4) stub
fixme:msvcrt:__clean_type_info_names_internal (0x3e4cbc) stub
fixme:msvcrt:__clean_type_info_names_internal (0x1009c770) stub
fixme:msvcrt:__clean_type_info_names_internal (0x33a694) stub
fixme:msvcrt:__clean_type_info_names_internal (0x1e8d7020) stub
fixme:msvcrt:__clean_type_info_names_internal (0x1e7ba8c4) stub
fixme:msvcrt:__clean_type_info_names_internal (0x1e1fc7f8) stub
steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~$

Kubuntu Raring Ringtail.
RE: Gnome-keyring-pkcs11.so returns even worse than before
by Michael Davenport on Friday May 10th 2013, 8:57
Can anyone else confirm this?
RE: Gnome-keyring-pkcs11.so returns even worse than before
by John on Friday May 10th 2013, 12:20
I can confirm. I have the same output.
RE: Gnome-keyring-pkcs11.so returns even worse than before
by Steven Wilson on Saturday May 11th 2013, 13:24
As soon as I see that Ubuntu has a package of the new wine 1.5.30, I will try that but as of this morning it appears they do not have one for Raring Ringtail yet.
RE: Gnome-keyring-pkcs11.so returns even worse than before
by Michael Davenport on Monday May 20th 2013, 19:29
This is a bug in wine, and unfortunately significant.
RE: Gnome-keyring-pkcs11.so returns even worse than before
by Michael Davenport on Monday May 20th 2013, 19:31
Try installing gnome-keyring, or reinstalling it.
Latest on new launcher
by William Magill on Friday May 3rd 2013, 23:14
Beta 3 for U10 has the following "feature" for the new launcher:

"The PC Qt launcher now supports Happy Cloud."
RE: Latest on new launcher
by Björn Bidar on Saturday May 4th 2013, 5:00
I hope they fix the memory leak if its not an issue of wine.
RE: Latest on new launcher
by William Magill on Saturday May 4th 2013, 21:26
The memory leak issue is simple -- both the LOTRO Client and Awesomium are 32-bit clients... attempting to address more than 4gb (or 3.7 under OSX) worth of memory.

The graphics enhancements and other changes made for Riders of Rohan are simply beyond the capabilities of a 32-bit client to handle.

The "fix" which Turbine constantly employs is to "dumb-down" the graphics. This is independent of any graphics settings you make in-game. The "most obvious" aspect of this "fix" is the number of "critters" who now "glide" across "the next land-block" instead of execute a walk animation.

The "fix" is accomplished on a "land-block" by "land-block" basis -- there is no change to the client made to clear those crashes which they have cleared.

The problem can still be triggered by simply opening and closing dialog boxes with NPCs or even simply opening and closing elements of your own UI.

It is interesting to note -- none of the issues raised with the "Mac Client" during Beta 2 for Riders of Rohan have been fixed in the QT Launcher released for Windows. Typical are the bogus error messages generated any time the Turbine Servers are down. "Internal error. Contact customer support." is my favorite -- generated any time the Patch server is down. These are again being raised during the Bullroarer beta, so we'll see if they are addressed. However, as with many contract programming jobs... this one suffers from deliverables written by lawyers, not technical people.
RE: Latest on new launcher
by Björn Bidar on Sunday May 5th 2013, 5:02
May be true but there's something wine related too since when I install gnutls lotro crashes nearly instant. see my bug report.
pylotro - Windows -fails to start LOTRO
by Steven Wilson on Tuesday April 30th 2013, 9:58
I am using KDE, so why the gnome-keyring- thing?

steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~/LOTRO/drive_c/Program Files (x86)/PyLotRO$ $HOME/LOTRO/drive_c/'Program Files (x86)'/PyLotRO/pylotro.exe
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
wine: Unhandled exception 0xc0000417 in thread 9 at address 0x200023:0x78b2af3e (thread 0009), starting debugger...
Process of pid=0008 has terminated
No process loaded, cannot execute 'echo Modules:'
Cannot get info on module while no process is loaded
No process loaded, cannot execute 'echo Threads:'
steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~/LOTRO/drive_c/Program Files (x86)/PyLotRO$ process tid prio (all id:s are in hex)
0000000e services.exe
0000001f 0
0000001e 0
00000019 0
00000018 0
00000016 0
00000014 0
00000010 0
0000000f 0
00000012 winedevice.exe
0000001d 0
0000001a 0
00000017 0
00000013 0
0000001b plugplay.exe
00000021 0
00000020 0
0000001c 0
00000022 explorer.exe
00000023 0
winedbg: Internal crash at 0x7ed2441a

wine 1.5.29 and just upgrade to Kubuntu Raring.
RE: pylotro - Windows -fails to start LOTRO
by Jan Schnackenberg on Tuesday April 30th 2013, 10:34
Did you by any chance change your UserPreferences.ini to "OpenGL"?

I did this, and couldn't start anymore. After changing back to D3D9 I could start again.
RE: pylotro - Windows -fails to start LOTRO
by Björn Bidar on Tuesday April 30th 2013, 10:59
Dou you had gnutls or when on a 64bit System, lib32-gnutls installed?
Or are you an AMD/ATI gpu user?
RE: pylotro - Windows -fails to start LOTRO
by Steven Wilson on Tuesday April 30th 2013, 14:53
I am trying a 32 bit LOTRO install. I just used pylotro (windows) to try to log in...
RE: pylotro - Windows -fails to start LOTRO
by Steven Wilson on Tuesday April 30th 2013, 15:50
Nope still the same error message.

64 bit kubunto Raring Ringtale just upgraded, and wine 1.5.29
RE: pylotro - Windows -fails to start LOTRO
by Steven Wilson on Tuesday April 30th 2013, 14:37
no
In Game Store
by Björn Bidar on Monday April 29th 2013, 14:43
As the other comments about the ingame browser are a bit old, how far is the progress in making the in game browser working? (for me it won't work, only a white window).
RE: In Game Store
by Jan Schnackenberg on Tuesday April 30th 2013, 10:36
I installed LotRO into a separate wine home, and I'm not sure what I might have done additionally to the setup-guide above. But the ingame-shop works without problems for me.

Only veeeeery slow, but that's not much better in Windows.
RE: In Game Store
by Björn Bidar on Wednesday May 1st 2013, 10:52
I made a new prefix but this doesn't solves it.
I get this messages when starting lotro and try to open the browser:
[41:64:541252660:ERROR:chrome_url_request_context.cc(94)] Cannot use V8 Proxy resolver in single process mode.

err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Programme\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Programme\\PyLotRO\\qt4_plugins\\imageformats\\qsvg4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Programme\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Programme\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
fixme:win:FlashWindowEx 0x33e58c
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
fixme:imm:ImmReleaseContext (0x1009c, (nil)): stub
fixme:imm:NotifyIME IMC_SETCANDIDATEPOS
fixme:win:FlashWindowEx 0x33a95c
err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded
err:ntdll:RtlpWaitForCriticalSection section 0x111cea14 "?" wait timed out in thread 0046, blocked by 111ceaa4, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x111cea14 "?" wait timed out in thread 002a, blocked by 111ceaa4, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x111cea14 "?" wait timed out in thread 0046, blocked by 111ceaa4, retrying (60 sec)
fixme:imm:NotifyIME IMC_SETCANDIDATEPOS
fixme:win:FlashWindowEx 0x338adc

[41:13:541259743:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 0

[41:13:541259752:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 12167

[41:13:541259764:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 12167

[41:13:541259779:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 12167
OpenGL Render
by Björn Bidar on Monday April 29th 2013, 14:00
Using the OpenGL render lotro freezes after the login screen with this:
err:ntdll:RtlpWaitForCriticalSection section 0xf26ea14 "?" wait timed out in thread 0030, blocked by f26eaa4, retrying (60 sec)
*** Error in `lotroclient.exe': malloc(): memory corruption: 0xe1002160 **

or with this:
err:ntdll:RtlpWaitForCriticalSection section 0xf2cea14 "?" wait timed out in thread 0046, blocked by f2ceaa4, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bcc6a80 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 002a, blocked by 0040, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bcc6a80 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0042, blocked by 0040, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bcc6a80 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0018, blocked by 0040, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bcc6a80 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0022, blocked by 0040, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bcc6a80 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 000c, blocked by 0040, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x7bcc6a80 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0021, blocked by 0040, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0xf2cea14 "?" wait timed out in thread 0046, blocked by f2ceaa4, retrying (60 sec)


Anyone got some workarounds or even detected the source of these errors? (using wine 1.5.28).
RE: OpenGL Render
by Björn Bidar on Monday April 29th 2013, 14:15
ok lib32-gnutls was the issue (don't know why), removed as workaround.
RE: OpenGL Render
by Björn Bidar on Monday April 29th 2013, 14:41
added workaround see app notes.
Blank window
by Spongeroberto Squarepantalones on Sunday April 28th 2013, 16:45
Running on:
* Mint 14 Mate Edition
* GPU: Nvidia Geforce GTX 650 (drivers: experimental 310.14)
* CPU: Intel i5 3570
* Wine: 1.5.29


Installation:
* Performed a full installation and update on a windows machine (high res version)
* Logged in on windows machine to test the installation
* Created new wineprefix in ~/.wine-lotro
* Installed vcrun2008 and d3dx9_42
* Copied my installation directory to ~/.wine-lotro/drive_c/Program Files (x86)/The Lord of the Rings Online


Running:
Running the game always ends up with a lotro application appearing in the taskbar. It doesn't show anything but the upper left corner of my screen is frozen there; it shows what was there before and nothing else. This happens with the CLI launcher, pylotro on linux and pylotro on windows via wine. The instance of lotroclient.exe doesn't use any resources after it's started.

Checking the console there doesn't appear to be any error message.

This approach worked fine last time I played the game on linux. Not sure why it failes now
RE: Blank window
by Spongeroberto Squarepantalones on Tuesday April 30th 2013, 15:05
Doing a rollback to wine 1.5.21 the game works perfectly.
RE: Blank window
by Björn Bidar on Tuesday April 30th 2013, 15:24
Always use a 32bit prefix if you don't run a 64 applications (WINEARCH=win32). I think this is the issue, if not one of the patches that are applied by your distribution is might be the issue.
FYI -- Update 11 going to Bullroarer
by William Magill on Sunday April 21st 2013, 20:03
Sapience has indicated that Update 11 will be heading to Bullroarer sometime next week (22-28 April 2013).... included are:

[QUOTE=Fredelas;6756084]The updated launcher is planned to release with Update 11. We will have more details next week when it becomes available for public testing on Bullroarer.

The main change to the launcher for Windows PC users is that it will no longer rely on the Microsoft .NET Framework 1.1. This framework can be problematic to install on newer versions of Windows, and mainstream support for it from Microsoft ended in October 2008.

You shouldn't have to take any special action to get the launcher to work. The launcher is already capable of updating itself and shouldn't require a reinstall of the game.

Edit: Here's a link to the post describing a few of the features of Update 11: [url]forums.lotro.com/showthread.php?507799-Update-11&p=6755068#post6755068[/url][/QUOTE]
RE: FYI -- Update 11 going to Bullroarer
by Björn Bidar on Sunday April 21st 2013, 23:14
So I hope we get the Qt Launcher like the OS X guys.
RE: FYI -- Update 11 going to Bullroarer
by Michael Davenport on Monday April 22nd 2013, 17:49
It might be built against a newer version of .net as well.
RE: FYI -- Update 11 going to Bullroarer
by Björn Bidar on Monday April 22nd 2013, 23:14
This would be a hell, but I see no reason using the Qt launcher for every plattform (like blizzard does) instead of having to clients.
RE: FYI -- Update 11 going to Bullroarer
by Michael Davenport on Monday April 22nd 2013, 23:27
They would have to remake most of the launcher, instead of just replacing deprecated functions. Obviously I want something more compatible with linux, but on the other hand, we're not a significant portion of their player base I imagine.
RE: FYI -- Update 11 going to Bullroarer
by Björn Bidar on Monday April 22nd 2013, 23:33
They already done this with the Qt Launcher. The reason that not many Linux users play lotro is that their client is horrible to use with wine. If they would provide a native client it should be better (just build the OS X client for Linux, as it shouldn't contain much plattform specific code).
RE: FYI -- Update 11 going to Bullroarer
by Michael Davenport on Tuesday April 23rd 2013, 10:50
Don't argue to me about it. I understand the logic, trust me.

I suggest you ask turbine.
RE: FYI -- Update 11 going to Bullroarer
by William Magill on Tuesday April 23rd 2013, 18:12
Keep in mind that the .net launcher has already been replaced by the Mac Client's launcher.

I don't know if that is what folks are referring to as the "QT launcher," by which I assume they mean Quick Time -- which to me is video/graphics platform, not a network communications platform.
RE: FYI -- Update 11 going to Bullroarer
by Björn Bidar on Tuesday April 23rd 2013, 18:16
With Qt Launcher is the launcher meant that is used for the OS X clienz.
The launcher is based on Qt and Qt is here just Qt not QuikTime.
RE: FYI -- Update 11 going to Bullroarer
by William Magill on Tuesday April 23rd 2013, 18:29
Aha, ok... being retired, I haven't kept up with such stuff :)

One thing to watch as this "new launcher" is installed... from my work with supporting the Mac Client, and CrossOver Games prior to that (which uses PyLotRO), it is quite clear that the .net issue has vexed Turbine support for several years. There have been numerous threads on the topic in the LOTRO support forums when Microsoft .net support was switched from .net 1 to .net 4 (3 years ago now?). The support forum folks were well aware of the constant problems they were having trying to work-around the .net1 issues. It looks like they finally got funding to actually fix the problem (i.e. replace it) rather than continue to simply "patch at it." ...

... we can only hope that the transition from a 32-bit to a 64-bit client won't be far behind.

The big stumbling block I see to that transition is Awesomium -- which is based on Chromium which only offered its first beta 64 bit version in the Fall of last year.
Pylotro Hangs
by Chris on Sunday April 21st 2013, 6:46
I am having problems with pylotro hanging on "Checking account details".
The application just stops and after a few minutes it responds with.

Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/PyLotROLauncher/MainWindow.py", line 295, in txtPasswordEnter
self.btnLoginClicked()
File "/usr/lib/python2.7/site-packages/PyLotROLauncher/MainWindow.py", line 289, in btnLoginClicked
self.AuthAccount();
File "/usr/lib/python2.7/site-packages/PyLotROLauncher/MainWindow.py", line 306, in AuthAccount
self.uiMain.txtPassword.text(), self.baseConfig.gameName, self.valHomeDir, self.osType)
File "/usr/lib/python2.7/site-packages/PyLotROLauncher/PyLotROUtils.py", line 533, in __init__
if webresp.status == 500:
AttributeError: 'NoneType' object has no attribute 'status'

Has anyone seen this before? Could an update have been applied to stop the login details being evaluated?
RE: Pylotro Hangs
by Michael Davenport on Monday April 22nd 2013, 14:19
You're going to need to specify which version of pylotro you're using.

Windows or the linux build?
RE: Pylotro Hangs
by Chris on Monday April 22nd 2013, 16:33
Sorry, I was using pylotro 0.1.15-3 (the build from the arch AUR).
I am using wine-1.5.28.

I also tried the lotro commandline launcher which had the exact same problem.
After days of attempting to get this to work I ended up install windows on dual boot, however I am interested if there is a fix, or something I have done wrong.
RE: Pylotro Hangs
by Michael Davenport on Monday April 22nd 2013, 17:43
Try using the windows version. It doesn't depend on dynamic libraries such as the linux version.
RE: Pylotro Hangs
by Chris on Tuesday April 23rd 2013, 3:10
Yes, I have tried pylotro from source, the AUR build, the windows exe, the command line launcher and the native turbine launcher (which didnt even load).
This was kinda the reason I dual booted windows, I kinda tried everything.

The same account that did not work on linux with ANY of these loaders worked on windows first time, so its not the username / password.
RE: Pylotro Hangs
by Michael Davenport on Tuesday April 23rd 2013, 10:44
I suggest trying a reinstall, and following our documentation exactly. If there is anything you have a question about during installation, please contact us.

On the other hand, if you have already done this, I will need you to post any information pylotro gives you on the windows build.
RE: Pylotro Hangs
by William Magill on Tuesday April 23rd 2013, 18:22
I believe this is a "communications problem."

The authentication process is "timed."

If the GLS response is delayed, both the Mac Client and Pylotro will "behave strangely."

One cause of this delay is any "virus scanner" (anti-malware) which is checking web site content.
For the Mac Client, "avast! free for Mac" has a sub-product called "Web Shield" which will cause this.

The solution is to either disable that product or cause it to bypass checks against: "patch.lotro.com," "moria.lotro.com" and "www.turbine.com/SE/GLS"

(All of the authentication work is done via html.)
RE: Pylotro Hangs
by Chris on Wednesday April 24th 2013, 3:07
I cant see that being the problem, at my end at least.
I am running arch linux and have no installed any firewalls or virus checkers.
Its not a problem external to the PC because windows worked on the same PC.
RE: Pylotro Hangs
by dimitris on Friday April 26th 2013, 4:27
try remove lib32-gnutls, there was a post on arch forums with wine and lib32-gnutls problem
Problems
by Steven Wilson on Saturday April 20th 2013, 19:33
Today I tried playing the game and noticed that the LOTRO store dose not work even after re logging the character!

wine 1.5.28 Kubuntu Ornic.
RE: Problems
by Michael Davenport on Tuesday April 23rd 2013, 10:46
The chromium based bug doesn't seem to be fixed yet, and it may be they changed their code so not even relogging in works anymore. This is a issue I can't help you on at the moment.
Significant Loading lag
by Erich Fischer on Saturday April 20th 2013, 0:11
I recently started playing again after being away for a couple months, and things run great except that when walking into different areas (going from 21st hall to Zelem-melek is consistently bad) or when large groups of mobs spawn at the same time (skirms in my case) there is noticeable lag, ranging from 5 up to even 30 seconds. I know this wasn't an issue before and I haven't changed any video settings in game.

Is this an issue anyone else has been having, and if so have you found a fix?

Additional Info:
Mint 13 (Ubuntu 12.04) 64-bit
wine 1.5.28 (tried older builds to no effect)
Ubuntu 12.04 32-bit chroot
NVidia GeForce GTX 460M
Keymaps not stored
by Basti G on Monday March 18th 2013, 8:48
Hi,

After some time away I wanted to check back on my old Lotro character.
Installing and patching went all smoothly but I encountered one issue:
Any changes that I'm applying to the keymaps are lost when I exit the game. This is particularly annoying for the quickslot shortcut keys. I don't want to spend the time to re-assign them for each session of Lotro.

I noticed that the lotro.keymap file gets updated everytime the game terminates, so it is probably not related to some unclean exit bug. I also tried removing the Lotro directory - it gets rebuilt with the default settings, and none of my keymaps.

The issue occurs on both 32bit and 64bit prefixes, in a separate X server and on :0, in windowed mode and in fullscreen.

I'm using a German keyboard, so '-' would need to be 'ß' (ssharp), etc. (remapping the keys in a custom layout does not work ... tried that already).

Does anyone have similar issues? I'm running out of ideas.

Thanks in advance
RE: Keymaps not stored
by Chuck on Monday March 18th 2013, 9:09
Does it always bug out for you on exit?
In the past, I've logged in and set my key map, then exited cleanly for it to save. Recently, I get errors on exit, but no crash (Ubuntu 12.10 64bit with high res install using opengl renderer).
RE: Keymaps not stored
by Basti G on Monday March 18th 2013, 10:57
Well as I said, it seems to exit cleanly. I also get PyLotRO display the famous "*** Finished ***" line, neither do the logs show any error.

All other settings, like graphics or audio also seem to be saved correctly.

I get the feeling that it has to do with the keyboard layout. In fact I discovered that I can change shortcut keys - only the two keys right of 0 (zero) seem to be problematic. These are "ß" and "'" (accent) and while every other key has a constant in lotro.keymap (e.g. DIK_LEFTARROW) both keys are stored as "" (quoted empty string)... I guess I'll need to take a look into a configuration file from Windows to see how it's done there.
RE: Keymaps not stored
by Basti G on Monday July 21st 2014, 4:09
In case others face the same issue: seems like using a non-UTF8 locale the game remembers my key mappings, at least for the ß character.
So in my case it's
LANG="de_DE" wine /TurbineLauncher.exe

by Steven Wilson on Sunday February 24th 2013, 13:47
Since pylotro for windows appears to be broken and I was unable to get Nir Flysher's work around to work then I decided to try to get the Turbine launcher to work. The main error that comes up when you launch the Turbine launcher seems to be No active X support. Is there a way to fake this in wine? Maybe something in winetricks?
RE:
by Michael Davenport on Monday February 25th 2013, 11:22
No, nothing will emulate Active X support. I would suggest following the documentation for installation.

Given the current situation I recommend deleting your wine directory, reverting any changes you've done to wineconfig and starting over. Lotro can be installed in 1.5.24 via the documentation.

There is a pylotro installer for the windows version already linked on the doc, which is the most recent released. Anything you find on the internet could be of a later release version and therefore you might be experiencing issues.

If you are still experiencing issues after following the doc, feel free to comment but please explain in detail what you have done, any debug messages you've received etc etc.
RE:
by William Magill on Monday February 25th 2013, 13:48
PyLotRO for windows STILL works with no issues.

The usual problem is that people pick-up old versions which do not work.

The current version is 0.1.15a -- sadly, the current version "About" box says 0.1.15"

A copy is available on my website: www.mcgillsociety.org/PyLotRO/index.html#PYLOTRO
or from Codweavers
www.codeweavers.com/compatibility/browse/name/?app_id=6292

Alan's website (lotrolinux.com) is no longer active.
RE:
by Steven Wilson on Monday February 25th 2013, 16:39
The documentation here links to pylotro for Linux. I found an old file that I had from last year that turned out to be pylotro for windows, I just checked on about and its version 0.1.15. Where can I get version 0.1.15a? I had been following the documentation to install so theoretically as soon as I get the correct version it should work again.
RE:
by Steven Wilson on Monday February 25th 2013, 17:27
I read over the documentation again and found that I had overlooked the link to the Windows version. When I ran pylotro for Windows it did not work! I ran in base and the patcher seemed to work but it still will not log in:

steve7233@steve7233-HP-Pavilion-dv6-Notebook- href="PC://home/steve7233$">home/steve7233$ wine .wine/drive_c/'Program Files (x86)'/PyLotRO/pylotro.exe
fixme:system:SetProcessDPIAware stub!
err:module:import_dll Library QtSvg4.dll (which is needed by L"Z:\\home\\steve7233\\.wine\\drive_c\\Program Files (x86)\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"Z:\\home\\steve7233\\.wine\\drive_c\\Program Files (x86)\\PyLotRO\\qt4_plugins\\imageformats\\qsvg4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"Z:\\home\\steve7233\\.wine\\drive_c\\Program Files (x86)\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"Z:\\home\\steve7233\\.wine\\drive_c\\Program Files (x86)\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
fixme:win:FlashWindowEx 0x32e5bc
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:imm:ImmReleaseContext (0x90138, (nil)): stub
fixme:win:FlashWindowEx 0x32c4dc
fixme:imm:NotifyIME IMC_SETCANDIDATEPOS
fixme:win:FlashWindowEx 0x32ae6c
fixme:imm:NotifyIME IMC_SETCANDIDATEPOS
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
fixme:win:FlashWindowEx 0x3275cc
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
fixme:imm:NotifyIME IMC_SETCANDIDATEPOS
fixme:win:FlashWindowEx 0x32a97c
fixme:msvcrt:__clean_type_info_names_internal (0x1d1b01e4) stub
fixme:msvcrt:__clean_type_info_names_internal (0x3e4cbc) stub
fixme:msvcrt:__clean_type_info_names_internal (0x1009c770) stub
fixme:msvcrt:__clean_type_info_names_internal (0x33a694) stub
fixme:msvcrt:__clean_type_info_names_internal (0x1e8d7020) stub
fixme:msvcrt:__clean_type_info_names_internal (0x1e7ba8c4) stub
fixme:msvcrt:__clean_type_info_names_internal (0x1e1fc7f8) stub
steve7233@steve7233-HP-Pavilion-dv6-Notebook- href="PC://home/steve7233$">home/steve7233$
RE:
by Steven Wilson on Monday February 25th 2013, 20:37
Opps typo base=bash
RE:
by Steven Wilson on Tuesday February 26th 2013, 1:55
Never mind. I discovered that I had installed using a WINEPREFIX and forgotten to use it on all my instillation instructions. The problem was part of the program was in one path and part in another path. Basically a Rockie Linux mistake, but since I have been using linux for severral years then I will just say that I was having a Homer Simpson moment. Lol

I deleted the mess and installed again and now the game works almost perfectly except for the game crash when I change to a bad resolution! I think that's on Turbine because pylotro still displays its window. I notice that the lotro store pylotro character log in bug seems to be gone!
Workaround HUD keys / ALT-TAB under Ubuntu 12.xx
by Nir Flysher on Saturday February 23rd 2013, 16:15
Finally I've mannaged to run Lotro properly.
The secret is using a second X Server.
By doing this one could switch between the regular X-server (ALT-CTRL-F7) and the Lotro X-server (ALT-CTRL-F8) without causing the game to crush or cause strange problems.
In addition any keyboard shortcut that can cause problems such as ALT / HUD key in the normal X-server won't be a problem at the new one.

In order to do so you can create shell file with :
cd ~/.wine/drive_c/Program Files/Turbine/The Lord of the Rings Online
xinit /usr/bin/ck-launch-session pylotro -- :1

The ' -- :1' will open a new X-Server.

One of the problems will be that you won't have any sound.
Apparently the ALSA cannot run more than one instance.
To Fix that edit /etc/group , find a line starts with
audio:x:29:pulse and add a comma with your username at the end.

For example : audio:x:29:pulse,username
(Credits go to : ubuntuforums.org/showthread.php?p=7404192)

Have a wonderful play,

Nir.
RE: Workaround HUD keys / ALT-TAB under Ubuntu 12.xx
by Björn Bidar on Saturday February 23rd 2013, 16:22
Don't edit user config files by hand use usermod or your favorite gui tool.
RE: Workaround HUD keys / ALT-TAB under Ubuntu 12.xx
by Steven Wilson on Saturday February 23rd 2013, 19:07
Without causing the game to crush? Do you mean crash? or is this some little used programming word?
RE: Workaround HUD keys / ALT-TAB under Ubuntu 12.xx
by Nir Flysher on Sunday February 24th 2013, 13:02
Yap, Sorry.
RE: Workaround HUD keys / ALT-TAB under Ubuntu 12.xx
by Steven Wilson on Saturday February 23rd 2013, 20:23
That does not work!

xinit /usr/bin/ck-launch-session pylotro -- :1

X: user not authorized to run the X server, aborting.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
RE: Workaround HUD keys / ALT-TAB under Ubuntu 12.xx
by Nir Flysher on Sunday February 24th 2013, 13:04
Try pressing ALT-CTRL-F5
Log in with your regular user, and then run it.
RE: Workaround HUD keys / ALT-TAB under Ubuntu 12.xx
by Steven Wilson on Sunday February 24th 2013, 19:38
Nope it says display 0 is already active.
RE: Workaround HUD keys / ALT-TAB under Ubuntu 12.xx
by Steven Wilson on Sunday February 24th 2013, 20:17
I found a couple of typos. It looks like it started and then shut down!
How do I keep it running?
RE: Workaround HUD keys / ALT-TAB under Ubuntu 12.xx
by Steven Wilson on Sunday February 24th 2013, 21:11
Is this for the Linux version of pylotro or the Windows version? I have the Windows version.
Steam announces Linux client for Ubuntu
by William Magill on Thursday February 14th 2013, 21:00
Steam announced the Linux client for Steam... apparently for "Ubuntu only."

"TRY LINUX
GRAB UBUNTU DESKTOP
Ubuntu is our favorite version of Linux. Interested in giving it a whirl? You can install and run Ubuntu from a Live CD or USB stick, or install it to run alongside Windows.

Grab an Ubuntu installer from Canonical and see what it’s all about."

Apparently supporting 57 games -- NOT including LOTRO, DDO or AC.
RE: Steam announces Linux client for Ubuntu
by William Magill on Thursday February 14th 2013, 21:01
RE: Steam announces Linux client for Ubuntu
by Björn Bidar on Thursday February 14th 2013, 21:02
It wotks on every distrubtion, Ubuntu is the only supported but Steam is willing too help other distributors.
RE: Steam announces Linux client for Ubuntu
by Michael Davenport on Friday February 15th 2013, 15:36
The beta was open to everyone since I believe November.

I'm currently on Fedora, and it works perfectly fine. They do eventually want to support other distributions, and are currently seeking the best way to do so.

I'm hoping that valve, indie developers, and even major gaming companies get a lot of money from the linux community. Maybe then Turbine will think about porting Lotro.

As far as games go, if there were Free software alternatives to my favourite proprietary games, I would be playing them instead.
Freeze when loosing focus
by Björn Bidar on Thursday February 7th 2013, 13:54
Has anyone the same issue that lotro freezes when its loosing focus?
(running in virtual desktop and d3dx9 as render).
RE: Freeze when loosing focus
by Björn Bidar on Thursday February 7th 2013, 14:03
Without virtual desktop the same issue:
err:ntdll:RtlpWaitForCriticalSection section 0x7bcc5960 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0009, blocked by 0039, retrying (60 sec)
RE: Freeze when loosing focus
by Michael Davenport on Saturday February 9th 2013, 18:53
You need to post what wine version you're using.
RE: Freeze when loosing focus
by Björn Bidar on Saturday February 9th 2013, 18:57
Oh forgot that latest dev version 1.5.23.
RE: Freeze when loosing focus
by Björn Bidar on Sunday March 3rd 2013, 7:48
Still an issue with wine 1.5.25 (using the windows version of pylotro, runned in virtual desktop).
Update 10 and WINE.
by William Magill on Sunday February 3rd 2013, 11:51
Recent (since Update 8 - RoR) updates and patches to LOTRO have incorporated many changes to the Game Engine and related mechanics.

In January, Turbine instituted new Pando downloaders at LOTRO.com, apparently baed on Java 7. I've been working with Pando to find out what the situation happens to be, and so far we have isolate one issue with the CDN (Content Deliver Network).

Currently, only the Steam download is working for the Mac Client.

As for the Windows Client, using CrossOver 12.1.1 (WINE 1.5.15) I'm having problems getting it to download. However, I've been working mainly on the Mac Download and at 18-30 hours per try, haven't done much with the PC download via WINE (I.e. CrossOver).

At the moment, I'm suspecting JAVA issues. The previously working version of the Pando Media Booster (PMB) was based on Java 6 and still works fine. The current version is apparently based on Java 7, and is problematic.... and just to complicate matters, I'm working from OSX 10.8.2 which dropped support for Java completely -- leaving it up to Oracle to provide a working Java environment on the Mac ... sigh.
RE: Update 10 and WINE.
by Björn Bidar on Sunday February 3rd 2013, 12:05
There's a native version for OS X. the OS X version has an advantage over the windows version beside that its native: it no longer uses the old .NET launcher and uses Qt if this version would uses for the windows version we would no longer need to maintain our launcher.
PyLotro (Linux) stuck at "Checking account details"
by Dif on Sunday February 3rd 2013, 7:44
I am having issues to log in to lotro with the Linux version of PyLotro (0.1.15).

Once I enter my password and I hit "Login", it stays stuck at "Checking account details..."

Running from a command line, after few seconds I get:
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/PyLotROLauncher/MainWindow.py", line 295, in txtPasswordEnter
self.btnLoginClicked()
File "/usr/lib64/python2.7/site-packages/PyLotROLauncher/MainWindow.py", line 289, in btnLoginClicked
self.AuthAccount();
File "/usr/lib64/python2.7/site-packages/PyLotROLauncher/MainWindow.py", line 306, in AuthAccount
self.uiMain.txtPassword.text(), self.baseConfig.gameName, self.valHomeDir, self.osType)
File "/usr/lib64/python2.7/site-packages/PyLotROLauncher/PyLotROUtils.py", line 532, in __init__
if webresp.status == 500:
AttributeError: 'NoneType' object has no attribute 'status'

I don't know if it is related, but the problem started after I got the following updates for my Gentoo box:
dev-libs/openssl-1.0.1c
sys-libs/pam-1.1.6-r1

For the time being I am doing fine with the Windows version of PyLotro, but it would be nice to get the Linux version back working.

Any idea?
RE: PyLotro (Linux) stuck at
by Michael Davenport on Sunday February 3rd 2013, 10:59
While I realize you would prefer the linux version, neither version is being maintained. The linux version requires dependencies that may not even be included in portage by default anymore.

I had the same problems a few months back with the linux version. I suggest just using the windows version which is still working perfectly fine.

In general, the code is deprecated.
RE: PyLotro (Linux) stuck at
by William Magill on Sunday February 3rd 2013, 11:40
1- The current version of PyLotRO is 0.1.15a -- sadly, the version information only shows 1.15 in the about box, and it is the Windows version.

I don't know that the Linux version was ever updated by whoever was maintaining it. I don't believe that Alan Jackson (the original author) was maintaining it. As far as I know, he dropped support for anything but the Compiled Windows version, several years ago.

2- Are you trying to run in a Language OTHER than English?
If so, you MUST first answer the EULA and TOS pop-ups in English BEFORE you can continue. (This might be fixed with Update 10, I haven't checked on Bullroarer.)

Select English BEFORE you enter your userid and password and click login.

Once you have answered the two pop-ups, you can switch back.

Note that Turbine has required that these two be "re-answered" with every update since Update 8.
RE: PyLotro (Linux) stuck at
by Dif on Sunday February 3rd 2013, 12:02
I am running LOTRO in English and since I was running the game until the evening before those 2 Gentoo upgrades (and there was no game update on that day), I don't think it is a problem with the EULAs - even further, PyLotro isn't even launching wine anymore, so indeed it's a PyLotro problem.

Maybe the linux version of PyLotro uses any of those 2 programs (I may guess OpenSSL for secure authentication) and maybe there was some api change on the upgrade that makes PyLotro fail.

Since, as Michael is mentioning, PyLotro is no longer maintained and the Windows version is still working, I am afraid that there is no reasons for downgrade OpenSSL to make it works. :-(

For the future I hopes that either someone is willing to resume the work on PyLotro or a new launcher arise. It is a matter of time for the the linux version to gradually fail on all distribution as they eventually upgrade the libraries PyLotro relys on and for the Windows version, even if it works for the moment we cannot rely on it indefinitely as being unmaintained it may be prone to failures if Turbine ever decide to do some change on the Lotro login procedure.

Thanks anyway for the answers.
RE: PyLotro (Linux) stuck at
by Björn Bidar on Sunday February 3rd 2013, 12:23
As I said in another comment above if we have luck the Windows version will get the Qt launcher from the OS X version, it would not be so unlikely cause the old .NET launcher needs .NET 1.x with is not supported under Windows 6.2 (marketing name 8).
RE: PyLotro (Linux) stuck at
by Björn Bidar on Sunday February 3rd 2013, 12:19
As I know the windows version is the same version as the current Linux version. There's a patch to fix the bug that fixed issues with login names or passwords with non ANSI characters. In long sight we need to port pylotro to python3.
RE: PyLotro (Linux) stuck at
by Michael Davenport on Sunday February 3rd 2013, 14:50
There is a 2to3 converter, though I'm unsure how well that will work given the fact that pylotro is dependent on third party libraries.

Personally, I would rather make a port to Vala instead of python3.x
RE: PyLotro (Linux) stuck at
by Björn Bidar on Sunday February 3rd 2013, 15:40
I tried this, there are several changes needed towards PyQt for example removing Qstring stuff.
in-game store problems
by William Magill on Wednesday January 23rd 2013, 20:15
It turns out you have to read between the lines, but here's the Turbine Knowledge Base explanation...

support.turbine.com/link/portal/24001/24001/Article/3808/What-is-the-AwesomiumProcess-exe-process-and-why-is-it-running-when-I-play

Basically, Firewall software needs to allow (exempt) "Awesomium" on the Mac or "AwesomiumProcess.exe" with the Windows (Linux) version.

"If you are using a third-party firewall (Zone Alarm, Kaspersky, Norton, AVG, etc.) the steps to add exceptions may be similar to those listed above. Please refer to the maker of your firewall for detailed instructions if needed."

The OSX Firewall (Mountain Lion 10.8.2) is found in "[B]System Preferences/Security & Privacy[/B]" click on the "[B]Firewall[/B]" tab.

[url]support.apple.com/kb/PH11309?viewlocale=en_US[/url] - Apple KP article on Firewall: OS X Mountain Lion: Prevent unwanted connections with a firewall - Article: PH11309
RE: in-game store problems
by William Magill on Wednesday January 23rd 2013, 20:19
OOps what I get for cutting and pasting -- ignore the last 2 paragraphs, unless you are running via CrossOver on a Mac.
command line launcher
by Chuck on Wednesday January 23rd 2013, 10:31
is there a command line way to launch lotro ?
gui is nice but honestly, all i use the gui for is to enter my password to get into the game.
also would need a command line way to patch.
RE: command line launcher
by William Magill on Wednesday January 23rd 2013, 15:00
I am not aware of one... the CLI version which PyLotRO is based on stopped working several years ago. I have no idea if it was fixed or not.

www.bmx-chemnitz.de/~mfr/LOTRO/

This does appear to be either based on or IS the original SNy version, I don't know.
It is not clear if that information is updated or not -- it appears to be dated 2008.
RE: command line launcher
by Marko Friedemann on Friday January 25th 2013, 13:38
The command line launcher is in perfect condition, I am not aware of any stoppage, apart from some problems now and then when Turbine changed stuff (ie: world queues).

You can get it from the link as usual. I might even upload the patch companion I made someday. :P

Hope that helps.
Changes to documentation
by Michael Davenport on Thursday January 10th 2013, 21:23
I think we should stick with just the pylotro that was built for windows, instead of having the other options.

The windows version should worked standard on all distributions. I've personally had problems with the native version since my qt was several versions higher than what it required.

Do we really want to subject users to native builds that could potentially not work on their distribution of choice?
RE: Changes to documentation
by Björn Bidar on Friday January 11th 2013, 0:14
I personally have no problem when using pylotro with the latest version qt (I'm using a rolling release distrubtion), which problems do you got?
Maybe they were specific to your distrubtion?
RE: Changes to documentation
by Erik Wroblewski on Friday January 11th 2013, 6:02
I never had any issue with PyLotro Linux version too. It allways workd fine, except when I tried it in Linux Mint 14 KDE, when it returned me a error message related to access permissions in the /usr/local/lib/python2.7/dist-packages/ folder.

Changing the permissions solved the problem, and PyLotro worked with no other issues.

But I must agree that istall it directly in Wine (.exe file) is a lot easier, specially for people who is starting to use Linux as main desktop.
RE: Changes to documentation
by Björn Bidar on Friday January 11th 2013, 6:04
>But I must agree that istall it directly in Wine (.exe file) is a lot >easier, specially for people who is starting to use Linux as main >desktop.
Its a bit easyer when you distrution don't have a package, as Arch User you can use the AUR link or as Ubuntu User the link to them PPA.
Fell free to add packages for other distrubtions.
RE: Changes to documentation
by Michael Davenport on Friday January 11th 2013, 8:17
I just think we should advertise pylotro for windows much more than the others. It's just to promote standardization. There could be a plethora of issues between all the distributed pylotro packages.

I was on gentoo so I installed via source, and that frankly didn't work because of an updated qt.
RE: Changes to documentation
by Björn Bidar on Friday January 11th 2013, 8:31
Than it was an issue of gentoo or your system. If we get issue cause distrubtions don't ship the needed python2, than I think we shoud do what you said, but current I don't see any issues.
RE: Changes to documentation
by William Magill on Wednesday January 23rd 2013, 7:43
Alan Jackson (author of PyLotRO) gave up attempting to create a "native Mac" version of PyLotRO "long ago" -- for exactly that reason: QT compatibility problems.

By creating the "windows version" he created a "static binary" which worked all the time, independent of WHICH version of Quick Time was being used by the parent OS. One simply loaded it into the bottle with LOTRO and away you went.
LOTRO runs extremely slow after 1.5.20 update
by jarrod bagwell on Monday December 31st 2012, 19:58
After the new update, my version of LOTRO runs horribly laggy and slow. I get frame rates of under 10fps and changing the graphics settings can't seem to do anything. I've tried editing the preferences.ini file, but that doesn't do anything either. I tried switching the graphics core to OpenGL, but the game threw an error saying it couldn't detect the specified graphics engine or something like that. Under wine 1.5.19, LOTRO ran fine for me in linux. This is most distressing.

My specs

Nvidia GTX 680 (2x)
Wine 1.5.20
Linux Mint 13 64bit
MATE desktop
RE: LOTRO runs extremely slow after 1.5.20 update
by jarrod bagwell on Monday December 31st 2012, 20:01
I forgot

Kernel 3.2.0-23
Nvidia Propietary driver 310 series
RE: LOTRO runs extremely slow after 1.5.20 update
by Michael Davenport on Tuesday January 1st 2013, 0:08
I don't use Nvidia cards personally, but are you using the latest driver?

If it's not that, it could be any number of issues. I'll see what I can gather.
RE: LOTRO runs extremely slow after 1.5.20 update
by William Magill on Wednesday January 23rd 2013, 15:16
This has been a "common" complaint about Update 8 (not about WINE per-se).

It appears that many of the problems somehow relate to a "clean" installation.

Variously, folks who have created new userids and re-installed LOTRO there have had zero problems while their original installations on the same computer are slug-slow. The threads I have read seem to have done the "obvious" things about cleaning out temp files and the like, but there is clearly some file which is NOT being cleared... or something.

I suppose that it could just as easily be the difference between working with a virgin prefs file compared to one which has been "tweaked" to certain user preferences. Other than the "usual suspects" here (i.e. ALL of the "fancy" graphics settings) I don't have a feel for what those "evil tweaks" might be.

I know that with the Native Mac Client, serious performance differences (FPS) can be seen by toggling several of those Graphics settings, and in particular "Specular lighting" ... but that's very "Mac Client centric" -- OpenGL vs DX9 (i.e. I don't see the same kind of impact when using CrossOver (WINE 1.5.15)

Of course, now we have to contend with Update 9.1 just released this morning... so, not only may your milage vary, but the make and model can make a big difference :)
RE: LOTRO runs extremely slow after 1.5.20 update
by Nick Ladis on Wednesday January 2nd 2013, 4:01
After a system update I had the same problem ( 2-5 fps ) and whatever I did had no effect. I even did a back up and deleted the contents of the entire home/user directory but the result was the same.
Finally I decided to check if this had to do with my user or it was system wide and therefore I created another user and transferred lotro there. Lotro worked normally there.

I deleted all files even in the tmp dir which had to do with wine and my main user and finally the problem was solved.
RE: LOTRO runs extremely slow after 1.5.20 update
by jarrod bagwell on Thursday January 3rd 2013, 23:19
Where exactly is the tmp directory that you deleted from? I found a .tmp under the file system but I don't see any files or folders referencing LOTRO.
RE: LOTRO runs extremely slow after 1.5.20 update
by Nick Ladis on Friday January 4th 2013, 1:43
In my system, which is OpenSUSE 12.1 & 12.2, it's in the main root directory: /tmp.
I've never used ubuntu but I doubt it has different arrangement in main directory than opensuse.

In there, logically you will find one or more hidden directories under the name .wine-1000, .wine-1001 or similar. Personally i deleted the one which had the same time-stamp with when my troubles started but even if you delete all .wine-xxx directories wine should make a new one.

Careful though. I have no knowledge of your linux expertise and I have to warn you:
Do not feel tidy and start deleting anything else in tmp unless you know what you are doing as it may cause you troubles with your environment.
RE: LOTRO runs extremely slow after 1.5.20 update
by jarrod bagwell on Sunday January 6th 2013, 22:35
Ok.. I found that wine was only creating that file after a run of LOTRO. Thing is, I only found one wine-100x file and that was after I ran it a few minutes ago. I tried deleting it and there was no change.
RE: LOTRO runs extremely slow after 1.5.20 update
by Nick Ladis on Wednesday January 9th 2013, 9:51
Sorry to hear that.
I've run out of suggestions I am afraid.
The only thing I can advice you right now is to check if by creating a new user and new bottle + ccpying the game there, you are able to play through this user normally. I did that too previously and verified that the problem was visible only to one user and not to entire system.
In Game Store
by Erik Wroblewski on Thursday December 27th 2012, 20:42
Whenever I log in LOTRO, the in game store shows a "balnk screen". But I had solved it by logging out my character (just the character, not logging out the game by choosing exit), and opening the store by character selection screen.

When I log in the character again, the LOTRO in game store will work normally until the next time I start the game client.
RE: In Game Store
by William Magill on Monday January 21st 2013, 11:05
This may or may not be relevant. A kinmate of mine reported in kin-chat a couple of days ago that they discovered a problem with Windows proxy settings impacting the Store.

" On Win 7: Control Panel -> Network and Internet -> Internet Options -> Connections tab -> LAN Settings button -> Automatically Detect Settings checked by default

Yay, looks like I found the cause of all my Store access issues. There's an internet option on by default to use automatic proxy detection that was blocking access. Weird"

They had been going to make a forum post about their findings, but so far, I haven't found it.

I don't know if such an "Automatic Proxy Settings" option exists in Linux or WINE or if turning it off will help... but it might be a clue.

One assumes that the Store uses the same ports as does the game. See:

www.mcgillsociety.org/PyLotRO/index.html#ROUTER
RE: In Game Store
by William Magill on Monday January 21st 2013, 11:09
I would add... when I play LOTRO via CrossOver (WINE 1.1.15), in the PyLotRO "Output" window at logout, I always see:

[43:64:5732643:ERROR:chrome_url_request_context.cc(94)] Cannot use V8 Proxy resolver in single process mode.

[43:23:5738041:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 0

[43:23:5738696:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 12167

[43:23:5739645:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 12167

[43:23:5739646:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 12167

[43:23:5739647:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 12167

*** Finished ***

However, during the game I have no problems with the Store.
RE: In Game Store
by Steven Wilson on Wednesday January 23rd 2013, 3:29
I get the same output from pylorto but when playing the game after loging out and back in my character the game works fine. The lotro store doesn’t work until I re log my character. pylotro appears to have a common bug that needs to be debugged so players don't have to do the character re log just to get the lotro store to display more than a black blank window. It's probably something to do with port i/o from and to the game server.
RE: In Game Store
by Michael Davenport on Wednesday January 23rd 2013, 6:52
The errors displayed in the output of pylotro have always been outputted.

I had the same errors in 1.5.18 but the store worked. It's an issue with the game or wine, as those have had changes in the code base.
RE: In Game Store
by William Magill on Wednesday January 23rd 2013, 7:39
I don't doubt that it is related to changes in the "Game Engine."

Riders of Rohan (Update 8), which broke all versions of WINE available at the time (i.e. prior to 1.5.18), DID contain major revisions in many areas of Game Technology.

Not the least of which was the fact that Update 8 REPLACED the use of an external Browser, with an imbedded in-game browser -- AWESOMIUM, which is based on CHROMIUM.

In fact, PyLotRO has NOT been updated now for several years (June of 2011 for v 1.15a). It had/has continued to function with no issues since then. The proxy messages began appearing with the Arrival of AWESOMIUM.
RE: In Game Store
by Michael Davenport on Wednesday January 23rd 2013, 11:22
The fact that pyLotro isn't being maintained is a bit troublesome. It's pure coincidence that it's still working.

We might want to look for other solutions to get lotro working, or find a python coder. I would do it myself but I'm a full time student trying to maintain a excellent gpa and I have work. It also doesn't help that I have never touched a bit of python code, so I'd have to learn the language first.
RE: In Game Store
by William Magill on Wednesday January 23rd 2013, 14:46
If I remember correctly from the last email exchange I had with the author of PyLotRO -- it's not that it isn't being maintained, but rather that he doesn't feel it needs any maintenance (issues of Real Life aside).

i.e. that is why he created the "Python package" (version 1.15a) long ago, which continues to run in current versions of WINE with no problems. The logic of the program is unchanged since the "a" patch, and since the binary can simply be loaded into the WINE bottle, there is no need to compile it from scratch on any Linux or Mac operating system version.

PyLotRO is a Windows program -- not a Linux program -- which is intended to run inside the WINE bottle.

The existence of so many different and varied Linux distributions DOES make any attempt to maintain a source code version difficult, if not impossible, as Linux is anything but standardized. (He happens to be Linux, not Mac based himself.)
RE: In Game Store
by Steven Wilson on Wednesday January 23rd 2013, 15:12
Since Valve now makes a steam client for linux then maybe they can come linux > wine > lotro players aid. The linux steam client is still in beta so it might take a while even if they are willing to help.
RE: In Game Store
by William Magill on Wednesday January 23rd 2013, 15:25
Unless you have read something different from what I saw... the "Steam Client" is exactly that -- the Steam Client... not any specific game, nor ports of other software. It's up to the original vendors to do the ports (or possibly pay Valve to do them.)

The Steam download of LOTRO is simply the Turbine client(s) (Windows and Mac) hosted on Valve's network instead of Akamai. The downloads are bit-identical!

The Steam Client is the interface to Steam's tracking system, player matching, "in-game" audio and the overlay. It is a wrapper ... it's even less of an emulator than WINE! :)
RE: In Game Store
by Erik Wroblewski on Monday February 4th 2013, 18:16
Sadly, even if Steam Linux Client could do something so marvelous as run LotRO in Linux/OSX without the need of anything else, or implement something that actually help it with Wine, the game is available only to US and some European countries. The rest of the world just can’t download LotRO through Valve servers, receiving a message like “this game is not available to your “area”.
So, to someone like me, who live in Brazil, the Linux Steam client may be a great deal with other games, but when I talk about LotRO, it is worthless =/
RE: In Game Store
by Björn Bidar on Monday February 4th 2013, 18:20
As the OS X client of Lotro is not tied steam, so I don't see why the should do this with a Linux version.
RE: In Game Store
by William Magill on Monday February 4th 2013, 18:51
While neither of the LOTRO Clients (Mac and Windows) are tied to Steam, Steam's "contract" with WB/Turbine restricts them to delivering it only to ?North American and European? users of Steam.

WB/Turbine clearly has other versions of the Client which are Russian and Chinese based. (And they have separate servers in those countries.)

Currently, the distributions from LOTRO.COM are done by Pando Media Booster -- which is its own CDN (COntent Delivery Network) like Steam. As far as I know they are available world-wide.

The real problem which LOTRO has, when may or may not exist with any other MMO today, is the size of the Client. At 18GB, it is a HUGE download. Both Steam and PMB are "torrent style" downloaders. As such, they "smell" like Peer to Peer File Sharing aka Piracy... and many ISPs block or otherwise restrict such traffic.

Currently, the PMB download of the Mac Client is restricted to about 550K BPs, with no mechanism to change that. I've been working with PANDO to straighten out some issues with the their new downloaders (the versions were updated in mid January), and will eventually, I hope, manage to address the "throttling" issue. It is purely artificial, and a result of the coding of the Java version of the PMB downloader. The problem exists for both the current Windows and Mac dowloaders at lotro.com.

As for a LINUX version of the LOTRO Client from Steam -- I strongly doubt that such a thing is in the works. Steam is developing a STEAM client (i.e. the downloader and "overlay") to run on some, I believe only one, version of Linux. To the best of my knowledge, Steam has NOT be contracted to port LOTRO to Linux.
Graphics Issues with Update 9
by William Magill on Tuesday December 25th 2012, 11:12
Note that, especially with the Bree Revamp, there are quite a few "significant" graphics issues in certain locations in Update 9.

In particular, working with the Mac Client -- which runs OpenGL as opposed to DXx -- we have verified that un-cheking "Speculative Lighting" eliminates many Graphics issues in Bree.

That particular setting can cause a Toggle effect on walls and colorations in Bree.

I haven't had a chance to verify this with Crossover (WINE 1.5.15), but it wouldn't surprise me to discover a similar situation.
RE: Graphics Issues with Update 9
by William Magill on Tuesday December 25th 2012, 11:15
What I should have mentioned -- the Graphics in Bree were "updated' (Converted) to the new Riders of Rohan level. Which, according to the Developer Scarycrow, uses significantly "different" graphics capabilities than were previously used in LOTRO.
RE: Graphics Issues with Update 9
by Erik Wroblewski on Thursday January 10th 2013, 11:17
As far as I tested it in the last 3 days, under Wine 1.5.21 (Linux), Bree is still somewhat bugged, but it is significantly better than before. Moria and Lothlorien still have some minor glitches (strange colors and corrupted textures minor areas on the floor or in waterfalls, for example), but the average game experience is unaffected now.

Most buildings will not vanish anymore in Bree, and the color changes occur only when the camera change focus.
unimplemented function d3d11.dll.D3D11CreateDevice
by Björn Bidar on Monday December 24th 2012, 14:42
Anyone has the same issue:?
err:xvidmode:ComputeGammaFromRamp strange gamma ramp ([1]=105 for 114->115), rejected

wine: Call from 0x7b83bcb2 to unimplemented function d3d11.dll.D3D11CreateDevice, aborting

System: Thinkpad Edge E530
GPU: Nvidia Geforce GT 630

No change when using virtualgl or primus
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Michael Davenport on Monday December 24th 2012, 15:25
Are you by chance using wine 1.5.20?
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Björn Bidar on Monday December 24th 2012, 15:27
Yes
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Michael Davenport on Monday December 24th 2012, 15:29
Could you quickly try adding d3d11.dll to overrides tab and then disabling it?
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Björn Bidar on Monday December 24th 2012, 15:37
The wine complies about that the game requires it and says its not found, but it start.
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Björn Bidar on Monday December 24th 2012, 15:42
This was with primus, with optirun it don't starts.
With primus I can't click anything after loading screen.
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Michael Davenport on Monday December 24th 2012, 15:53
Just out of curiosity, did lotro work for you with 1.5.19 on that current setup?

I'm sure the answer is yes, so I'll try to figure out the issue. Could you post what wine outputs up until after the loading screen?
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Björn Bidar on Monday December 24th 2012, 16:00
I reseted 'GraphicsCore' and now I come after game loading screen but don't after character loading screen
Log:
err:xvidmode:ComputeGammaFromRamp strange gamma ramp ([1]=105 for 114->115), rejected

err:module:import_dll Library d3d11.dll (which is needed by L"C:\\Programme\\Der Herr der Ringe Online\\D3D11GraphicsCore.dll") not found

[8:55:13004:ERROR:chrome_url_request_context.cc(94)] Cannot use V8 Proxy resolver in single process mode.


[8:64:20130:ERROR:proxy_resolver_winhttp.cc(95)] WinHttpGetProxyForUrl failed: 0


err:ntdll:RtlpWaitForCriticalSection section 0x1109e994 "?" wait timed out in thread 003d, blocked by 0000, retrying (60 sec)

err:ntdll:RtlpWaitForCriticalSection section 0x7bcc5960 "../../../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0009, blocked by 0037, retrying (60 sec)

err:ntdll:RtlpWaitForCriticalSection section 0x8c2ea2c "../../../wine/dlls/winealsa.drv/mmdevdrv.c: ACImpl.lock" wait timed out in thread 002b, blocked by 0028, retrying (60 sec)
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Björn Bidar on Monday December 24th 2012, 16:01
I don't used this prior wine 1.5.20 (I primary play it on my desktop but this was some months ago).
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Michael Davenport on Monday December 24th 2012, 16:16
Just to see if the issue is actually isolated with wine 1.5.20, could you downgrade to 1.5.19 if it's possible for your distribution.
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Björn Bidar on Tuesday December 25th 2012, 15:29
Yes wine 1.5.20 was the issue.
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Björn Bidar on Tuesday January 8th 2013, 6:31
Now I tested it again on my destop (i7 2nd gen and Nvidia Geforce GTX 580, for more details: www.sysprofile.de/id123113), with the latest version of wine (currently wine 1.5.21) and now I get this, after
selecting my character:
*** Error in `lotroclient.exe': malloc(): memory corruption: 0xebb0ad10 ***
======= Backtrace: =========
[...] ... [...]
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Michael Davenport on Tuesday January 8th 2013, 16:10
I'm unsure if you do any programming, but just a malloc(): memory corruption doesn't say enough. It does say evidently that memory that was allocated to lotro had been manipulated. Definitely a wine issue, and we should look at the commits.

Could you post some of the backtrace? Maybe like the first third of it.
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Björn Bidar on Tuesday January 8th 2013, 16:29
I had WINEDEDBUG=-all while doing this was why the output was so small.
I done it again with WINEDEBUG-all and tabbed out of the game at character loginscreen and got:

/usr/bin/../lib32/libc.so.6(+0x77052)[0xf751b052]
/usr/bin/../lib32/libc.so.6(+0x78b5a)[0xf751cb5a]
/usr/bin/../lib32/libc.so.6(+0x79ab8)[0xf751dab8]
/usr/bin/../lib32/libc.so.6(realloc+0xe7)[0xf751eb87]
/usr/lib32/libgmp.so.10(__gmp_default_reallocate+0x2a)[0x7d91685a]
/usr/lib32/libgmp.so.10(__gmpz_realloc+0x56)[0x7d92ac06]
/usr/lib32/libgmp.so.10(__gmpz_tdiv_r+0x239)[0x7d92d419]
/usr/lib32/libgmp.so.10(__gmpz_mod+0x62)[0x7d927842]
/usr/lib32/libgnutls.so.28(+0xd9246)[0x7dabd246]
/usr/lib32/libgnutls.so.28(+0xd8c16)[0x7dabcc16]
/usr/lib32/libgnutls.so.28(+0xd8761)[0x7dabc761]
/usr/lib32/libgnutls.so.28(+0xd78af)[0x7dabb8af]
/usr/lib32/libgnutls.so.28(+0xd7adb)[0x7dabbadb]
/usr/lib32/libgnutls.so.28(+0xd1400)[0x7dab5400]
/usr/lib32/libgnutls.so.28(+0xb4d36)[0x7da98d36]
/usr/lib32/libgnutls.so.28(+0xb4ecb)[0x7da98ecb]
/usr/lib32/libgnutls.so.28(+0x25ae8)[0x7da09ae8]
/usr/lib32/libgnutls.so.28(gnutls_handshake+0x66a)[0x7da0709a]
/usr/bin/../lib32/wine/secur32.dll.so(+0x1f55c)[0x7e00055c]
/usr/bin/../lib32/wine/secur32.dll.so(+0x1dfe0)[0x7dffefe0]
/usr/bin/../lib32/wine/secur32.dll.so(InitializeSecurityContextW+0x120)[0x7e006730]
[0x2d2bc3e]
full output: pastebin.com/KkQE0JJb

I done it again with WINEDEBUG= and don't tabbed out of the game before character login was completed, after loading I tried to tab out of the game and got no error, I will try to play longer and see waht I get:

but there is my output for now:
pastebin.com/8kttG13u
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Michael Davenport on Wednesday January 9th 2013, 14:23
I don't experience the same error under wine 1.5.21

What graphics renderer are you using?
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Björn Bidar on Wednesday January 9th 2013, 14:37
It is OpenGL so its may be an issue of a memory lack in lotro it self.
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Michael Davenport on Wednesday January 9th 2013, 15:53
Change it to directx9.

As counter-intuitive as it is, I have never seen a decrease in performance even when using a low end card such as intel HD 3000. I play on the highest setting just fine.
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by Björn Bidar on Wednesday January 9th 2013, 16:06
Yes actually, but I hope we get d3dx11/OpenGL 4 effects in some time in this render mode cause till the d3dx11 works will take much more time.
RE: unimplemented function d3d11.dll.D3D11CreateDevice
by William Magill on Thursday January 10th 2013, 12:16
Significant to the OpenGL issue and LOTRO Graphics in general...

1- the native Mac Client is 100% OpenGL
2- The Windows Client AND the Mac Client are still suffering from the fact that they are 32 bit clients attempting to address more than 4GB of memory!

This 32 bit client issue is not likely to be resolved until Microsoft makes all of its 32Bit OS EOL!... and probably not even then, as it is a direct limit on "older" (i.e. cheaper) systems playing the game. Hopefully, at some time technology will overrule marketing, but until then, don't hold your breath.

Through Update 9, Turbine has been addressing the various Memory Leaks in LOTRO via repeated patches.
However, even with the Mac Client, which has only ever run on a 64 bit operating system (OSX), the problems persist, and and are fairly acute.
They have made significant inroads, but the underlying problems persist, and manifest themselves persistently.

The LOTRO Client has always been a "big" client, running just under the 4GB celling. With the release of Update 8 (Riders of Rohan) Turbine implemented significant changes to the Game Engine -- not the least of which was the replacement of an external browser for all NPC dialogs with Awesomium -- another 32 bit product based on Chromium.

ALL dialogs with the player -- NPC, Vault, Store, Options, etc. are processed by Awesomium.

In general, the length of time one can play before being "attacked" by the Memory Leak issue is directly dependent upon player activity. The things which precipitate the Memory Leak are:
* Playing in Rohan (and now with Update 9, Bree)
* Transitions -- doorways, gateways, swift-travel, Instances, Session Plays, etc.
* extensive NPC interaction -- as with Vaults, options, quests, Task Boards, etc.

There may be things external to the game engine (i.e. hardware) which relate to mitigation of the problem, but if there are Turbine support has not shared them with the User Community.
Keyboard keys not reporting to LOTRO
by Beej on Monday December 17th 2012, 1:43
It has taken forever to get LOTRO working on my machine, from compatibility problems to video driver issues, nothing has gone right. I finally had to force Winetricks to "Emulate a virtual desktop" in order to prevent it from opening LOTRO as an 800x600 window that crashes as soon as you try to adjust the resolution from within the game. I have no idea what that's about but it's working.

So, now I'm finally in LOTRO only to discover that the game isn't grabbing the keyboard strokes you need to control the game; namely the control keys, alt keys and I think the shift keys. The windows key works but it also activates something outside of windows. The control keys cause the mouse location to pulse (like a pointer finder for a laptop), but don't register to activate normal functions like ctrl-O and ctrl-/ or quick slots like ctrl-1.

In the process of trying to figure out the keys and if I could remap the keyboard, I also ran into a problem where the mouse started behaving badly - it wasn't registering what I was clicking on (Exit game) and kept giving me a combat warning.

Is this normal? Is there some other set of steps I missed in setting up LOTRO?

I'm on Wine1.5.19 with Winetricks, Ubuntu 12.04.1 LTS (32bit), AMD AthlonII x2 270, ASUS HD5450 1gb (ATI Radeon) w/ ATI/AMD prop FGLRX driver. And, I'm an utter newbie to linux.
RE: Keyboard keys not reporting to LOTRO
by Michael Davenport on Monday December 17th 2012, 10:25
I assume you're playing in windowed mode still.

I suggest while in window mode setting the game to it's maximum resolution, then quitting and finally removing emulate a virtual desktop. I personally had to go through these steps to get a full screen.

Regarding the other issue, I haven't experienced it. Could you post your wine output as the game is loading up?

Just run pylotro through a terminal and then login.
RE: Keyboard keys not reporting to LOTRO
by William Magill on Monday December 17th 2012, 11:13
There is a known issue from Update 8 (which still existed in Update 9 Beta3; status in the Update 9 release is not yet known) for the Native Mac Client AND for CrossOver 12 (WINE 1.5.15). Note, this situation is well known to the player community, but not fully acknowledged by Turbine.

It is easy to verify this is what is happening -- Turbine, in kind of a "semi-acknowledgement, has now added a "what to do with the audio when focus is lost setting -- "Audio/Focus Loss Behavior": Options "Persist sound"; "Disable Sound" (the default) and "mute sound".

Basically you CANNOT change screen resolutions without the client "loosing focus." I.e. if you change from Full Screen, as at first launch, to any other resolution, including windowed mode, you can no longer type into the chat window or interact with any of the various NPC dialog boxes, etc... the keyboard focus has been lost by the client. Other Graphics changes also will trigger this Loss of Focus. However, "movement keys -- WASD, and arrow keys, continue to work, as to most of the rest of the "normal" keyboard controls. It is only the "alpha/numeric typing" which disappears.

One work-around is to edit the "UserPreferences.ini" file -- change (from True to False) -- "FullScreen=False"
and set the two resolution values appropriately:
Resolution=2560x1440
WindowedResolution=1920x1200
(I run windowed on a 27 inch iMac. You do not need to pick values which match the in-game tables, they just need to be correct for your environment.)

The other is to Change your settings, exit the game, and log back in.
Note: You need to exit cleanly. The UserPreferences.ini file is written out ONLY on a clean exit!
Lotro Store
by Steven Wilson on Sunday December 16th 2012, 20:47
When entering the Lotrol store it shows a black empty box!
RE: Lotro Store
by Michael Davenport on Monday December 17th 2012, 10:18
I'm able to access the lotro store in the character selection screen just fine. In game on the other hand there is the black screen.
RE: Lotro Store
by Michael Davenport on Monday December 17th 2012, 11:29
This issue has been very much prevalent with prior releases of lotro. Others suggest it might a turbine issue.
RE: Lotro Store
by Steven Wilson on Wednesday January 23rd 2013, 15:05
A work around was discovered by others:

Log out the character then re log the same character. The lotro store now displays correctly until I start the game again. Apparently there is something not correct in wine asomeum patch that dosn't set port I/O correctly but re logging your toon uses the game client instead and that seems to fix it.
plylotro will not connect to realm!
by Steven Wilson on Saturday December 15th 2012, 19:16
steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~$ WINEPREFIX=/$HOME/LOTRO wine $HOME/Downloads/pylotro-setup.exe
fixme:iphlpapi:NotifyAddrChange (Handle 0xefe2f8, overlapped 0xefe310): stub
fixme:iphlpapi:NotifyAddrChange (Handle 0x101e8d0, overlapped 0x101e8dc): stub
wine: configuration in '//home/steve7233/LOTRO' has been updated.
fixme:win:DisableProcessWindowsGhosting : stub
fixme:msg:ChangeWindowMessageFilter c055 00000001
fixme:msg:ChangeWindowMessageFilter c055 00000001
fixme:msg:ChangeWindowMessageFilter c055 00000001
fixme:ieframe:taskbar_list_SetProgressValue iface 0x18cc28, hwnd 0x10088, ullCompleted 0, ullTotal 34b0e0b stub!
fixme:sfc:SfcIsFileProtected ((nil), L"C:\\Program Files (x86)\\PyLotRO\\unins000.exe") stub
fixme:ieframe:taskbar_list_SetProgressState iface 0x18cc28, hwnd 0x10088, flags 0 stub!
steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~$ fixme:system:SetProcessDPIAware stub!
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files (x86)\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files (x86)\\PyLotRO\\qt4_plugins\\imageformats\\qsvg4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files (x86)\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files (x86)\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
fixme:win:FlashWindowEx 0x33e59c
fixme:win:FlashWindowEx 0x33ae4c
fixme:shell:BrsFolder_OnCreate flags BIF_NEWDIALOGSTYLE partially implemented
fixme:win:FlashWindowEx 0x336e1c
fixme:win:FlashWindowEx 0x337f0c
fixme:imm:NotifyIME IMC_SETCANDIDATEPOS
fixme:imm:ImmReleaseContext (0x50074, 0x1ea210): stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
fixme:imm:NotifyIME IMC_SETCANDIDATEPOS
fixme:win:FlashWindowEx 0x33ad0c
fixme:imm:NotifyIME IMC_SETCANDIDATEPOS
fixme:win:FlashWindowEx 0x338cfc

I had to go to options to tell the launcher where the game was but that was obvious since I used WINEPREFIX=.

What is FlashWindowsEx?
RE: plylotro will not connect to realm!
by Michael Davenport on Saturday December 15th 2012, 22:31
Can you download and try this version of PyLotro

ubuntuone.com/54ctpNaN5iwsoPIH6ZELxD

It's the one i'm actually using, and I just assumed the one prior listed on another lotro page was in working condition.

Make sure you patch your game before launching it.
RE: plylotro will not connect to realm!
by Steven Wilson on Sunday December 16th 2012, 10:33
Installed the new version of pylotrol but patch failed!

Connecting to patch.lotro.com:80

Checking files...
files to patch: 2 bytes to download: 1506992
Patching files:

Downloading selfpatch.dll............................

Downloading patchclient.dll................................................

...........................................................................

.......................................
File in use. It will be self patched.

Self patch required. Program will restart.

Connecting to patch.lotro.com:80

Checking files...
files to patch: 1 bytes to download: 0
Patching files:
Downloading patchclient.dllFile in use. It will be self patched.

Self patch required. Program will restart.

Connecting to patch.lotro.com:80

checking data...
Data patch check failed result code: 0x80004004
Failed to check data: E_ABORT(0x80004004)

*** Finished ***
RE: plylotro will not connect to realm!
by Michael Davenport on Sunday December 16th 2012, 11:34
Try quiting Pylotro and running it again. I'm currently reviewing solutions to solve your problem.

If it works feel free to comment back.
RE: plylotro will not connect to realm!
by Steven Wilson on Sunday December 16th 2012, 15:50
I already tried that. I will try rebooting and see if that helps. Back in a moment.
RE: plylotro will not connect to realm!
by Steven Wilson on Sunday December 16th 2012, 16:01
No joy.

steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~$ WINEPREFIX=/$HOME/LOTRO wine $HOME/LOTRO/drive_c/'Program Files (x86)'/PyLotRO/pylotro.exe
fixme:system:SetProcessDPIAware stub!
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files (x86)\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files (x86)\\PyLotRO\\qt4_plugins\\imageformats\\qsvg4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files (x86)\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
err:module:import_dll Library QtSvg4.dll (which is needed by L"C:\\Program Files (x86)\\PyLotRO\\qt4_plugins\\iconengines\\qsvgicon4.dll") not found
fixme:win:FlashWindowEx 0x32e59c
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
fixme:toolhelp:Heap32ListFirst : stub
fixme:imm:ImmReleaseContext (0x1006a, (nil)): stub
fixme:imm:NotifyIME IMC_SETCANDIDATEPOS
fixme:win:FlashWindowEx 0x32a95c
fixme:imm:NotifyIME IMC_SETCANDIDATEPOS
fixme:win:FlashWindowEx 0x32894c
steve7233@steve7233-HP-Pavilion-dv6-Notebook-PC:~$
RE: plylotro will not connect to realm!
by Michael Davenport on Sunday December 16th 2012, 18:05
This isn't telling me anything that would actually hinder the running of the program.

wine '/home/michael/.wine/drive_c/Program Files (x86)/PyLotRO/pylotro.exe'

Would give me the same output, but pylotro runs and lotr runs as well.


What realm are you trying to connect to, has patching at all been successful, and have you pointed pylotro via the client based selection tool to the installed directory of lotro?

tools>options to point to the current directory.

Also, how have you installed lotro? Disk, online downloader/installer?
RE: plylotro will not connect to realm!
by Steven Wilson on Sunday December 16th 2012, 20:20
I solved the problem. I used the high res installer the solution was to uninstall LOTROL and reinstall using the low res install. Now patching and launching the game via pylotrol works. I have to fiddle with window boarders a bit every-time I play as the VIZIO TV doesn’t report it's hdmi settings to the os correctly. I understand 720P hdmi TV’s don't report their res and aspect ratios correctly. This has the same problem in windows so, its not just Linux. I wish it was 1280P, then it would probably report correctly.
RE: plylotro will not connect to realm!
by Michael Davenport on Sunday December 16th 2012, 21:40
All right, while I wasn't much help I'm very much excited you were able to find the solution.

I'll make a note of it for other people to look at.
RE: plylotro will not connect to realm!
by Steven Wilson on Sunday December 16th 2012, 10:42
I thought I would add that I am using Kubuntu 12.04.1 last updated last night and wine 1.5.19.
No need for any external browser
by William Magill on Tuesday December 11th 2012, 13:36
With the Riders of Rohan update, LOTRO now uses Awesomium (based on Chromium) for all of the in-game displays previously associated with an external browser. This includes ALL dialog boxes with NPC, Vaults, Crafting, the LOTRO Store, help desk, forums, etc.
RE: No need for any external browser
by Steven Wilson on Friday December 14th 2012, 19:59
I installed with no winetricks. The installer seemed to work although I did have to use the GC switch to get Panda Media Booster to run. When the game launched I got Launcher error Active x support is not implemented.
RE: No need for any external browser
by Steven Wilson on Wednesday January 23rd 2013, 15:19
Never mind it was because I used the high res installer which has been found to be not compatible with pylotro. I reinstalled using the low res installer.
Back