https://bugs.winehq.org/show_bug.cgi?id=49867
Bug ID: 49867 Summary: Support /var/log Product: Wine Version: 5.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: acroq3@gmail.com Distribution: ---
Store logs in /var/log as primary option
https://bugs.winehq.org/show_bug.cgi?id=49867
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #1 from Zebediah Figura z.figura12@gmail.com --- Wine does not store logs by default anywhere; it's up to the user to decide whether to redirect stdout to a file, if at all.
Can you give justification for this?
https://bugs.winehq.org/show_bug.cgi?id=49867
--- Comment #2 from N acroq3@gmail.com --- Obvious and very frequent malfunctions?..
https://bugs.winehq.org/show_bug.cgi?id=49867
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- (In reply to N from comment #2)
Obvious and very frequent malfunctions?..
What?
https://bugs.winehq.org/show_bug.cgi?id=49867
--- Comment #4 from N acroq3@gmail.com --- 95% of wine bugs and performance issues aren't reported in this bugtracker
https://bugs.winehq.org/show_bug.cgi?id=49867
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- (In reply to N from comment #4)
95% of wine bugs and performance issues aren't reported in this bugtracker
Can you justify that statement?
https://bugs.winehq.org/show_bug.cgi?id=49867
--- Comment #6 from N acroq3@gmail.com --- What do you want for me? I was "using" wine for last 6 months with more than 100 programs.
Who are you?
https://bugs.winehq.org/show_bug.cgi?id=49867
--- Comment #7 from Zebediah Figura z.figura12@gmail.com --- (In reply to N from comment #6)
What do you want for me? I was "using" wine for last 6 months with more than 100 programs.
Justification for your statements, thorough explanation of your proposals and what exact behaviour they would entail, thorough explanations as to why the things you're proposing are in fact good ideas, and, frankly, complete sentences. Coming to bugzilla and posting a bunch of sentence fragments for things that look tailored to your own use cases is not a good way to request any change in Wine.
https://bugs.winehq.org/show_bug.cgi?id=49867
--- Comment #8 from N acroq3@gmail.com --- If you need a book instead of "Store logs in /var/log as primary option" that's not MY problem.
If you don't see bugs and performance issues with current Wine?..
My advice: go outside and try to USE Wine with slightly older computers.
https://bugs.winehq.org/show_bug.cgi?id=49867
--- Comment #9 from Zebediah Figura z.figura12@gmail.com --- (In reply to N from comment #8)
If you need a book instead of "Store logs in /var/log as primary option" that's not MY problem.
Well, it kind of is, because otherwise your bugs will be ignored or closed as INVALID.
If you don't see bugs and performance issues with current Wine?..
I certainly have seen plenty of bugs, and bug reports, with Wine. It's not clear to me at all, however, how changing a non-default or even default output location for logs would change anything.
Allow me to explain further:
Currently, if Wine is run from the terminal, it will output messages to stderr (and thus, if stderr is not redirected, the terminal itself). This makes messages pretty much maximally visible to the user, at the expense of possibly overrunning the terminal buffer and discarding earlier output.
If Wine is not run from the terminal, it will output no messages at all, which does in fact improve performance.
What benefit could come from changing either of these to output to a specific, fixed file location, by default, or in addition?
https://bugs.winehq.org/show_bug.cgi?id=49867
--- Comment #10 from N acroq3@gmail.com --- Bugs and performance issues are common and you need to "enable" them manually?
In my case: 5% programs work better than expected 20-30% programs work as intended 25% programs run slow 40-50% don't start
https://bugs.winehq.org/show_bug.cgi?id=49867
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC| |o.dierick@piezo-forte.be
--- Comment #11 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
(In reply to N from comment #10)
Bugs and performance issues are common and you need to "enable" them manually?
Wine has default output that doesn't need to be enabled. Non-default debugging channels must be enabled manually because they have an impact on performance that is undesirable for normal usage.
Additionally to what Zebediah Figura said, writing in /var/log requires root permission by default on most systems. Wine MUST NOT run as root, so writing to /var/log would require setting up complex file access to work around it. That fill access setup operation itself requires administrative privileges so it would have to be performed externally anyway (manually or at the packaging level, which is outside the scope of Wine). That makes it impossible to support /var/log from inside Wine.
Marking invalid.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49867
N acroq3@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED
--- Comment #12 from N acroq3@gmail.com --- I have trouble to use such output in e.g. Lutris https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a._terminal...
Store them in non-root directory for logs?..
https://bugs.winehq.org/show_bug.cgi?id=49867
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID
https://bugs.winehq.org/show_bug.cgi?id=49867
N acroq3@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED
--- Comment #13 from N acroq3@gmail.com --- Same about Steam.
https://bugs.winehq.org/show_bug.cgi?id=49867
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID
https://bugs.winehq.org/show_bug.cgi?id=49867
--- Comment #14 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to N from comment #12)
I have trouble to use such output in e.g. Lutris
(In reply to N from comment #13)
Same about Steam.
Hello,
Steam and Lutris install their own customized version of Wine, wrapped in their specific tools. If you want to control how they store logs or suggest changes to that, you'll have to ask them about it. WineHQ.org doesn't provide support for other people's projects.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49867
--- Comment #15 from N acroq3@gmail.com --- Lutris can work with system wine.
https://bugs.winehq.org/show_bug.cgi?id=49867
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #16 from Austin English austinenglish@gmail.com --- (In reply to N from comment #15)
Lutris can work with system wine.
It's also a wine wrapper (i.e., it can handle logging in a generic way for vanilla wine, lutris, staging, etc.).
-
WineHQ Bugzilla