computer freezes when loading Guild Wars in WIne

[Auxilio]

When I try to boot up guild wars using wine 1.1.2, it loads up the Guild Wars loader/updater, and then it freezes my whole laptop before I can get to the 3D menu. Also, glxgears works fine. The only way I can get out of it is if I manually shut down the whole system. I own an MSI VR601X-412CA. It has an
integrated Intel graphics card, I believe. I'm also using edubuntu. The line in the Terminal that is the last line (which is the error) is this:
Wars\Gw.exe: brw_curbe.C:87: calculate_curbe_offsets: Assertion 'total_regs <= 32' failed.

[Auxilio (kaptain-kirk)]

Created an attachment (id=15364)
the error/output log of GW

[Vitaliy-bugzilla (vitaliy-bugzilla)]

This is intel driver bug - as seen from it's assert.

Closing invalid - not a Wine problem.

[Vitaliy-bugzilla (vitaliy-bugzilla)]

Invalid I mean

[Vitaliy-bugzilla (vitaliy-bugzilla)]

Closing invalid.

[Auxilio (kaptain-kirk)]

When I try to boot up guild wars using wine 1.1.2, it loads up the Guild Wars loader/updater, and then it freezes my whole laptop before I can get to the 3D menu. Also, glxgears works fine. The only way I can get out of it is if I manually shut down the whole system. I own an MSI VR601X-412CA. It has an
integrated Intel graphics card, I believe. I'm also using edubuntu. The line in the Terminal that is the last line (which is the error) is this:
Wars\Gw.exe: brw_curbe.C:87: calculate_curbe_offsets: Assertion 'total_regs <= 32' failed.

[Bryce Harrington (bryce)]

Hi kaptain-kirk,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

[Auxilio (kaptain-kirk)]

I haven't tried it in a while. Thank you for trying to get back to me. I haven't tried it with the latest type of Ubuntu, though, so I'm not sure if that will help the problem. Now I have Windows dual-booted on my laptop, so I'm don't really need this thread anymore. Thank you for all the help.

=/\= Starfleet out =/\=

> From: <email address hidden>
> To: <email address hidden>
> Date: Fri, 7 Nov 2008 08:24:10 +0000
> Subject: [Bug 256815] Re: computer freezes when loading Guild Wars in WIne
>
> Hi kaptain-kirk,
>
>
> Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)
>
> If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
> Thanks in advance.
>
>
> The output of lspci -vvnn would also be worth having.
>
>
> ** Changed in: mesa (Ubuntu)
> Status: New => Incomplete
>
> --
> computer freezes when loading Guild Wars in WIne
> https://bugs.launchpad.net/bugs/256815
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Wine: Invalid
> Status in “mesa” source package in Ubuntu: Incomplete
>
> Bug description:
> When I try to boot up guild wars using wine 1.1.2, it loads up the Guild Wars loader/updater, and then it freezes my whole laptop before I can get to the 3D menu. Also, glxgears works fine. The only way I can get out of it is if I manually shut down the whole system. I own an MSI VR601X-412CA. It has an
> integrated Intel graphics card, I believe. I'm also using edubuntu. The line in the Terminal that is the last line (which is the error) is this:
> Wars\Gw.exe: brw_curbe.C:87: calculate_curbe_offsets: Assertion 'total_regs <= 32' failed.

_________________________________________________________________

[Hew (hew)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!