Hi,
I had the same problems with this. I was just missing some sound
drivers. Maybe renaming some wine*drv*so would do the trick...
Scott Ritchie a écrit :
Hi,
Could both of you please try:
wineserver -k
killall -9 wine-preloader
This should stop all old versions of wine that may still be running
Then:
wine --version
which wine
If the which command comes up with something in /usr/local/bin, that
means it's running the version you compiled and not the one in the
package. Also if you could post more about your platform it could be
useful.
Thanks,
Scott Ritchie
On Sat, 2006-08-12 at 13:57 -0400, Colin Kern wrote:
I have Ubuntu 6.06, and I'm using Wine 0.9.18 with no problem. I
built it myself with a patch for World of Warcraft, so maybe that's
why it works. I noticed that it updated the package to 0.9.19 this
morning, but "wine --version" still says 0.9.18.
Colin
On 8/12/06, Gavin Hamill <gdh@xxxxxxxxxxxxxx> wrote:
Hi :)
I'm having enormous probs with the Budgetdedicated APT repo on Ubuntu
dapper... 0.9.17 works a treat, but 0.9.18 and 0.9.19 immediately call
the debugger on /any/ app, even winecfg + /usr/bin/notepad..
I've tried deleting my .wine dir, and always ensure there is no
wineserver hanging around, but always to the same end effect:
gdh@plip:~$ rm -r .wine
gdh@plip:~$ notepad
wine: creating configuration directory '/home/gdh/.wine'...
wine: Unhandled page fault on write access to 0x003ffd80 at address
0x60a7dc0e (thread 0009), starting debugger... wine: Unhandled page
fault on write access to 0x003ffd80 at address 0x7e798c0e (thread
000b), starting debugger... WineDbg starting on pid 0x8 wine: Unhandled
page fault on write access to 0x003ffd80 at address 0x7e79bc0e (thread
000d), starting debugger... Unhandled exception: page fault on write
access to 0x003ffd80 in 32-bit code (0x60a7dc0e). Register dump:
CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:0000 EIP:60a7dc0e
ESP:0033e768 EBP:0033ead0 EFLAGS:00210206( - 00 - RIP1)
EAX:0033ec00 EBX:60a8419c ECX:60015778 EDX:003fffff ESI:003ffd80
EDI:600157a0 Stack dump:
0x0033e768: 0033e7a8 60a83a28 0033e7a8 0033e7a4
0x0033e778: 00000000 00000000 00000000 00000000
0x0033e788: 0000dd24 0000dd24 00000005 600157a0
0x0033e798: 60a84374 60a84378 0033ea28 0000002a
0x0033e7a8: 53203123 5020504d 4d454552 54205450
0x0033e7b8: 41207568 33206775 3a333020 323a3331
fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for c0000119
Backtrace:
=>1 0x60a7dc0e pthread_initialize+0x272 in libpthread.so.0 (0x60a7dc0e)
2 0x60a8399f __do_global_ctors_aux+0x23 in libpthread.so.0
(0x60a8399f) 3 0x60a79a7e _init+0x12 in libpthread.so.0 (0x60a79a7e)
4 0x6000b2ab in ld-linux.so.2 (+0xb2ab) (0x6000b2ab)
5 0x6000b3f4 in ld-linux.so.2 (+0xb3f4) (0x6000b3f4)
WineDbg starting on pid 0xc
Unhandled exception: page fault on write access to 0x003ffd80 in 32-bit
code (0x7e79bc0e). Register dump:
CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:0000
EIP:7e79bc0e ESP:0034e768 EBP:0034ead0 EFLAGS:00210286( - 00
-RISP1) EAX:0034ec00 EBX:7e7a219c ECX:b7f80778 EDX:003fffff
ESI:003ffd80 EDI:b7f807a0
Stack dump:
0x0034e768: 0034e7a8 7e7a1a28 0034e7a8 0034e7a4
0x0034e778: 00000000 00000000 00000000 00000000
0x0034e788: 0000dd24 0000dd24 00000005 b7f807a0
0x0034e798: 7e7a2374 7e7a2378 0034ea28 0000002a
0x0034e7a8: 53203123 5020504d 4d454552 54205450
0x0034e7b8: 41207568 33206775 3a333020 323a3331
fixme:ntdll:RtlNtStatusToDosErrorNoTeb no mapping for c0000119
Backtrace:
=>1 0x7e79bc0e pthread_initialize+0x272 in libpthread.so.0 (0x7e79bc0e)
2 0x7e7a199f __do_global_ctors_aux+0x23 in libpthread.so.0
(0x7e7a199f) 3 0x7e797a7e _init+0x12 in libpthread.so.0 (0x7e797a7e)
4 0xb7f762ab in ld-linux.so.2 (+0xb2ab) (0xb7f762ab)
5 0xb7f763f4 in ld-linux.so.2 (+0xb3f4) (0xb7f763f4)
6 0x602215c6 in libc.so.6 (+0xea5c6) (0x602215c6)
7 0x6000b106 in ld-linux.so.2 (+0xb106) (0x6000b106)
8 0x60221c29 _dl_open+0x98 in libc.so.6 (0x60221c29)
9 0x6024fca9 GLIBC_2+0xca9 in libdl.so.2 (0x6024fca9)
... and so on for what seems like an eternity.. is this a known-issue?
Like I say 0.9.17 works fine but of course I'd like to stay up to date
with the project's progress :)
Cheers,
Gavin.
_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users
_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users
_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.org/mailman/listinfo/wine-users
