http://bugs.winehq.org/show_bug.cgi?id=24569
Summary: ~/.xsession-errors filling with "fixme:tapi" messages Product: Wine Version: 1.3.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: jason.whipp@gmail.com
Running Zultys MXIE (a phone client to Zultys phone systems) I am seeing this message repeating over and over (to a tune of thousands of times) while MXIE is running:
fixme:tapi:lineGetDevCapsA (0x16ef128, 000229c2, 00020002, 00000000, 0x1a0d750): stub. fixme:tapi:lineNegotiateAPIVersion (0x16ef128, 141763, 65540, 131074, 0x1a0e81c, 0x1a0e800): stub.
Wasn't seeing this previous to 1.3.1 running Zultys MXIE client, but since the .xsessions-errors file was never an issue before, I've never looked. This is a major problem as an average session of mxie will make for a 4 gig .xsession-errors file.
As a work around, I've changed my ~/.xsession-errors to a symlink to /dev/null.
http://bugs.winehq.org/show_bug.cgi?id=24569
--- Comment #1 from Louis Lenders xerox_xerox2000@yahoo.co.uk 2010-09-29 15:54:47 CDT --- Created an attachment (id=31030) --> (http://bugs.winehq.org/attachment.cgi?id=31030) patch
does attached patch help (just quiet the fixme's)
http://bugs.winehq.org/show_bug.cgi?id=24569
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID Severity|major |minor
--- Comment #2 from Dmitry Timoshkov dmitry@codeweavers.com 2010-09-29 23:50:49 CDT --- Wine doesn't explicitly add anything to ~/.xsession-errors, all Wine output is printed to stderr. You may use WINEDEBUG=-all to workaround broken WM/ console emulator behaviour.
http://bugs.winehq.org/show_bug.cgi?id=24569
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Dmitry Timoshkov dmitry@codeweavers.com 2010-09-29 23:51:02 CDT --- Closing invalid.
http://bugs.winehq.org/show_bug.cgi?id=24569
--- Comment #4 from Jase Whipp jason.whipp@gmail.com 2010-09-30 11:10:59 CDT --- (In reply to comment #2)
Wine doesn't explicitly add anything to ~/.xsession-errors, all Wine output is printed to stderr. You may use WINEDEBUG=-all to workaround broken WM/ console emulator behaviour.
WINEDEBUG=-all is an env variable wine respects?
I don't understand the "broken WM/console emulator behavior comment...what is broken? We're talking logging from wine, not the wm or any console emulator.
http://bugs.winehq.org/show_bug.cgi?id=24569
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh@gmail.com
--- Comment #5 from Jerome Leclanche adys.wh@gmail.com 2010-09-30 11:31:49 CDT --- The real issue here is that tapi:lineGetDevCapsA and tapi:lineNegotiateAPIVersion are very verbose. xsession-errors is automatically managed to by the X server, so it's not directly Wine's fault if yours ends up being gigabytes-large.
The best you can hope for is either: - Devs making it a fixme-once (Louis' patch) - Properly implementing and unstubbing the functions - Downgrading the fixmes to warns
And meanwhile, linking to /dev/null is fine.
This should be closed as a dupe of bug 15435.
http://bugs.winehq.org/show_bug.cgi?id=24569
--- Comment #6 from Jase Whipp jason.whipp@gmail.com 2010-09-30 11:43:47 CDT --- (In reply to comment #5)
The real issue here is that tapi:lineGetDevCapsA and tapi:lineNegotiateAPIVersion are very verbose. xsession-errors is automatically managed to by the X server, so it's not directly Wine's fault if yours ends up being gigabytes-large.
The best you can hope for is either:
- Devs making it a fixme-once (Louis' patch)
- Properly implementing and unstubbing the functions
- Downgrading the fixmes to warns
And meanwhile, linking to /dev/null is fine.
This should be closed as a dupe of bug 15435.
Which is the nature of this bug. :)
Really, what I think we need is configurable *outside of compilation params* wine logging. As a user of wine, I'd like to be able to turn on and off verbose logging when needed. A simple way may be adding a simple check box to winecfg to enabling verbose logging, off by default.
So I guess what I am saying is for a technical wine user, this may not be a bug, but an enhancement request. However, for a normal user of wine, not testing, over verbose logging could be a bug considering they are not looking for logging to begin with.
http://bugs.winehq.org/show_bug.cgi?id=24569
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2010-09-30 11:50:18 CDT --- Once again: Wine doesn't write anything to ~/.xsession-errors, all Wine output is printed to stderr.
You need to find out who redirects Wine output to ~/.xsession-errors, and file a bug report to its developers.
Regarding WINEDEBUG usage refer to the user documentation, or ask on the user support forum.
http://bugs.winehq.org/show_bug.cgi?id=24569
--- Comment #8 from Jerome Leclanche adys.wh@gmail.com 2010-09-30 12:14:07 CDT --- (In reply to comment #7)
Once again: Wine doesn't write anything to ~/.xsession-errors, all Wine output is printed to stderr.
You need to find out who redirects Wine output to ~/.xsession-errors, and file a bug report to its developers.
Regarding WINEDEBUG usage refer to the user documentation, or ask on the user support forum.
IIUC, X automatically redirects stderr->xsession-errors if the program was not opened from a terminal.
http://bugs.winehq.org/show_bug.cgi?id=24569
--- Comment #9 from Austin English austinenglish@gmail.com 2010-09-30 12:32:12 CDT --- (In reply to comment #6)
Really, what I think we need is configurable *outside of compilation params* wine logging. As a user of wine, I'd like to be able to turn on and off verbose logging when needed. A simple way may be adding a simple check box to winecfg to enabling verbose logging, off by default.
It is, add 'WINEDEBUG=-all' to your environment (~/.bashrc, likely) to disable it for all apps or to the particular shortcut you're using to disable it for just that program.
http://bugs.winehq.org/show_bug.cgi?id=24569
--- Comment #10 from Jase Whipp jason.whipp@gmail.com 2010-09-30 12:37:40 CDT --- (In reply to comment #8)
(In reply to comment #7)
Once again: Wine doesn't write anything to ~/.xsession-errors, all Wine output is printed to stderr.
You need to find out who redirects Wine output to ~/.xsession-errors, and file a bug report to its developers.
Regarding WINEDEBUG usage refer to the user documentation, or ask on the user support forum.
IIUC, X automatically redirects stderr->xsession-errors if the program was not opened from a terminal.
That's my understanding as well.
I'm basically turning off a useful X log facility or disabling output for ALL wine apps which I shouldn't need to do for one chatty app. There's nothing broken in the X configuration. I still think an option in winecfg is warranted, that way a program that has too much sdout can be -all logged while others can be left alone with out creating pipe files.
And the issue of the fixme:tapi are way to numerous, I don't see how that's invalid.
http://bugs.winehq.org/show_bug.cgi?id=24569
Louis Lenders xerox_xerox2000@yahoo.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox_xerox2000@yahoo.co.uk
--- Comment #11 from Louis Lenders xerox_xerox2000@yahoo.co.uk 2010-09-30 12:40:10 CDT ---
And the issue of the fixme:tapi are way to numerous,
I'll send the patch to quiet the fixme's then (probably tomorrow though).
http://bugs.winehq.org/show_bug.cgi?id=24569
--- Comment #12 from Austin English austinenglish@gmail.com 2010-09-30 12:40:51 CDT --- (In reply to comment #10)
I'm basically turning off a useful X log facility or disabling output for ALL wine apps which I shouldn't need to do for one chatty app. There's nothing broken in the X configuration. I still think an option in winecfg is warranted, that way a program that has too much sdout can be -all logged while others can be left alone with out creating pipe files.
And the issue of the fixme:tapi are way to numerous, I don't see how that's invalid.
See bug 15435 a (long) discussion on the topic.
http://bugs.winehq.org/show_bug.cgi?id=24569
--- Comment #13 from Jase Whipp jason.whipp@gmail.com 2010-09-30 12:45:33 CDT --- (In reply to comment #9)
(In reply to comment #6)
Really, what I think we need is configurable *outside of compilation params* wine logging. As a user of wine, I'd like to be able to turn on and off verbose logging when needed. A simple way may be adding a simple check box to winecfg to enabling verbose logging, off by default.
It is, add 'WINEDEBUG=-all' to your environment (~/.bashrc, likely) to disable it for all apps or to the particular shortcut you're using to disable it for just that program.
I'll utilize this for the mxie app, thanks.
http://bugs.winehq.org/show_bug.cgi?id=24569
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |satyagowtham.k@gmail.com
--- Comment #14 from Dmitry Timoshkov dmitry@codeweavers.com 2010-10-06 10:31:23 CDT --- *** Bug 24648 has been marked as a duplicate of this bug. ***
-
wine-bugs＠winehq.org