Wine problem on Kubuntu Jaunty Alpha 3

Dabore · Post by **Dabore** » Sun Jan 25, 2009 4:19 pm

Hello.

I've just installed a fresh Kubuntu Jaunty Alpha 3. I've also installed Wine package. But when trying to create my home directory with any command (wine something.exe or winecfg) the following command appears:

Code: Select all

wine: created the configuration directory '/home/dabore/.wine'
wine: Unhandled page fault on write access to 0xb87bd46c at address 0x7db33b66 (thread 000b), starting debugger...

After a while, my program or winecfg window appears, and .wine got created. Also, wineboot.exe seems to eat all my cpu and I've to kill it.

But I've more problems running applications that I know runs on wine (I've another installation of Debian unstable with same wine versions that runs just fine) and I'm sure that's the cause.

I've tried with wine 1.0.1 Jaunty package and freshly compiled wine 1.1.13, same result (I've deleted my home .wine directory every time, of course)

If someone is able to help, thanks in advance

.

austin987 · Post by **austin987** » Sun Jan 25, 2009 4:22 pm

On Sun, Jan 25, 2009 at 3:19 PM, Dabore <[email protected]> wrote:

Hello.

I've just installed a fresh Kubuntu Jaunty Alpha 3. I've also installed Wine package. But when trying to create my home directory with any command (wine something.exe or winecfg) the following command appears:

Code:
wine: created the configuration directory '/home/dabore/.wine'
wine: Unhandled page fault on write access to 0xb87bd46c at address 0x7db33b66 (thread 000b), starting debugger...

After a while, my program or winecfg window appears, and .wine got created. Also, wineboot.exe seems to eat all my cpu and I've to kill it.

But I've more problems running applications that I know runs on wine (I've another installation of Debian unstable with same wine versions that runs just fine) and I'm sure that's the cause.

I've tried with wine 1.0.1 Jaunty package and freshly compiled wine 1.1.13, same result (I've deleted my home .wine directory every time, of course)

If someone is able to help, thanks in advance .

Hmm. Can you attach the backtrace? Does
http://wiki.winehq.org/PreloaderPageZeroProblem help?

--
-Austin

Dabore · Post by **Dabore** » Sun Jan 25, 2009 4:29 pm

Hi!

Thanks for your FAST response

.

No, I already have tried that. I've also tried again, but no luck. I don't get any problem with the lower 64Ks running software, but some unhandled page exceptions on some other locations (c0000005) but I'm focusing on resolving this one first and I'm sure all will work

There is no backtrace, and the debugger doesn't start. I don't know if it's normal

Perhaps you want the WINEDEBUG=+relay log?

austin987 · Post by **austin987** » Sun Jan 25, 2009 4:33 pm

On Sun, Jan 25, 2009 at 3:29 PM, Dabore <[email protected]> wrote:

Hi!

Thanks fotr your FAST response .

No, I already have tried that. I've also tried again, but no luck. I don't get any problem with the lower 64Ks running software, but some unhandled page exceptions on some other locations (c0000005) but I'm focusing on resolving this one first and I'm sure all will work

Might be apparmor/etc.

There is no backtrace, and the debugger doesn't start. I don't know if it's normal

Sometimes...Try:

$ rm -rf ~/.wine
$ winedbg wineboot

Perhaps you want the WINEDEBUG=+relay log?

That would be next up, but if so, put on pastebin, it'd be a lot of output.

--
-Austin

Dabore · Post by **Dabore** » Sun Jan 25, 2009 4:59 pm

austin987 wrote: Sometimes...Try:

$ rm -rf ~/.wine
$ winedbg wineboot

That only returned

Code: Select all

wine: created the configuration directory '/home/dabore/.wine'
wine: Unhandled page fault on write access to 0x61f796f9 at address 0x7db29b66 (thread 000b), starting debugger...
err:process:__wine_kernel_init boot event wait timed out
WineDbg starting on pid 001a
start_process () at /tmp/wine-1.1.13/dlls/kernel32/process.c:904
0x7b879273 start_process+0x93 [/tmp/wine-1.1.13/dlls/kernel32/process.c:904] in kernel32: movl  %edi,0x0(%esp)
Unable to open file ''
Wine-dbg>

The relay log is 100Mb! I don't think pastebin will allow me to store that much

. I've pasted only a section, I hope this will suffice. If not, maybe you know any way of removing uninteresting bits.

http://pastebin.com/m8277fbc

austin987 · Post by **austin987** » Sun Jan 25, 2009 5:09 pm

On Sun, Jan 25, 2009 at 3:59 PM, Dabore <[email protected]> wrote:

austin987 wrote:
Sometimes...Try:

$ rm -rf ~/.wine
$ winedbg wineboot

That only returned

Code:
wine: created the configuration directory '/home/dabore/.wine'
wine: Unhandled page fault on write access to 0x61f796f9 at address 0x7db29b66 (thread 000b), starting debugger...
err:process:__wine_kernel_init boot event wait timed out
WineDbg starting on pid 001a
start_process () at /tmp/wine-1.1.13/dlls/kernel32/process.c:904
0x7b879273 start_process+0x93 [/tmp/wine-1.1.13/dlls/kernel32/process.c:904] in kernel32: movl %edi,0x0(%esp)
Unable to open file ''
Wine-dbg>

Do you not have write access to /tmp/?

--
-Austin

Dabore · Post by **Dabore** » Sun Jan 25, 2009 5:16 pm

austin987 wrote:On Sun, Jan 25, 2009 at 3:59 PM, Dabore <[email protected]> wrote:
austin987 wrote:
Sometimes...Try:

$ rm -rf ~/.wine
$ winedbg wineboot

That only returned

Code:
wine: created the configuration directory '/home/dabore/.wine'
wine: Unhandled page fault on write access to 0x61f796f9 at address 0x7db29b66 (thread 000b), starting debugger...
err:process:__wine_kernel_init boot event wait timed out
WineDbg starting on pid 001a
start_process () at /tmp/wine-1.1.13/dlls/kernel32/process.c:904
0x7b879273 start_process+0x93 [/tmp/wine-1.1.13/dlls/kernel32/process.c:904] in kernel32: movl %edi,0x0(%esp)
Unable to open file ''
Wine-dbg>
Do you not have write access to /tmp/?

--
-Austin

Yeah, I do. But that's pointing to the original location where I compiled wine. I don't have the source here anymore, of course. But even yesterday (when I compiled it) the error was the same.

Do you want me to remove it and try again with 1.0.1 from Jaunty repository?

austin987 · Post by **austin987** » Sun Jan 25, 2009 5:19 pm

On Sun, Jan 25, 2009 at 4:16 PM, Dabore <[email protected]> wrote:

austin987 wrote:
On Sun, Jan 25, 2009 at 3:59 PM, Dabore <[email protected]> wrote:

austin987 wrote:
That only returned

Code:
wine: created the configuration directory '/home/dabore/.wine'
wine: Unhandled page fault on write access to 0x61f796f9 at address 0x7db29b66 (thread 000b), starting debugger...
err:process:__wine_kernel_init boot event wait timed out
WineDbg starting on pid 001a
start_process () at /tmp/wine-1.1.13/dlls/kernel32/process.c:904
0x7b879273 start_process+0x93 [/tmp/wine-1.1.13/dlls/kernel32/process.c:904] in kernel32: movl %edi,0x0(%esp)
Unable to open file ''
Wine-dbg>

Do you not have write access to /tmp/?

--
-Austin
Yeah, I do. But that's pointing to the original location where I compiled wine. I don't have the source here anymore, of course. But even yesterday (when I compiled it) the error was the same.

Argh, of course. Brain needs caffeine.

Do you want me to remove it and try again with 1.0.1 from Jaunty repository?

Worth a try. Did you have compiler errors/warnings?

--
-Austin

Dabore · Post by **Dabore** » Sun Jan 25, 2009 5:43 pm

austin987 wrote:Argh, of course. Brain needs caffeine.

Don't worry

.

Do you want me to remove it and try again with 1.0.1 from Jaunty repository?
Worth a try. Did you have compiler errors/warnings?

I don't remember, but I'm sure there were a lot of warnings. But I think it's normal (like deprecated string to char* conversion and the like). Anyway, I'm removing and installing 1.0.1.

Dabore · Post by **Dabore** » Sun Jan 25, 2009 5:59 pm

Ok, all set!

I think I've pointed the cause. Here is the new errors, with backtrace.

http://pastebin.com/m640fabea

as you can see, there is some problem with libgl.so. And maybe is because I have the lastest NVidia driver (180.22) with IgnoreABI in my xorg.conf to make it work.

Maybe Wine has some problem with this, but the rest of apps doesn't seem to have any. Do you know how to fix that?

Dabore · Post by **Dabore** » Sun Jan 25, 2009 6:09 pm

Ok, fixed. I've just reinstalled the NVidia driver as said in https://bugs.launchpad.net/ubuntu/+sour ... bug/316902

Thanks a lot for your help! And sorry for wasting your time.

I'll be back with the other errors in a few minutes