Likely the driver update
** Changed in: wine1.2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/709660
Title:
Working applications crash after update to wine 1.
OK now I feel really stupid...
Fixed by a couple of simple updates..
a. Update Manager upgraded the kernel from 2.6.32-27-generic to
2.6.32-28-generic. On restart, as expected, the NVidia proprietary
drivers weren't working.
b. So instead of re-using the driver file I already had (version
260.1
If you add the PPA but don't install the Wine1.2 / Wine1.3 package then
the only thing that's different on your system is a new ia32-libs
(which, in turn, merely adds libraries that aren't there on stock
Ubuntu)
If you are building Wine for testing like this, also verify that you
don't have confli
64 bit Install:
What that link basically says is to install the 1.3 PPA and get build
dependencies. For one I don't want to install wine 1.3 from the PPA as I
just have one main use system (no dev system) and I don't want to break
any stuff that works there esp. gstreamer
And that is only to get
winetricks gdiplus
a. Moved ~/.wine to ~/.wine-backup1
b. Installed Commandos 2 using the installed wine version (1.2.2) no
problems
guest@UbuntuD64Lucid:~$ wine --version
wine-1.2.2
guest@UbuntuD64Lucid:~$ wine /media/Commandos\ 2/setup.exe
wine: created the configuration directory '/home/gues
Did winetricks gdiplus help?
Also the instructions for building on 64 bit have been greatly
simplified: http://wiki.winehq.org/WineOn64bit#head-
245e8f90708da8070a4f3cbe336254c712af07e2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK I got bounced by successive git bisect bad's all the way down to
wine-1.2-1-g6f2893e
Which failed again, and then
guest@UbuntuD64Lucid:~/wine-git$ git bisect bad
6f2893ed77a52004ae947c472a3e4031d4bfbfdc is the first bad commit
commit 6f2893ed77a52004ae947c472a3e4031d4bfbfdc
n. Issued git bisect bad (23 revisions) and built (wine version
wine-1.2-23-ga93af65) using the command at (f) above
o. Ran Commandos 2, which crashed without output, so ran with winedbg again,
different backtrace produced
guest@UbuntuD64Lucid:~/wine-git$ ./wine C:\\Program\ Files\\Pyro\
S
Re installing the v1.3 PPA, I did see that at the top of the
RegressionTesting wiki but I skipped it because even if it works there I
would not use that version, but would rather stick to the stable v1.2.
Maybe I'll do that after the regression testing is done.
First time I've compiled wine so jus
First step should probably, in fact, be installing wine1.3 from
https://launchpad.net/~ubuntu-wine/+archive/ppa and seeing whether the problem
has been fixed in that yet.
If not:
The instructions for Debian should be applicable to Ubuntu -- hopefully Scott
(who packages wine for Ubuntu) should s
Will try the Regression Test bit as I don't really think the nvidia
driver is the problem..
But the Regression Test seems a bit complex..
Two questions
a. The Wine wiki states re 64-bit systems: "Ubuntu, for instance,
requires hand-linking 32-bit libraries" but the WineOn64bit linkthere
doesn't
Certainly seems like a regression in wine.
Are you able to try http://wiki.winehq.org/RegressionTesting
You could also try upgrading your graphics drivers from nvidia.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/709660
Title:
Working applications crash after update to wine 1.2.2
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
13 matches
Mail list logo
