https://bugs.winehq.org/show_bug.cgi?id=52172
Bug ID: 52172 Summary: Guild Wars 2 spams "0150:fixme:msctf:KeystrokeMgr_TestKey{Up,Down} STUB" Product: Wine Version: 6.23 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msctf Assignee: wine-bugs@winehq.org Reporter: lingm+winebz@posteo.org Distribution: ---
When playing Guild Wars 2, for every key press these two fixmes get printed: 0150:fixme:msctf:KeystrokeMgr_TestKeyDown STUB:(00000000022C5840) 0150:fixme:msctf:KeystrokeMgr_TestKeyUp STUB:(00000000022C5840)
While walking (with WASD) the KeyDown one gets printed continuously, which is especially annoying.
Best I can tell there's no related problem, so just silencing these messages would work for me.
https://bugs.winehq.org/show_bug.cgi?id=52172
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #1 from joaopa jeremielapuree@yahoo.fr --- FIXME are not bugs. If messages are annoying for you, you can do that:
wine foo.exe&>/dev/null.
Can an administrator close this bug as INVALID?
https://bugs.winehq.org/show_bug.cgi?id=52172
--- Comment #2 from LingM lingm+winebz@posteo.org --- Silencing all output kind of defeats the point of being able to see interesting messages. If that was my goal, I'd just stick to Lutris and not have to look at the console at all.
Plus, there's plenty precedent of reporting noisy fixmes: bug 30575, bug 35349, bug 44746, bug 47367, bug 48300, ...
https://bugs.winehq.org/show_bug.cgi?id=52172
--- Comment #3 from Paul Gofman pgofman@codeweavers.com --- I think WINEDEBUG=-all is even better as besides stopping the unwanted output it also avoids the overhead for formatting and writing those messages. And yes, there is probably nothing to fix here (besides maybe implementing that functionality but that’s not what this report concerns).
https://bugs.winehq.org/show_bug.cgi?id=52172
Paul Gofman pgofman@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |pgofman@codeweavers.com
--- Comment #4 from Paul Gofman pgofman@codeweavers.com --- If you need to analyze the log you can redirect the output to file and filter unwanted messages. WINEDEBUG=-msctf should also work. Making the log to output things interesting for you and only those by default doesn’t look feasible.