wine-bugs May 2019

wine-bugs@winehq.org

1 participants
7605 discussions

[Bug 36416] New: valgrind shows a possible leak in ole32/tests/moniker.c
by wine-bugs＠winehq.org 13 May '19

13 May '19

https://bugs.winehq.org/show_bug.cgi?id=36416 Bug ID: 36416 Summary: valgrind shows a possible leak in ole32/tests/moniker.c Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com ==24681== 28 bytes in 1 blocks are possibly lost in loss record 187 of 649 ==24681== at 0x7BC50A9B: RtlAllocateHeap (heap.c:255) ==24681== by 0x536CBB8: apartment_getclassobject (compobj.c:526) ==24681== by 0x536FFC6: get_inproc_class_object (compobj.c:2894) ==24681== by 0x5372D2F: CoGetClassObject (compobj.c:3032) ==24681== by 0x536310A: ClassMoniker_BindToObject (classmoniker.c:242) ==24681== by 0x4D8CADC: test_MkParseDisplayName (objidl.h:3485) ==24681== by 0x4D8E21F: func_moniker (moniker.c:2076) ==24681== by 0x4DBDEA8: run_test (test.h:584) ==24681== by 0x4DBE297: main (test.h:654) -- 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 20359] New: Addition NetServerEnum() support
by wine-bugs＠winehq.org 13 May '19

13 May '19

http://bugs.winehq.org/show_bug.cgi?id=20359 Summary: Addition NetServerEnum() support Product: Wine Version: 1.1.31 Platform: All URL: http://rh-software.com/ OS/Version: All Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ray(a)pobox.co.uk Currently none of the SIV networking pages work as NetServerEnum() (http://msdn.microsoft.com/en-us/library/aa370623(VS.85).aspx) is not implemented. Please can support be added ? Once added then SIV (http://rh-software.com/downloads/siv.zip) can be used to test this using the command: wine siv -save=[network]=stdout -- 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 11

[Bug 47181] New: 'File has unexpected size (374028 != 385384) . Mirror sync in progress?'
by wine-bugs＠winehq.org 13 May '19

13 May '19

https://bugs.winehq.org/show_bug.cgi?id=47181 Bug ID: 47181 Summary: 'File has unexpected size (374028 != 385384). Mirror sync in progress?' Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: joll.nicholas(a)gmail.com Distribution: --- Created attachment 64435 --> https://bugs.winehq.org/attachment.cgi?id=64435 Apt output I attach some errors that were generated by apt when it deals with the following Wine repository: https://dl.winehq.org/wine-builds/ubuntu/ bionic main It is only Wine and a few other offenders that ever generate these errors on my system. To be clear: I see such errors on my system, generated by Wine's repository, periodically. Now, such errors yields to a rash of support questions on Linux forums by those new to Linux who want to know what is going on. Is there no better way of doing things that could be implemented at your end? Thanks. -- 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 47091] New: Wine-Staging 4.7 release server-Desktop_Refcount patchset breaks ' patchinstall.sh ... --backend=git --force-autoconf --all'
by wine-bugs＠winehq.org 12 May '19

12 May '19

https://bugs.winehq.org/show_bug.cgi?id=47091 Bug ID: 47091 Summary: Wine-Staging 4.7 release server-Desktop_Refcount patchset breaks 'patchinstall.sh ... --backend=git --force-autoconf --all' Product: Wine-staging Version: 4.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hello folks, encountered this when building official Wine-Staging 4.7 release. With the reintroduction of server-Desktop_Refcount patchset, running 'patchinstall.sh' script with '... --backend=git --force-autoconf --all' doesn't work anymore. You might argue why people use '--force-autoconf' option but that's a separate thing :-) --- snip --- ... HEAD is now at 6e3f39a4c5 Release 4.7. Cloning into '/home/focht/projects/wine/staging-patches-4.7'... remote: Enumerating objects: 102, done. remote: Counting objects: 100% (102/102), done. remote: Compressing objects: 100% (70/70), done. remote: Total 35588 (delta 45), reused 61 (delta 31), pack-reused 35486 Receiving objects: 100% (35588/35588), 29.56 MiB | 4.26 MiB/s, done. Resolving deltas: 100% (23518/23518), done. HEAD is now at 547e7c81 Release v4.7 Cloning into '/home/focht/projects/wine/staging-src-4.7'... done. Checking out files: 100% (7764/7764), done. HEAD is now at 6e3f39a4c5 Release 4.7. Applying /home/focht/projects/wine/staging-patches-4.7/patches/Compiler_Warnings/0001-windowscodecs-Avoid-implicit-cast-of-interface-point.patch Applying: windowscodecs: Avoid implicit cast of interface pointer. Auto packing the repository in background for optimum performance. ... Applying /home/focht/projects/wine/staging-patches-4.7/patches/riched20-IText_Interface/0010-riched20-Silence-repeated-FIXMEs-triggered-by-Adobe-.patch Applying: riched20: Silence repeated FIXMEs triggered by Adobe Reader. Applying /home/focht/projects/wine/staging-patches-4.7/patches/server-Desktop_Refcount/0001-server-Introduce-a-new-alloc_handle-object-callback..patch Applying: server: Introduce a new alloc_handle object callback. (v2) error: patch failed: include/wine/server_protocol.h:6677 error: include/wine/server_protocol.h: patch does not apply Patch failed at 0001 server: Introduce a new alloc_handle object callback. (v2) Use 'git am --show-current-patch' to see the failed patch When you have resolved this problem, run "git am --continue". If you prefer to skip this patch, run "git am --skip" instead. To restore the original branch and stop patching, run "git am --abort". ERROR: Failed to apply patch, aborting! ERROR in build.sh: line 470 with exit code 1 ERROR message: "Failed to run Wine-Staging 'patchinstall' script!" --- snip --- https://github.com/wine-staging/wine-staging/tree/master/patches/server-Des… Introduced here: https://github.com/wine-staging/wine-staging/commit/4e7071e4f14f6ce85b0eb4b… Specifically: https://github.com/wine-staging/wine-staging/blob/master/patches/server-Des… It seems 'include/wine/server_protocol.h' was committed by mistake here? Regards -- 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 47124] New: Wine+eventfd_synchronization patches build fails
by wine-bugs＠winehq.org 12 May '19

12 May '19

https://bugs.winehq.org/show_bug.cgi?id=47124 Bug ID: 47124 Summary: Wine+eventfd_synchronization patches build fails Product: Wine-staging Version: 4.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shtetldik(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- I tried building Wine + eventfd_synchronization patches from staging (applying only them using ./patchinstall.sh DESTDIR="$wine_src" eventfd_synchronization The build is failing like this (both on Wine master and Wine b47938273): gcc -m64 -c -o trace.o /home/user/build/wine-git/source/server/trace.c -I. \ -I/home/user/build/wine-git/source/server -I../include \ -I/home/user/build/wine-git/source/include -D__WINESRC__ -Wall -pipe -fno-strict-aliasing \ -Wdeclaration-after-statement -Wempty-body -Wignored-qualifiers -Wno-packed-not-aligned \ -Wshift-overflow=2 -Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla \ -Wwrite-strings -Wpointer-arith -Wlogical-op -O3 -march=znver1 /home/user/build/wine-git/source/server/sock.c: In function ‘req_socket_cleanup’: /home/user/build/wine-git/source/server/sock.c:1345:20: error: too many arguments to function ‘enumerate_handles’ while ((sock = enumerate_handles(current->process, &sock_ops, &index, NULL))) ^~~~~~~~~~~~~~~~~ In file included from /home/user/build/wine-git/source/server/sock.c:64: /home/user/build/wine-git/source/server/handle.h:51:21: note: declared here extern obj_handle_t enumerate_handles( struct process *process, const struct object_ops *ops, ^~~~~~~~~~~~~~~~~ make[1]: *** [Makefile:1368: sock.o] Error 1 Probably dependency patch is not listed. -- 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 47108] New: Space Hack (Maximus XV): missing textures
by wine-bugs＠winehq.org 12 May '19

12 May '19

https://bugs.winehq.org/show_bug.cgi?id=47108 Bug ID: 47108 Summary: Space Hack (Maximus XV): missing textures Product: Wine-staging Version: 4.7 Hardware: x86 URL: https://www.fileplanet.com/archive/p-24861/Maximus-XV- Abraham-Strong-Demo OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 64300 --> https://bugs.winehq.org/attachment.cgi?id=64300 screenshot In the game Space Hack (aka. Maximus XV) most of the textures are missing. The problem doesn't occur in vanilla Wine. The patch to blame: https://github.com/wine-staging/wine-staging/blob/master/patches/ddraw-Rend… setupmaximusxvdemo.exe (103 MB) md5sum: 261d276e48b99bc1b2568a4356ac8e4d wine-4.7-66-g8039941c52 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 418.52.05 OpenGL core profile shading language version string: 4.60 NVIDIA -- 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 7

[Bug 47100] New: Simple command that needs CreateSymbolicLinkW doesn`t work anymore in Staging-4.7
by wine-bugs＠winehq.org 12 May '19

12 May '19

https://bugs.winehq.org/show_bug.cgi?id=47100 Bug ID: 47100 Summary: Simple command that needs CreateSymbolicLinkW doesn`t work anymore in Staging-4.7 Product: Wine-staging Version: 4.6 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: xerox.xerox2000x(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hi, I noticed that the patchset in Staging for CreateSymbolicLinkW has been updated. Just creating this bug to let you know that the simple command from comment #4: https://bugs.winehq.org/show_bug.cgi?id=44948#c4 doesn`t work anymore. I have a compiled recent version lying here ( wine-4.3-339-g865d4c3c72 (Staging)). There it seems to wok fine. The command from comment #4 in one liner: cd $(mktemp -d) && /media/louis/00e587ff-1035-4ec8-8d1f-b69d3527589a/wine-staging4.3/wine64-build/wine cmd /C "mklink foo bar" && stat foo 000b:fixme:winediag:start_process Wine Staging 4.3 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. File: foo -> /home/louis/.wine/dosdevices/z:/tmp/tmp.8TxcDBiOH7/bar Size: 54 Blocks: 0 IO Block: 4096 symbolic link Device: 821h/2081d Inode: 1048736 Links: 1 Access: (0777/lrwxrwxrwx) Uid: ( 1000/ louis) Gid: ( 1000/ louis) Access: 2019-04-29 21:56:16.530708099 +0200 Modify: 2019-04-29 21:56:16.530708099 +0200 Change: 2019-04-29 21:56:16.530708099 +0200 in current Staging 4.7: cd $(mktemp -d) && /opt/wine-staging/bin/wine cmd /C "mklink foo bar" && stat foo 000b:fixme:winediag:start_process Wine Staging 4.7 is a testing version containing experimental patches. 000b:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. Failed to open 'foo' stat: cannot stat 'foo': No such file or directory If I remember correctly running Office365 installer with Staging was enough to avoid manually copying files to correct locations. I did not yet test if that is broken too now in Staging-4.7, will do later (takes quite some time). Just reporting this simple example for now. -- 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 11

[Bug 47121] New: Soulbringer displays only black screen in hardware rendering mode
by wine-bugs＠winehq.org 12 May '19

12 May '19

https://bugs.winehq.org/show_bug.cgi?id=47121 Bug ID: 47121 Summary: Soulbringer displays only black screen in hardware rendering mode Product: Wine-staging Version: 4.7 Hardware: x86 URL: https://www.gog.com/game/soulbringer OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: gofmanp(a)gmail.com, leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 64331 --> https://bugs.winehq.org/attachment.cgi?id=64331 terminal output The screen turns black but the game is still running when the game is loading to the menu when any of the available hardware rendering modes is selected in the launcher (including DX6 and DX7 renderers). Software rendering works properly. The problem doesn't occur in vanilla Wine. No demo version is available. The patch to blame: https://github.com/wine-staging/wine-staging/blob/master/patches/ddraw-Rend… wine-4.7-177-gb479382737 (Staging) OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 418.52.05 -- 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 5

[Bug 47148] New: mouse long-clic is badly handled in wine 4.7
by wine-bugs＠winehq.org 12 May '19

12 May '19

https://bugs.winehq.org/show_bug.cgi?id=47148 Bug ID: 47148 Summary: mouse long-clic is badly handled in wine 4.7 Product: Wine Version: 4.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: guillaume.lelouet(a)gmail.com Distribution: --- it was alright before 4.7, and if I switch back to wine 4.6 it's alright. The long press right click and middle click behave badly, like a long click is translated on a different position than a short click. eg if I click somewhere, it's okay ; if I click and keep mouse1 clicked, then the mouse is moved somewhere else. In some games it means the right/middle click is not usable. OS is ubuntu 19.04 , wine version is 4.7~disco , package is winehq-stagging . -- 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 15

[Bug 39335] New: Evernote 5.9.x - cannot browse or edit notes
by wine-bugs＠winehq.org 12 May '19

12 May '19

https://bugs.winehq.org/show_bug.cgi?id=39335 Bug ID: 39335 Summary: Evernote 5.9.x - cannot browse or edit notes Product: Wine Version: 1.7.50 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: falconepl(a)gmail.com Distribution: --- When Evernote 5.9.x (e.g. the latest Evernote 5.9.1.8742) is started up, your recently modified note (e.g. on another device) is being displayed. However, when one tries to jump to some other note, by selecting an element on "All notes" list, the content of the currently displayed note is not changed (only note's header is being updated - information on note's creation date etc.) Only when you double click on given note element from your notes list, a pop-up window with that note's content/text shows up, but the note cannot be edited. The last version of Evernote that hasn't got these problems was Evernote 5.8.13.8152. Tested under Wine 1.7.50. -- 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 21

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs May 2019