Wine doesn't work at all on Ubuntu 64 bit

[Justin_ZW]

I've used Wine before on Ubuntu when I had a 32-bit version of the OS, but I've since gotten a new laptop and installed a 64 bit version. However, Wine doesn't seem to want to play ANY of my games now. All I really want it for is Doom, and it ran that just fine on my old and terrible computer. I've thus come to the conclusion that Wine doesn't want to play nice with a 64 bit version of Ubuntu. Every time I try to start Doom (or any other game, for that matter), I get this error:
Unhandled exception: page fault on read access to (memory location) in 32-bit code (memory location)

Is there something special I have to do to make Wine work on a 64 bit Ubuntu? I tried a simple apt-get install wine, and then I found this and tried the CHROOT option, but it didn't solve my problem.

All I really want is to be able to play Doom with the Brutal Doom mod because that is quite possibly my favorite game ever, and it almost feels like this isn't even worth it. I've been jumping through hoops for the past four or five hours, and that's why I'm here. I've finally given up on trying to do this myself, so if anyone can help me, I'd appreciate it.

This is on Ubuntu 12.04 LTS, by the way, with Wine v1.4.

[dimesio]

Most Ubuntu users have 64 bit systems and Wine works. Compiling Wine on 64 bit Ubuntu can be something of a challenge, though.

I tried a simple apt-get install wine, and then I found this and tried the CHROOT option

Did you uninstall the package via your package manager before installing the Wine you built yourself? You should have, and if you didn't, that's most likely the cause of your problems. If that's not it--were there any warnings from ./configure that you ignored?

FYI, Wine 1.4 is old and no longer supported. The Wine PPA does have newer packages for 12.04. I recommend trying either the stable or development package from there before compiling Wine yourself. But make sure you uninstall the Wine you compiled before installing the package.

[Justin_ZW]

No, there were no problems with the ./configure. The make did take almost two hours, though. And yes, I made sure to do an apt-get remove wine before compiling it in the chroot.

In addition, I have the PPA added to my apt repositories list (via add-apt-repository ppa:ubuntu-wine/ppa) and yet it continues to install wine 1.4. I've tried finding what I believe to be the latest stable (1.6?), and that has proven fruitless. I can't locate the correct version, and the Ubuntu PPA only has 1.4. I've tried multiple times to find 1.6 via apt and it continues to tell me that the only available versions are 1.2-1.4

Maybe some light could be shed on this?

I should also add that I had no problems on my 32 bit when I simply did a apt-get install wine. It worked right out of the box.

EDIT: Somewhat embarrassing, here, but I forgot to run an apt-get update to allow downloading of 1.6. I'm doing that now.

[dimesio]

I don't know what's going on with your package manager; https://launchpad.net/~ubuntu-wine/+arc ... er=precise lists both wine1.6 and wine1.7 packages. Ask for help on the Ubuntu forum.

[Justin_ZW]

I did find it there after doing an apt-get update. However, it doesn't seem to have created the .wine directory or any of the necessary subdirectories, and now Wine just refuses to do anything at all. I'm honestly almost at the point where I just chalk this one up as a loss and delete all of this stuff.

[dimesio]

~/.wine doesn't get created until you actually run something in Wine. What happens when you run winecfg?

[Justin_ZW]

Haha, yeah, just found that out. Doom actually started running! Although... it's SOOOO SLOW. Slower than it was on my horribly old desktop, and I just don't understand this. But that's a question for another day. I have something working, so that's a start, and I need to get to bed. Thanks for pointing me toward Wine 1.6, dimesio. I'm sure I've made myself look like a proper retard, so I appreciate your tolerance

[southbird]

Doom actually started running! Although... it's SOOOO SLOW. Slower than it was on my horribly old desktop, and I just don't understand this.

Given you noted Brutal Doom, I'm wondering what source port you're using to play it. If the answer is GZDoom, that has only started to work in recent Wine versions with updates to XInput. (Previously it would run but you couldn't control anything!)

GZDoom under recent Wine versions mostly works but tends to constantly spew something to the console (can't remember what it is off-hand), which causes significant slowdown. Redirecting that to /dev/null seemed to do the trick.

Also, what should be obvious, make sure you have actual 3D acceleration drivers installed and working, preferably binaries from your manufacturer.

And last resort, if Doom is your only problem, check if the source port you're running has a Linux compile option. I know GZDoom at least USED to, although I haven't tried to build it manually for some time (especially with my success from recent Wine versions.)