October 2018 - Wine-bugs - list.winehq.org

[Bug 45787] New: Regession Steam throws exception at start up
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=45787 Bug ID: 45787 Summary: Regession Steam throws exception at start up Product: Wine Version: 3.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: zzhang(a)codeweavers.com Distribution: --- Created attachment 62248 --> https://bugs.winehq.org/attachment.cgi?id=62248 console log e215d070cfc5882fee5c2b4b6c3ce7ab71a18c6e is the first bad commit commit e215d070cfc5882fee5c2b4b6c3ce7ab71a18c6e Author: Fabian Maurer <dark.shadow4(a)web.de> Date: Thu Aug 16 07:01:11 2018 +0200 kernel32: In UpdateProcThreadAttribute handle PROC_THREAD_ATTRIBUTE_MITIGATION_POLICY. Needed for x32 win7 chrome and chromium. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=45648 Signed-off-by: Fabian Maurer <dark.shadow4(a)web.de> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 87bf6b7e838e356b28a1d61b024b138c081613cd f03d9c56a2bbd05f0399598f4d39b7a2b95b181e M dlls :040000 040000 4c3e21b432ef05052e57e9da003c8084b7d25eab a566459833fffc00e9d3cdd7577a89a1993952ef M include -- 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 9

[Bug 33760] New: Jagged edges on most text and art in the Touhou 14 demo
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=33760 Bug #: 33760 Summary: Jagged edges on most text and art in the Touhou 14 demo Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: murela_alba(a)abv.bg Classification: Unclassified Created attachment 44705 --> http://bugs.winehq.org/attachment.cgi?id=44705 windows 7 main menu 960x720 When running the "Touhou 14 ~ Double Dealing Character" demo (ver 0.01a) on any resolution other than the highest (1280x960), pretty much all text displays varying degrees of aliasing. Same goes for the edges of all the 2D art and UI elements from the loading screen, to the main menu, to the game proper. Here's the title screen on windows 7 in 960x720 (windowed). -- 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.

1 17

[Bug 31687] New: DYMO Stamps can't connect to its server
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

http://bugs.winehq.org/show_bug.cgi?id=31687 Bug #: 31687 Summary: DYMO Stamps can't connect to its server Product: Wine Version: 1.5.12 Platform: x86 URL: http://sites.dymo.com/Promotions/Pages/DYMOStamps.aspx ?locale=enUS OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Depends on: 31685, 31686 Classification: Unclassified Created attachment 41656 --> http://bugs.winehq.org/attachment.cgi?id=41656 WINEDEBUG=crypt,chain,context,secur32 Install the app. You'll need native gdiplus for bug 31686. After that, you can get native hid, for bug 31685. I also installed dotnet20, to verify that it wasn't a mscoree fixme to blame, but the problem happens either way. Start it up, and it asks for your credentials. Put them in, and click next. That gives an error: The remote certificate is invalid according to the validation procedure. terminal output doesn't show much relevant. Tried native wininet/winhttp, which then in turns shows a few fixme's for crypt32/secur32/winsock. If you add in native crypt32, you get: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. and with native secur32 as well: The requested security package is not supported. Not sure what to try next. The initial problem seems to indicate crypt32 or secur32, so hopefully this log will help: WINEDEBUG=crypt,chain,context,secur32 -- 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.

1 9

[Bug 37010] New: DYMO Stamps "Unable to connect to postage transaction server" with wine-mono
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=37010 Bug ID: 37010 Summary: DYMO Stamps "Unable to connect to postage transaction server" with wine-mono Product: Wine Version: 1.7.23 Hardware: x86 URL: http://sites.dymo.com/Promotions/Pages/DYMOStamps.aspx ?locale=enUS OS: Linux Status: NEW Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Depends on: 31686 Follow up to bug 31687. You'll need native gdiplus for bug 31686. Optionally, apply https://source.winehq.org/patches/data/105843. The app installs fine, and with native gdiplus, starts up. But when you try to login, the application cannot connect to the server. Terminal shows one mscoree fixme: fixme:mscoree:ConfigFileHandler_startElement Unknown element L"configSections" in state 2 With native dotnet20, it will attempt to connect, then fails with 'This account is not active'. Trying to login via the website shows the same problem, so that's okay. But wine-mono should fail the same way. I'm using an archived installer: austin(a)aw25 ~/oldbugs/31687 $ sha1sum DYMOstampsWebSetup.exe 6f96fbdc9806effa499edba7e89329534b5901a7 DYMOstampsWebSetup.exe austin(a)aw25 ~/oldbugs/31687 $ du -h DYMOstampsWebSetup.exe 3.5M DYMOstampsWebSetup.exe the current version of the program appears to have other .Net/Mono issues -- 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 8

[Bug 45408] New: Wine crashes on d3d device init
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=45408 Bug ID: 45408 Summary: Wine crashes on d3d device init Product: Wine-staging Version: 3.11 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mrx(a)hcc.im CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Created attachment 61724 --> https://bugs.winehq.org/attachment.cgi?id=61724 trace with WINEDEBUG=+all When I try to run any programs which needs d3d, wine-staging would crash on wined3d_device_init_gdi. The machine is MacBook Pro 15-inch 2017 running macOS 10.13.2, with Intel HD Graphics 630 and Radeon Pro 650. Using wine-staging with upstream commit 8686448. I've tried to capture the full trace with WINEDEBUG=+all and the last few lines before crash are in trace.log file. -- 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 8

[Bug 39350] New: Alone in the Dark: The New Nightmare (GOG.com) hangs on start when WRITECOPY enabled
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=39350 Bug ID: 39350 Summary: Alone in the Dark: The New Nightmare (GOG.com) hangs on start when WRITECOPY enabled Product: Wine-staging Version: unspecified Hardware: x86 URL: http://www.gog.com/game/alone_in_the_dark_the_new_nigh tmare OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- I have this problem with the GOG.com version of the game, but can't reproduce it with the original demo version. After starting the game with alone4.exe, it switches screen resolution then hangs with an empty black screen and 100% CPU usage. Plain terminal output doesn't show anything. The game starts properly when STAGING_WRITECOPY variable is unset. wine-1.7.51-225-g3966aff Fedora 22 32-bit -- 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 6

[Bug 45869] New: Crackling sound With PulseAudio
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=45869 Bug ID: 45869 Summary: Crackling sound With PulseAudio Product: Wine-staging Version: 3.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ahmed.com(a)aol.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 62367 --> https://bugs.winehq.org/attachment.cgi?id=62367 wine.log My laptop produces crackling sound everytime I use Wine, and that happens with all the games not a specific game. What I've tried: /etc/pulse/default.pa load-module module-udev-detect tsched=0 ignore_dB=1 /etc/pulse/daemon.conf ; realtime-priority = 9 ; flat-volumes = no ; default-fragments = 2 ; default-fragment-size-msec = 125 PULSE_LATENCY_MSEC=60 Winetricks ==> change settings ==>> sound=alsa But no difference at all. I added a wine log using: WINEDEBUG=+dsound,+pulse,+alsa wine .⁄witcher.exe &>wine.log System info : Distro: Manjaro Linux Desktop: KDE Plasma 5.13.5 Kernel: 4.14.70-1 System: HP ProBook 450 G1 Sound device: Intel 8 Series/C220 Series High Definition Audio Audio driver: snd_hda_intel -- 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 2

[Bug 45222] New: How do I remove my WineHQ Bugzilla Account
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=45222 Bug ID: 45222 Summary: How do I remove my WineHQ Bugzilla Account Product: WineHQ Bugzilla Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: rexax007(a)gmail.com CC: austinenglish(a)gmail.com Distribution: --- How do I remove my WineHQ Bugzilla Account -- 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 45201] New: "Task Lists" shows "Wine 2.0"
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=45201 Bug ID: 45201 Summary: "Task Lists" shows "Wine 2.0" Product: WineHQ Bugzilla Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: trivial Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: manzisam(a)gmail.com CC: austinenglish(a)gmail.com Observation bugzilla shows "Wine 2.0" under the "Task Lists" and also shows the text: ------------------------------------ Current Bug Task Lists The bugs we are currently working on are organized into Task lists. Wine 2.0 These bugs are scheduled to be fixed before Wine 2.0 is released. ------------------------------------ according to the winehq website 2.0 was released ages ago and the two current versions are (Stable:Wine 3.0.1) and (Development:Wine 3.8) My suggestion is remove it as obviously no has enough time to update with the frequency that it as requires. Thanks for wine :) -- 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 43234] New: Allow users to show all full logs
by wine-bugs＠winehq.org 04 Nov '18

04 Nov '18

https://bugs.winehq.org/show_bug.cgi?id=43234 Bug ID: 43234 Summary: Allow users to show all full logs Product: Wine-Testbot Version: unspecified Hardware: Other OS: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Currently it's possible to expand one log at a time to show not only the failing lines but also the trace() output. It would be nice if we had a way to see them all at once, though. Of course the user does get the full results e-mailed to them, but the e-mail can take a while to go through, and also it might be good if other people can get the full logs of a test they didn't run (e.g. because it was linked to by the user.) -- 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 3