https://bugs.winehq.org/show_bug.cgi?id=52732
--- Comment #6 from Rencer rencer@euromail.hu --- (In reply to Rafał Mużyło from comment #4)
To put in in plain text: I've read exactly what you've wrote and based on that decided that with a very high probability the problem you think you have is not the problem you actually have.
It's a REAL problem, it happening in every new Wine prefix with the new Wine version (runnig in terminal, command line, CLI), and in every existing Wine porefix that I tried to update to new Wine version. When I runnig in terminal, command line, CLI, any older Wine versions and creating a new OR just using an already existing Wine prefix, don't have this bug.
It doesn't matter what YOU decided, this thing is still happening, and this starge thing ONLY happennig with Wine. Only when I need to run a Windows-software. Everything else is working as needed in my system to run a Windows-software, only problematic is the new Wine-vesrions itself. Nothinng else.
Because of that you can't reproduce, or this, my report is the first one thatmention this bug that doesn't mean it is not real.
I already learned that if it is Wine, it can take very LONG time to even talk about it. (I had a bug a very long time that affected Wine, and that is fixed after more than 3 years, after countless of comments, contless of merging releated bug reports...) Maybe later something come up that can related to this and can be helpful to eliminate this thing.
So, this bug report is still open and real.