[Bug 51885] New: Installing Dotnet Causes Recursive Cannot Parse File Errors and Terminal Spam
https://bugs.winehq.org/show_bug.cgi?id=51885 Bug ID: 51885 Summary: Installing Dotnet Causes Recursive Cannot Parse File Errors and Terminal Spam Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nekoNexus(a)protonmail.ch Distribution: --- This is an issue that's plagued me with Wine for a long while now: For some reason, I don't know why, but VERY often when I execute a Wine process in a terminal (I use Konsole and Yakuake) Wine spits out excess lines of "information" until I terminate the terminal shell. This gets particularly noticeable when doing things like installing dotnet, where there's a lot going on. For not as long but still a while, installing dotnet in particular causes it to search in my ~/.local/share/applications folder for some reason, then going through a symlink I have there, then navigating to the Wine-defined "Z drive" to scan a bunch of other locations on my PC recursively. The two issues combined causes literally endless spam in my terminal and it even spills into other process in that same terminal session, like opening a file in nano. I would log this data to a file *but I literally can't do so;* there's too many characters to log and it isn't possible for me to capture all the data. Needless to say (I kind of already said it), this can also make collecting information quite difficult for application testing for bug reporting. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51885 nekoNexus(a)protonmail.ch changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51885 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #1 from Zebediah Figura <z.figura12(a)gmail.com> --- You can redirect output to a file with "wine whatever.exe &>file". Can you please do that [ideally with a builtin program like winecfg, assuming it reproduces the bug] and paste the output here? (If it's too large to attach, try compressing it.) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51885 --- Comment #2 from nekoNexus(a)protonmail.ch --- Created attachment 70830 --> https://bugs.winehq.org/attachment.cgi?id=70830 Terminal Output Log I managed to collect the output (I had to use a different method because since the process "technically" ends when control is returned to the user, the excess stuff after that can't get logged to a file) The libgtk3-nocsd messages in the output is just a package that replaces GTK app borders with KDE Plasma Qt ones and it's throwing a fit because we're running a Winetricks with -q and WIne doesn't enforce GTK app borders in Plasma to begin with; I made a copy of the log and removed those messages in case that helps. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51885 --- Comment #3 from nekoNexus(a)protonmail.ch --- An update on this: I found that having a symlink inside of the ~/.local/share/applications directory pointing to a location with another Wine prefix causes this terminal spam. However, there's another connected issue with this I noticed: Wine tries give advice on how .desktop files are written even when they have no relevance to Wine itself, if it finds there's something it doesn't like about them. Additionally, in Konsole and Yakuake, Wine has a tendency to overflow into the user's input "line" after executing certain Wine tasks (such as running some programs, installing dotnet, running winecfg, etc) and this behavior is intrusive to the terminal (might be connected to why, in the original post, Wine output was flooding other terminal programs such as nano when it shouldn't have been) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51885 --- Comment #4 from nekoNexus(a)protonmail.ch --- Issue sill persists: can be reproduced by using vanilla Wine 7.6 and running "winetricks -q dotnet472" and attempting to cancel the transaction when the installation hangs on a failure in the Wine process. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51885 nekoNexus(a)protonmail.ch changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |printing, win64 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51885 nekoNexus(a)protonmail.ch changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |dotnet -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla