July 2021 - Wine-Bugs - list.winehq.org

[Bug 51546] ran a application and it gave an error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51546 mrtbryanonlinux(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu -- 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.

July 31, 2021

[Bug 51546] New: ran a application and it gave an error

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51546 Bug ID: 51546 Summary: ran a application and it gave an error Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrtbryanonlinux(a)gmail.com Distribution: --- Created attachment 70389 --> https://bugs.winehq.org/attachment.cgi?id=70389 Im trying to run Xenos64.exe for gta v and then that happened plz help tried to run a application called xenos64.exe i use it for gta v so i wined it then that happened. plz try and fix ASAP -- 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.

July 31, 2021

[Bug 5163] Microsoft Office XP 2002 installer reports error 25003 (installation source corrupted), custom action 'CADpc' returns 1603

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=5163 Mark <themh(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |themh(a)gmx.de --- Comment #104 from Mark <themh(a)gmx.de> --- @Anastasius Focht: This analysis from 2008 was a blast to read. Very educational. Meanwhile, since the fix to this bug is in staging, I managed to install Office 2002 almost completely working with this method. I thought I might share it for others who stumble upon this, even though Office 2002 today has probably rather niche usecases. 1. I used a 32bit wineprefix with Wine 6.11-staging, without installing mono or gecko. I used PlayOnLinux for easy installation, but you could probably compile it yourself, too. 2. Install Access, Word, Excel and Powerpoint with the installer. De-select all autocorrection options in the installer. They won't install properly (probably another bug) and if you don't de-select them, Office keeps asking to insert the installation medium at every start. 3. I then copied the prefix in my default wine environment, which is currently 5.0-stable, ran winecfg and changed the mode to Windows XP. It probably runs in Windows 7 mode, to, but since it's Office XP you might as well put it to the proper OS version. 4. The installation is now complete. Finally, I manually created 4 launchers for the progams via alacarte (you can google that if you're unfamiliar with menu editing) The launchers have to look similar to that: env WINEPREFIX="/home/username/.wine-mso" wine-stable /home/username/.wine-mso/drive_c/Program\ Files/Microsoft\ Office/Office10/WINWORD.EXE -- 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.

July 31, 2021

[Bug 51531] DrMingw problem

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51531 --- Comment #4 from Vladimir Koković <vladimir.kokovic(a)gmail.com> --- (In reply to Bernhard Übelacker from comment #3) > Hello, you added the path to your system.reg in the first message. > From that I assume you installed drmingw with such an environment? > WINEPREFIX=/mnt/WD-Elements-25A1/src/wine-git/install64 > > But ispp64-llvm-mingw-start.sh changes that to: > WINEPREFIX="/mnt/WD-Elements-25A1/ispp-sql-mingw-64/windows-10" > > Therefore, for the wine processes started afterwards, I guess the AeDebug > setting from the system.reg below this wineprefix matters. > Is DrMingw installed to this wineprefix too? > > Another thing could be, what filesystem is the mount /mnt/WD-Elements-25A1? It's my fault, I apologize to everyone, but if I put export wineprefix=/mnt/wd-elements-25a1/src/wine-git/install64, Wine don't do start program ! blkid /dev/sdd1: UUID="423b17a7-7cc7-48eb-bbbb-3646b13d57b1" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Elements" PARTUUID="10f9b972-3188-4b46-a2d4-a6d647f313f4" mount /dev/sdd1 on /mnt/WD-Elements-25A1 type ext4 (rw,noatime) -- 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.

July 31, 2021

[Bug 40613] Multiple applications require UAC implementation to run installer/app as a normal user instead of administrator (WhatsApp Desktop, Smartflix, Squirrel Installers, OneDrive)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=40613 someuniquename(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |someuniquename(a)gmail.com -- 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.

July 31, 2021

[Bug 51531] DrMingw problem

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51531 --- Comment #3 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- Hello, you added the path to your system.reg in the first message. >From that I assume you installed drmingw with such an environment? WINEPREFIX=/mnt/WD-Elements-25A1/src/wine-git/install64 But ispp64-llvm-mingw-start.sh changes that to: WINEPREFIX="/mnt/WD-Elements-25A1/ispp-sql-mingw-64/windows-10" Therefore, for the wine processes started afterwards, I guess the AeDebug setting from the system.reg below this wineprefix matters. Is DrMingw installed to this wineprefix too? Another thing could be, what filesystem is the mount /mnt/WD-Elements-25A1? -- 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.

July 31, 2021

[Bug 51545] New: STDOUT lost from a forked program on Cygwin/MSYS2

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51545 Bug ID: 51545 Summary: STDOUT lost from a forked program on Cygwin/MSYS2 Product: Wine Version: 6.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wineserver Assignee: wine-bugs(a)winehq.org Reporter: megastallman(a)gmail.com Distribution: --- Hi guys! This bug is a continuation of https://bugs.winehq.org/show_bug.cgi?id=50705 that is actually fixed and looks much like an ancient https://bugs.winehq.org/show_bug.cgi?id=18479 , so - probably a regression. I'm using tha latest Wine-staging build on Xubuntu. Trying to run Cygwin and MSYS2. But for some reason, bash sessions lose STDOUT. Nevertheless, builtins work fine from both bash and wineconsole. I can finally call 'ls' or 'uname -a' from wineconsole. I get the output without closing the shell. As for bash session - 'ls' and 'uname' just output nothing. 'uname -a > qqq' results in an empty file. Builtins, like 'pwd' or 'pwd > qqq' - work fine. Same for bash scripting, STDOUT is lost. -- 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.

July 31, 2021

[Bug 50705] Cygwin64 on Wine64-staging closes the console after every command.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=50705 megastallman <megastallman(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from megastallman <megastallman(a)gmail.com> --- Actally this particular problem is resolved. So, I'll file new bugreports for new bugs. Thanks guys! -- 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.

July 31, 2021

[Bug 51061] Solid Edge 2021 Academic Edition: can't create new file

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51061 --- Comment #9 from Aritz Erkiaga <aerkiaga3(a)gmail.com> --- Reproduced on 6.14-staging -- 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.

July 31, 2021

[Bug 51060] Solid Edge 2021 Academic Edition: can't open any file

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=51060 --- Comment #9 from Aritz Erkiaga <aerkiaga3(a)gmail.com> --- Reproduced on 6.14-staging -- 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.

July 31, 2021