October 2020 - Wine-Bugs - list.winehq.org

[Bug 40571] New: Google SketchUp 13 crashes every other time when printing
by wine-bugs＠winehq.org Feb. 12, 2021

Feb. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=40571 Bug ID: 40571 Summary: Google SketchUp 13 crashes every other time when printing Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ivan.t7ko(a)gmail.com Distribution: --- Google SketchUp 2013 (13.0.4812). Wine 1.7.18 Ubuntu 14.04 Open a model, send it to printer (physical over CUPS or PDF over CUPS). In most of the cases, first attempt succeeds. But in most of the cases, second attempt crashes the app. -- 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.

2 3

[Bug 40008] New: OllyDbg hangs when trying to pause debuggee
by wine-bugs＠winehq.org Feb. 12, 2021

Feb. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=40008 Bug ID: 40008 Summary: OllyDbg hangs when trying to pause debuggee Product: Wine Version: 1.9.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: b7.10110111(a)gmail.com Distribution: --- To reproduce: 1. Launch OllyDbg 2. Press F3, choose some exe file, e.g. Test.exe in OllyDbg distribution 3. Press Ctrl+E 4. In the newly-opened dialog enter in HEX+00 field: EBFE 5. Press F9 6. Choose in menu Debug->Pause 7. See OllyDbg freeze. -- 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.

2 5

[Bug 22242] New: Paint.NET 3.5.4 installer fails with mono
by wine-bugs＠winehq.org Feb. 12, 2021

Feb. 12, 2021

http://bugs.winehq.org/show_bug.cgi?id=22242 Summary: Paint.NET 3.5.4 installer fails with mono Product: Wine Version: 1.1.41 Platform: x86 URL: http://www.getpaint.net/download.html OS/Version: Linux Status: NEW Keywords: dotnet, download, Installer Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: madewokherd(a)gmail.com The Paint.NET installer fails with mono installed (via winetricks mono26). The current blocking issue is the lack of ngen.exe. I sent a patch for that: http://www.winehq.org/pipermail/wine-patches/2010-April/086832.html After that, it apparently fails due to a FileNotFound error, which I suspect is caused by a program's inability to detect its own path. We should switch mscoree.dll to using the mono embedding api rather than calling mono.exe, so that the GetCommandLine and GetModuleFileName(0) point to the program being executed. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 19

[Bug 40837] New: error when opening KSafe.exe
by wine-bugs＠winehq.org Feb. 12, 2021

Feb. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=40837 Bug ID: 40837 Summary: error when opening KSafe.exe Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rico_server(a)live.co.uk Distribution: --- Created attachment 54810 --> https://bugs.winehq.org/attachment.cgi?id=54810 Wine crashes when I opening KSafe.exe Wine crashes when I opening KSafe.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.

2 5

[Bug 28927] New: Wabbitcode don't launch
by wine-bugs＠winehq.org Feb. 12, 2021

Feb. 12, 2021

http://bugs.winehq.org/show_bug.cgi?id=28927 Bug #: 28927 Summary: Wabbitcode don't launch Product: Wine Version: 1.3.31 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: poubellepasfraiche(a)gmail.com Classification: Unclassified Installing wabbitcode from it's .msi file (http://wabbit.codeplex.com/releases/view/45275#DownloadId=121815) the installation works, then I launch the prog using the wine menu (wine --> programmes --> Revsoft --> Wabbitcode) It showsthe error "Paramètres non valides" (also in english : invalid parameters), and then after clicking "ok", shows the error "aucun programme Windows n'est configuré pour ouvrir ce type de fichier" (in english : "no windows program is configured to open this type of file"). I've installed the windows version of mono using wine, relaunching the app does the same. Don't know how to install mono on ubuntu, but it should be already installed by default that's why I think it's a wine bug, 'cause it don't detect the default installed mono and the windows version of mono. If not, please help me ! -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 9

[Bug 23094] New: R6034 runtime error during AVATAR Demo install
by wine-bugs＠winehq.org Feb. 12, 2021

Feb. 12, 2021

http://bugs.winehq.org/show_bug.cgi?id=23094 Summary: R6034 runtime error during AVATAR Demo install Product: Wine Version: 1.2-rc2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: eg.galano(a)gmail.com CC: dank(a)kegel.com Towards the end of James Camerons AVATAR The Game Demo installation, It installs the VC Runtime Library. At this point an error pops up stating: R6034: An application has made an attempt to load the C Runtime library incorrectly. It does not effect the game and you are able to run it despite this error. To get the message to not appear during install doing: winetricks vcrun2005 does the trick. The game is downloadable from: http://www.bigdownload.com/games/james-camerons-avatar-the-game/pc/james-ca… -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 16

[Bug 49849] New: system("CLS") don't work
by WineHQ Bugzilla Feb. 12, 2021

Feb. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=49849 Bug ID: 49849 Summary: system("CLS") don't work Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: antoni.przybylik(a)wp.pl Distribution: --- In my Windows console program, I'm using system("CLS") to clear the screen. Unfortunately, when I try to run this program with wine, the screen doesn't clear. This isn't this program specific bug. system("CLS") doesn't work in any of my programs. I don't think an attachment is needed. The bug is easy to reproduce. -- 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.

1 4

[Bug 39993] New: OllyDbg fails to change some registers
by wine-bugs＠winehq.org Feb. 12, 2021

Feb. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=39993 Bug ID: 39993 Summary: OllyDbg fails to change some registers Product: Wine Version: 1.9.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: b7.10110111(a)gmail.com Distribution: --- If you try to set some registers in OllyDbg while debugging an application, it'll reset them to original values after single step. This must mean that its write request has failed. To reproduce: 1. Run OllyDbg (2.x) 2. File->Open, choose any PE file, e.g. Test.exe from OllyDbg distribution 3. Press space bar, assemble something like `dw 0xfeeb` to make sure no registers are changed on single step 4. Try to change any of the following registers (others work correctly): * ST2 or any other FPU data register * FST * FCW * MXCSR * data register tags via right clicking on "empty" and selecting "zero" 5. Single step (pressing F7) 6. See the changed registers return to original values, i.e. fail to actually change -- 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.

2 10

[Bug 42353] New: OllyDbg Step In on a "jump to self" instruction never stops if it' s the first instruction executed by debuggee
by wine-bugs＠winehq.org Feb. 12, 2021

Feb. 12, 2021

https://bugs.winehq.org/show_bug.cgi?id=42353 Bug ID: 42353 Summary: OllyDbg Step In on a "jump to self" instruction never stops if it's the first instruction executed by debuggee Product: Wine Version: 2.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: b7.10110111(a)gmail.com Distribution: --- To reproduce 1. Launch OllyDbg (tested on 2.01) 2. Open an application, e.g. Test.exe coming in the OllyDbg distribution 3. After it loads, press <Space>, then in Assemble dialog type dw 0xfeeb and press <Enter> (or click Assemble button). This should assemble a `jmp short <ModuleEntryPoint>` instruction. 4. Close Assemble dialog 5. Press F7 (shortcut for Step In) 6. See that right-bottom corner of the window (right-hand side of status bar) has "Step in" text, which never switches back to Paused. This result is wrong: the Step In action should set TF in EFLAGS, so that next pass of control to debuggee will trap after executing one instruction. In Windows XP OllyDbg gets control back immediately after pressing F7, while in Wine this never happens at all with `jmp short $` instruction unless EIP changes. The same happens if instead of `EB FE` instruction you use `E9 FB FF FF FF`, which is `jmp near $`. Note that if you press F7 before step 3, everything works as expected. -- 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.

2 6

[Bug 27248] New: cannot unpack *.crx (extensions or themes) in Chrome
by wine-bugs＠winehq.org Feb. 12, 2021

Feb. 12, 2021

http://bugs.winehq.org/show_bug.cgi?id=27248 Summary: cannot unpack *.crx (extensions or themes) in Chrome Product: Wine Version: 1.3.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Created an attachment (id=34835) --> (http://bugs.winehq.org/attachment.cgi?id=34835) log: unpack crx file with chrome 1. Download the Chrome installer from http://www.google.com/chrome?platform=win&hl=en 2. make sure bug 14864 is fixed, install Chrome: wine-1.3.20-230-g456e48e $ wine ChromeSetup.exe 3. start chrome with --no-sandbox == without --no-sandbox, chrome can not open any web site. is this a know bug? or should I submit a separate bug? == $ wine chrome.exe --no-sandbox 4. open https://chrome.google.com/webstore/detail/faamegfkmmdnkpdipihbehibalfjpmpk , install the theme package . then there will be a message box says: Can not unpack extension. To safely unpack an extension, there must be a path to your profile directory that starts with a drive letter and does not contain a junction, mount point, or symlink. No such path exists for your profile. full log is attached . -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

2 23