Your message dated Sat, 14 Jun 2014 20:34:30 -0400
with message-id
<CANTw=mpiot7idncjq0xmzw3nktr0waxr0xybqqubbd2vwkk...@mail.gmail.com>
and subject line Re: [pkg-wine-party] Bug#691110: wine: WINEDEBUG=-all does not
shut down useless warning that corrupt output
has caused the Debian Bug report #691110,
regarding wine: WINEDEBUG=-all does not shut down useless warning that corrupt
output
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
691110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691110
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wine
Version: 1.4.1-4
Severity: normal
Hello Debian Wine Party,
I use wine to run the testsuite of software I cross-compile
with mingw. I do something like
WINEDEBUG=-all wine ./foo.exe >result 2>&1
This worked fine with wine 1.2.3-0.3.
Unfortunately with this new version, this does not work: wine
output a warning that pollute result:
Application tried to create a window, but no driver could be loaded.
Make sure that your X server is running and that $DISPLAY is set correctly.
(this come from ./dlls/user32/driver.c).
My application does not actually try to create a window, and every thing
work outside the warning.
I was expecting that WINEDEBUG=-all would shut it down, but this is not the
case.
so now I have to do
WINEDEBUG=-all wine ./foo.exe 2>&1 | tail -n +3
Cheers,
--
Bill. <[email protected]>
Imagine a large red swirl here.
--- End Message ---
--- Begin Message ---
version: 1.7.19-1
>> I was expecting that WINEDEBUG=-all would shut it down, but this is not the
>> case.
>> so now I have to do
>> WINEDEBUG=-all wine ./foo.exe 2>&1 | tail -n +3
>
> Would you mind submitting this upstream? Also things may possibly be
> better with 1.6, but I haven't tested.
>From some limited testing with 1.7.19, this seems to no longer be an issue.
Best wishes,
Mike
--- End Message ---
