Bug#332545: Re: Bug#332545: Wine output

2005-10-09 Thread Marc Haber
On Sun, Oct 09, 2005 at 08:26:35AM +0200, Marc Haber wrote: > I confirm that the bug is 100 % reproducible on a freshly booted > system with 1 GB RAM and 2 GB swap. Seems to be fixed for me in 0.0.20050930-1. My (one) wine application runs fine now. Greetings Marc -- ---

Bug#332545: Wine output

2005-10-08 Thread Marc Haber
On Sat, Oct 08, 2005 at 10:29:10PM -0400, Ove Kaaven wrote: > Bas Kloet wrote: > >I've got the exact same problem and ran wine with "+x11drv,+bitmap,+seh" > >for you and saved it to a log file. It is > 15000 lines so I didn't want > >to paste it in this mail, but I put it online at: > >http://newto

Bug#332545: Wine output

2005-10-08 Thread Ove Kaaven
Bas Kloet wrote: I've got the exact same problem and ran wine with "+x11drv,+bitmap,+seh" for you and saved it to a log file. It is > 15000 lines so I didn't want to paste it in this mail, but I put it online at: http://newton.luon.net/~bas/Wine_debug.log It shows that at some point, it's creat

Bug#332545: Wine output

2005-10-08 Thread Bas Kloet
I've got the exact same problem and ran wine with "+x11drv,+bitmap,+seh" for you and saved it to a log file. It is > 15000 lines so I didn't want to paste it in this mail, but I put it online at: http://newton.luon.net/~bas/Wine_debug.log I tried running wine with WINEDEBUG=all, but the logfile gr