Diablo 3 on archlinux

johnride · 2012-05-28 22:16:05

Tried to réinstall it and now it seems worst... When the install finished I cliked "PLay" but it froze there. After I tried to relaunch it but it says updating tools and stays at 0%.

In the tests results from the wine appdb a guy got it working on Arch with "Wine vanilla 1.5.4 from repos".

I looked at the repos and I can't find anything about Wine vanilla, nor in the AUR.

Have an idea what it may be?

Thanks

Brcher · 2012-05-28 22:47:08

Vanilla usually means "unmodified." So he was probably saying that he used the default install (pacman -S wine, or whatever) rather than the AUR wine-diablo install.

johnride · 2012-05-29 06:52:05

Lol thanks!

I still am a happy newbie apparently... more to learn is more fun with Linux anyways!

groundnuty · 2012-05-30 09:45:00

getting an error while compiling (x86 here)
http://pastie.org/3994229

anyone, any ideas?

Last edited by groundnuty (2012-05-30 09:45:09)

Enverex · 2012-05-30 09:46:52

That looks like it's building as 64bit, you should generally build Wine as 32bit unless something's changed since I last manually compiled it.

groundnuty · 2012-05-30 10:52:05

it seems to be going ok according to PKGBUILD of https://aur.archlinux.org/packages.php?ID=58739
os is recognized as x86. 64bit version is able to build fine. just 32bit fails for some reason.
both versions of libtiff are installed. I'm kinda out of ideas

Throne777 · 2012-06-01 12:30:43

I'm using PlayOnLinux to run Diablo 3 (as it worked just fine when I ran it on Ubuntu 12.04), but once I get to the log in screen it says there is a patch, takes me back to the launcher which says it's up-to-date, ad infinitum. Seems to be a similar issue to what johnride was experiencing? Any ideas on how to fix it? 'Vanilla' wine is a no-go

Zancarius · 2012-06-02 17:50:48

Throne777 wrote:

I'm using PlayOnLinux to run Diablo 3 (as it worked just fine when I ran it on Ubuntu 12.04), but once I get to the log in screen it says there is a patch, takes me back to the launcher which says it's up-to-date, ad infinitum. Seems to be a similar issue to what johnride was experiencing? Any ideas on how to fix it? 'Vanilla' wine is a no-go

I didn't have much luck with vanilla Wine, but then it's usually advisable to check the appdb first. The relevant entry is here. Be sure to read it periodically as patches come out, or use Google.

It works just fine with the git version of wine with the patches applied (git apply makes things easy!). The launcher crashes about 30 seconds after you get to the title screen generating a pop-up, but it's not much of an issue.

I get about 60 FPS on my hardware (NVIDIA GeForce GTS 450, Phenom II 1090T, way more RAM than I'm willing to admit). The game stutters slightly when first loading mesh animations, textures, and maps, but is otherwise about as smooth as in Windows with everything but ground clutter turned up.

I seem have the best luck running it on its own desktop. This may work for vanilla wine--try it first before patching/building wine--although you will need to have a fully updated copy of Diablo with all of the associated patches copied over from Windows:

$ cd ~/build/wine
$ ./wine explorer /desktop=3,1920x1080 /misc/games/Diablo\ III/Diablo\ III\ Launcher.exe

Also, it might be necessary to remove your ~/.wine directory and use winetricks to install vcrun2008 and possibly d3dx9/d3dx9_43 and/or dsound. See the appdb comments for specific libraries if the patches don't work.

Last edited by Zancarius (2012-06-02 18:07:58)

Kopfweh · 2012-06-03 14:35:34

I just wanted to mention that I play it without any problems or errors. I just installed it whit playonlinux.

Last edited by Kopfweh (2012-06-03 14:54:17)

Throne777 · 2012-06-07 13:49:12

Zancarius wrote:

Throne777 wrote:
I'm using PlayOnLinux to run Diablo 3 (as it worked just fine when I ran it on Ubuntu 12.04), but once I get to the log in screen it says there is a patch, takes me back to the launcher which says it's up-to-date, ad infinitum. Seems to be a similar issue to what johnride was experiencing? Any ideas on how to fix it? 'Vanilla' wine is a no-go
I didn't have much luck with vanilla Wine, but then it's usually advisable to check the appdb first. The relevant entry is here. Be sure to read it periodically as patches come out, or use Google.
It works just fine with the git version of wine with the patches applied (git apply makes things easy!). The launcher crashes about 30 seconds after you get to the title screen generating a pop-up, but it's not much of an issue.
I get about 60 FPS on my hardware (NVIDIA GeForce GTS 450, Phenom II 1090T, way more RAM than I'm willing to admit). The game stutters slightly when first loading mesh animations, textures, and maps, but is otherwise about as smooth as in Windows with everything but ground clutter turned up.
I seem have the best luck running it on its own desktop. This may work for vanilla wine--try it first before patching/building wine--although you will need to have a fully updated copy of Diablo with all of the associated patches copied over from Windows:
$ cd ~/build/wine
$ ./wine explorer /desktop=3,1920x1080 /misc/games/Diablo\ III/Diablo\ III\ Launcher.exe
Also, it might be necessary to remove your ~/.wine directory and use winetricks to install vcrun2008 and possibly d3dx9/d3dx9_43 and/or dsound. See the appdb comments for specific libraries if the patches don't work.

Someone over at PlayOnLinux found a missing dependency.
Installed lib32-libldap & now it works just fine ^ ^

aardwolf · 2012-06-07 18:22:51

DSpider wrote:

Dual booting is really not that difficult.

I am a guy likes to work, play a bit, work more, play a bit again, etc... Rebooting to another OS every time for a little relaxation in between is a way too large context switch. Way better is to leave your stuff open, and launch the game to play it, when done close it, and continue working.

So yes, dual booting is difficult if it involves closing and reopening everything.

Meyithi · 2012-06-08 06:25:26

Game's working great, just started a Barbarian.

http://www.meyithi.com/graphics/d3.png

Built wine with the aur package, used winetricks to install vcrun2008, ran the launcher and off we go! Running on max graphics as smooth as butter. The Guild Wars 2 betas are also working nicely in wine as well, as long as these two games keep working well I can't see myself booting up my windows machine for a long time.

Enverex · 2012-06-12 20:54:27

I still can't open the installer or game itself (after having copied it over from another machine). It always crashes with the typical Windows error box, but it contains all the Wine trace info:

Unhandled exception: page fault on read access to 0xffffffff in 32-bit code (0x7d52e968).
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:7d52e968 ESP:0033f418 EBP:7dc849a8 EFLAGS:00010242(  R- --  I  Z- - - )
 EAX:00000030 EBX:7d537ff4 ECX:00000000 EDX:7d538648
 ESI:7d538648 EDI:7dc854d8
Stack dump:
0x0033f418:  00000628 f7582430 00000620 00000050
0x0033f428:  00000018 00000638 00000003 00000000
0x0033f438:  00000000 3fe00000 000000c5 00000050
0x0033f448:  3f6ac083 0000006e 00000077 0000007c
0x0033f458:  00000002 00000004 0000bb80 f7581ff4
0x0033f468:  f7582400 0000a418 0000a418 f745b640
Backtrace:
=>0 0x7d52e968 in libspeexdsp.so.1 (+0x9968) (0x7dc849a8)
  1 0x7d52f05a in libspeexdsp.so.1 (+0xa059) (0x7dc849a8)
  2 0x7d53020c speex_resampler_init_frac+0x19b() in libspeexdsp.so.1 (0x7dc6d8d8)
  3 0x7d7789b3 _init+0x386() in libasound_module_rate_speexrate. (0x00000000)
  4 0x7d37324e in libasound.so.2 (+0x6924d) (0x00000000)
  5 0x7d360b34 in libasound.so.2 (+0x56b33) (0x7dc85d38)
  6 0x7d3790a3 in libasound.so.2 (+0x6f0a2) (0x7dc85d38)
  7 0x7d360b34 in libasound.so.2 (+0x56b33) (0x0033fa08)
  8 0x7d351252 snd_pcm_hw_params+0x31() in libasound.so.2 (0x0033fb40)
  9 0x7d73c4dc in winealsa (+0x1c4db) (0x0033fb40)
  10 0x7d5da907 in dsound (+0x1a906) (0x0033fba0)
  11 0x7d5db4f4 in dsound (+0x1b4f3) (0x0033fc20)
  12 0x7d5dbdfa in dsound (+0x1bdf9) (0x0033fc60)
0x7d52e968: 	
Modules:
Module	Address			Debug info	Name (113 modules)
PE	  340000-  385000	Deferred        phonon4
PE	  3e0000-  3ea000	Deferred        qgif4
PE	  400000- 143d000	Export          blizzard launcher
PE	 1880000- 188b000	Deferred        qico4
PE	 1890000- 18c3000	Deferred        qjpeg4
PE	 18d0000- 190a000	Deferred        qmng4
PE	 1910000- 1958000	Deferred        qtiff4
PE	10000000-10a5d000	Deferred        qtwebkit4
PE	61000000-61056000	Deferred        qtxml4
PE	64000000-640f2000	Deferred        qtnetwork4
PE	65000000-657d2000	Deferred        qtgui4
PE	67000000-67234000	Deferred        qtcore4
ELF	7b800000-7ba3d000	Deferred        kernel32<elf>
  \-PE	7b810000-7ba3d000	\               kernel32
ELF	7bc00000-7bcd3000	Deferred        ntdll<elf>
  \-PE	7bc10000-7bcd3000	\               ntdll
ELF	7bf00000-7bf04000	Deferred        <wine-loader>
ELF	7d30a000-7d400000	Dwarf           libasound.so.2
ELF	7d525000-7d539000	Dwarf           libspeexdsp.so.1
ELF	7d5b1000-7d600000	Dwarf           dsound<elf>
  \-PE	7d5c0000-7d600000	\               dsound
ELF	7d71e000-7d74d000	Dwarf           winealsa<elf>
  \-PE	7d720000-7d74d000	\               winealsa
ELF	7d74d000-7d768000	Deferred        libgcc_s.so.1
PE	7d778000-7d77b000	Dwarf           libasound_module_rate_speexrate.
ELF	7d77b000-7d7a0000	Deferred        mmdevapi<elf>
  \-PE	7d780000-7d7a0000	\               mmdevapi
ELF	7d7f9000-7d802000	Deferred        librt.so.1
ELF	7d807000-7d825000	Deferred        wintab32<elf>
  \-PE	7d810000-7d825000	\               wintab32
ELF	7d8a2000-7d8ad000	Deferred        libxcursor.so.1
ELF	7d8af000-7d8e5000	Deferred        uxtheme<elf>
  \-PE	7d8c0000-7d8e5000	\               uxtheme
ELF	7d977000-7d9a0000	Deferred        libexpat.so.1
ELF	7d9a0000-7d9d5000	Deferred        libfontconfig.so.1
ELF	7d9d5000-7d9e5000	Deferred        libxi.so.6
ELF	7d9e5000-7d9ee000	Deferred        libxrandr.so.2
ELF	7d9ee000-7d9f8000	Deferred        libxrender.so.1
ELF	7d9f8000-7d9fe000	Deferred        libxxf86vm.so.1
ELF	7d9fe000-7da20000	Deferred        libxcb.so.1
ELF	7da20000-7da3a000	Deferred        libice.so.6
ELF	7da3a000-7db71000	Deferred        libx11.so.6
ELF	7db71000-7db83000	Deferred        libxext.so.6
ELF	7db83000-7dc13000	Deferred        winex11<elf>
  \-PE	7db90000-7dc13000	\               winex11
ELF	7dd13000-7ddaf000	Deferred        libfreetype.so.6
ELF	7ddb1000-7ddb7000	Deferred        libxfixes.so.3
ELF	7dde7000-7de59000	Deferred        ddraw<elf>
  \-PE	7ddf0000-7de59000	\               ddraw
ELF	7de59000-7dfa0000	Deferred        wined3d<elf>
  \-PE	7de70000-7dfa0000	\               wined3d
ELF	7dfc2000-7dfc9000	Deferred        libxdmcp.so.6
ELF	7dfc9000-7dfd2000	Deferred        libsm.so.6
ELF	7dfd2000-7e00e000	Deferred        d3d9<elf>
  \-PE	7dfe0000-7e00e000	\               d3d9
ELF	7e00e000-7e035000	Deferred        mpr<elf>
  \-PE	7e010000-7e035000	\               mpr
ELF	7e035000-7e039000	Deferred        libxcomposite.so.1
ELF	7e039000-7e049000	Deferred        libbz2.so.1.0
ELF	7e049000-7e06d000	Deferred        iphlpapi<elf>
  \-PE	7e050000-7e06d000	\               iphlpapi
ELF	7e06d000-7e0e4000	Deferred        wininet<elf>
  \-PE	7e080000-7e0e4000	\               wininet
ELF	7e0e4000-7e113000	Deferred        msvcr90<elf>
  \-PE	7e0f0000-7e113000	\               msvcr90
ELF	7e113000-7e1b1000	Deferred        msvcrt<elf>
  \-PE	7e130000-7e1b1000	\               msvcrt
ELF	7e1b1000-7e2b3000	Deferred        msvcp90<elf>
  \-PE	7e1e0000-7e2b3000	\               msvcp90
ELF	7e2b3000-7e2e7000	Deferred        ws2_32<elf>
  \-PE	7e2c0000-7e2e7000	\               ws2_32
ELF	7e2e7000-7e30b000	Deferred        imm32<elf>
  \-PE	7e2f0000-7e30b000	\               imm32
ELF	7e30b000-7e435000	Deferred        oleaut32<elf>
  \-PE	7e320000-7e435000	\               oleaut32
ELF	7e435000-7e472000	Deferred        winspool<elf>
  \-PE	7e440000-7e472000	\               winspool
ELF	7e472000-7e557000	Deferred        comdlg32<elf>
  \-PE	7e480000-7e557000	\               comdlg32
ELF	7e557000-7e581000	Deferred        msacm32<elf>
  \-PE	7e560000-7e581000	\               msacm32
ELF	7e581000-7e633000	Deferred        winmm<elf>
  \-PE	7e590000-7e633000	\               winmm
ELF	7e633000-7e735000	Deferred        comctl32<elf>
  \-PE	7e640000-7e735000	\               comctl32
ELF	7e735000-7e7a8000	Deferred        shlwapi<elf>
  \-PE	7e740000-7e7a8000	\               shlwapi
ELF	7e7a8000-7e9d0000	Deferred        shell32<elf>
  \-PE	7e7c0000-7e9d0000	\               shell32
ELF	7e9d0000-7ea4f000	Deferred        rpcrt4<elf>
  \-PE	7e9e0000-7ea4f000	\               rpcrt4
ELF	7ea4f000-7eb1e000	Deferred        gdi32<elf>
  \-PE	7ea60000-7eb1e000	\               gdi32
ELF	7eb1e000-7ec71000	Deferred        user32<elf>
  \-PE	7eb30000-7ec71000	\               user32
ELF	7ec71000-7ecdc000	Deferred        advapi32<elf>
  \-PE	7ec80000-7ecdc000	\               advapi32
ELF	7ecdc000-7ee04000	Deferred        ole32<elf>
  \-PE	7ecf0000-7ee04000	\               ole32
ELF	7ee04000-7ee11000	Deferred        libnss_files.so.2
ELF	7ef9a000-7efc8000	Deferred        libm.so.6
ELF	7efc9000-7efcf000	Deferred        libuuid.so.1
ELF	7efcf000-7efe6000	Deferred        libz.so.1
ELF	7efe6000-7f000000	Deferred        version<elf>
  \-PE	7eff0000-7f000000	\               version
ELF	f73a0000-f73a4000	Deferred        libxinerama.so.1
ELF	f73a6000-f73ab000	Deferred        libdl.so.2
ELF	f73ac000-f73b0000	Deferred        libxau.so.6
ELF	f73e3000-f7586000	Deferred        libc.so.6
ELF	f7586000-f75a1000	Deferred        libpthread.so.0
ELF	f75a1000-f76e4000	Dwarf           libwine.so.1
ELF	f76e5000-f7707000	Deferred        ld-linux.so.2
ELF	f7707000-f7708000	Deferred        [vdso].so
Threads:
process  tid      prio (all id:s are in hex)
0000000e services.exe
	0000001e    0
	0000001d    0
	00000018    0
	00000017    0
	00000015    0
	00000010    0
	0000000f    0
00000012 winedevice.exe
	00000019    0
	00000014    0
	00000013    0
0000001a plugplay.exe
	0000001f    0
	0000001c    0
	0000001b    0
00000020 explorer.exe
	00000021    0
0000002b Agent.exe
	00000039    0
	00000038    0
	00000037    0
	00000036    0
	00000035    0
	00000034    0
	00000033    0
	00000032    0
	00000031    0
	0000002f    0
	0000002e    0
	0000002c    0
00000042 (D) C:\users\Public\Application Data\Battle.net\Client\Blizzard Launcher.1640\Blizzard Launcher.exe
	0000002a   15
	0000000d    0
	0000002d    0
	00000009    0
	00000047    0
	00000046    0
	00000045    0
	00000043    0 <==
System information:
    Wine build: wine-1.5.6
    Platform: i386
    Host system: Linux
    Host version: 3.3.8-1-ARCH

jmissao · 2012-06-13 13:43:23

Enverex wrote:

I still can't open the installer or game itself (after having copied it over from another machine). It always crashes with the typical Windows error box, but it contains all the Wine trace info:

I think I had the same error a few days ago. The trace shows its sound related.
I haven't given much thought into this, but it seemed that wineserver expected pulseaudio to be working.
I had just removed pulseaudio a few hours earlier, reinstalling it and pulseaudio-alsa got it working.
Wine should work without pulseaudio, though. This is only a workaround.

Zancarius · 2012-06-13 17:05:14

jmissao wrote:

Wine should work without pulseaudio, though. This is only a workaround.

The Diablo 3 thread over at WineHQ suggests installing dsound via winetricks if it continues to crash due to sound-related issues. Odd that Pulse was causing you issues...

Enverex · 2012-06-22 16:07:47

Managed to get it to install AND run on my netbook (clean, no matches, mods, etc) but it's stuck in an infinite loop; the launcher says the game is up to date, when the game starts it claims it needs to be updated and exits, repeat ad infinitum.

cmmps · 2012-06-23 18:14:46

Zancarius wrote:
Throne777 wrote:
I'm using PlayOnLinux to run Diablo 3 (as it worked just fine when I ran it on Ubuntu 12.04), but once I get to the log in screen it says there is a patch, takes me back to the launcher which says it's up-to-date, ad infinitum. Seems to be a similar issue to what johnride was experiencing? Any ideas on how to fix it? 'Vanilla' wine is a no-go
I didn't have much luck with vanilla Wine, but then it's usually advisable to check the appdb first. The relevant entry is here. Be sure to read it periodically as patches come out, or use Google.
It works just fine with the git version of wine with the patches applied (git apply makes things easy!). The launcher crashes about 30 seconds after you get to the title screen generating a pop-up, but it's not much of an issue.
I get about 60 FPS on my hardware (NVIDIA GeForce GTS 450, Phenom II 1090T, way more RAM than I'm willing to admit). The game stutters slightly when first loading mesh animations, textures, and maps, but is otherwise about as smooth as in Windows with everything but ground clutter turned up.
I seem have the best luck running it on its own desktop. This may work for vanilla wine--try it first before patching/building wine--although you will need to have a fully updated copy of Diablo with all of the associated patches copied over from Windows:
$ cd ~/build/wine
$ ./wine explorer /desktop=3,1920x1080 /misc/games/Diablo\ III/Diablo\ III\ Launcher.exe
Also, it might be necessary to remove your ~/.wine directory and use winetricks to install vcrun2008 and possibly d3dx9/d3dx9_43 and/or dsound. See the appdb comments for specific libraries if the patches don't work.
Someone over at PlayOnLinux found a missing dependency.
Installed lib32-libldap & now it works just fine ^ ^

Yes... I run into the same issue with the game looping between the launcher and the message saying there was a new patch for the game.
Installing lib32-libldap solved the problem!

Thank you!

Enverex · 2012-06-24 14:08:06

Ok well installing libldap got the game working past the patching stage. Next issue is if I try and create a game, it just waits for a while then fails with error 300008.

EDIT: Just works now. Must have been a server issue at the time.

Last edited by Enverex (2012-06-26 12:43:17)

kanazky · 2012-06-28 00:21:10

Got mine working, but until warden stops banning accounts for using "3rd party tools" for running wine I gotta stick to windows I was over on the diablo 3 forums and apparently wine users are being banned for third party for just using wine

Before reading it on diablo3.com's forums I found the article here:

http://diablo.incgamers.com/blog/commen … -be-banned

Last edited by kanazky (2012-06-28 00:36:48)

Zancarius · 2012-06-28 19:36:57

kanazky wrote:

Got mine working, but until warden stops banning accounts for using "3rd party tools" for running wine I gotta stick to windows I was over on the diablo 3 forums and apparently wine users are being banned for third party for just using wine

Before reading it on diablo3.com's forums I found the article here:
http://diablo.incgamers.com/blog/commen … -be-banned

Out of curiosity, I submitted a ticket to Blizzard's accounting department. This was what I submitted (along with a little background information stating that I tend to play under Wine):

I occasionally play Diablo 3 under Wine in Linux, but I recently stumbled across news that a few Battle.net accounts may have been banned purportedly due to issues with Wine and Warden. While this doesn't concerned me greatly as I don't play very often and I can always boot to Windows instead, I am at least somewhat worried since there is a non-zero probability that at least one of those accounts may not have been doing anything grossly inappropriate.
What I'm curious about is Blizzard's stance on non-Windows (and non-Mac) platforms, like Linux, running Blizzard games under Wine. Should I just give up playing under Wine entirely, bite the bullet, and boot to Windows? Or should I just hang in there--play when I want under the OS I happen to be booted to--and simply address any potential issues if they should arise?

And this was the response:

Ahoy!
Mark from Account Services here! I wanted to let you know right up front, that there really is no right or wrong answer to this question. However personally, I always recommend playing how you feel comfortable. So, if you would like to continue playing on Wine, go for it. If any issues should arise, we can assist appropriately. So, we will be able to see what happened, and if needed, we could get the ban taken off. So, again, no official response, however, personally, I would recommend to stick with it, and if anything should happen, let us know, and we will help out.

(Side note: I've always liked Blizzard's customer service people.)

Anyway, suffice it to say I'm not going to worry about getting banned for playing under Wine. My gut feeling is that some of the people who were banned may have been doing questionable things. If anything should happen (it probably won't), I'll deal with it when it does.

The other side of the coin is that I can understand why Blizzard is worried about limiting the impact cheaters may have (the real money auction house comes to mind), so I can't be too upset about that...

funkypotatoe · 2012-06-30 09:04:59

Enverex wrote:

Managed to get it to install AND run on my netbook (clean, no matches, mods, etc) but it's stuck in an infinite loop; the launcher says the game is up to date, when the game starts it claims it needs to be updated and exits, repeat ad infinitum.

Same here ((

msthev · 2012-06-30 17:52:46

As Enverex wrote already, install lib32-libldap.

Last edited by msthev (2012-06-30 17:53:55)

Rasi · 2012-07-01 07:03:51

msthev wrote:

As Enverex wrote already, install lib32-libldap.

A friend has the same problem and he inissts on this library being installed.

ioos · 2012-07-02 22:26:28

Great. The new catalyst update no longer supports my integrated card on the mobo I purchased last year. Since I couldn't get the performance to a playable level anyway, I give up. I've reinstalled the free drivers and I'll boot into Windows to play.

Has anyone had luck playing under WINE with the Intel Ivy Bridge HD3000? I'm thinking about building a new box and I'm done with AMD.

Smasher816 · 2012-07-07 06:10:52

I was playing Diablo 3 just fine, however I stopped around 6/25 due to various events.
Seeing the "Linux Ban Hammer" information has made me worried of opening the game again.
I do have Windows installed (but rarely use it) but would prefer to not redownload the game.

So I am asking here. Are my fellow Arch Linux users playing Diablo 3 ok?

Last edited by Smasher816 (2012-07-07 14:29:44)

Arch Linux

#26 2012-05-28 22:16:05

Re: Diablo 3 on archlinux

#27 2012-05-28 22:47:08

Re: Diablo 3 on archlinux

#28 2012-05-29 06:52:05

Re: Diablo 3 on archlinux

#29 2012-05-30 09:45:00

Re: Diablo 3 on archlinux

#30 2012-05-30 09:46:52

Re: Diablo 3 on archlinux

#31 2012-05-30 10:52:05

Re: Diablo 3 on archlinux

#32 2012-06-01 12:30:43

Re: Diablo 3 on archlinux

#33 2012-06-02 17:50:48

Re: Diablo 3 on archlinux

#34 2012-06-03 14:35:34

Re: Diablo 3 on archlinux

#35 2012-06-07 13:49:12

Re: Diablo 3 on archlinux

#36 2012-06-07 18:22:51

Re: Diablo 3 on archlinux

#37 2012-06-08 06:25:26

Re: Diablo 3 on archlinux

#38 2012-06-12 20:54:27

Re: Diablo 3 on archlinux

#39 2012-06-13 13:43:23

Re: Diablo 3 on archlinux

#40 2012-06-13 17:05:14

Re: Diablo 3 on archlinux

#41 2012-06-22 16:07:47

Re: Diablo 3 on archlinux

#42 2012-06-23 18:14:46

Re: Diablo 3 on archlinux

#43 2012-06-24 14:08:06

Re: Diablo 3 on archlinux

#44 2012-06-28 00:21:10

Re: Diablo 3 on archlinux

#45 2012-06-28 19:36:57

Re: Diablo 3 on archlinux

#46 2012-06-30 09:04:59

Re: Diablo 3 on archlinux

#47 2012-06-30 17:52:46

Re: Diablo 3 on archlinux

#48 2012-07-01 07:03:51

Re: Diablo 3 on archlinux

#49 2012-07-02 22:26:28

Re: Diablo 3 on archlinux

#50 2012-07-07 06:10:52

Re: Diablo 3 on archlinux

Board footer