wine-bugs February 2019

wine-bugs@winehq.org

1 participants
7653 discussions

[Bug 43390] New: valgrind shows a few definite leaks in dlls/xaudio2_7/ tests/xaudio2.c
by wine-bugs＠winehq.org 05 May '19

05 May '19

https://bugs.winehq.org/show_bug.cgi?id=43390 Bug ID: 43390 Summary: valgrind shows a few definite leaks in dlls/xaudio2_7/tests/xaudio2.c Product: Wine Version: 2.12 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: xaudio2 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo ==3551== 8 bytes in 1 blocks are definitely lost in loss record 63 of 766 ==3551== at 0x7BC51061: notify_alloc (heap.c:254) ==3551== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==3551== by 0x5C85281: XAudio2Create (xaudio_dll.c:2159) ==3551== by 0x4A1B741: func_xaudio2 (xaudio2.c:1150) ==3551== by 0x4A1C74F: run_test (test.h:603) ==3551== by 0x4A1CBAD: main (test.h:687) ==3551== ==3551== 12 bytes in 1 blocks are definitely lost in loss record 94 of 766 ==3551== at 0x7BC51061: notify_alloc (heap.c:254) ==3551== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==3551== by 0x5C7DA6D: CreateAudioVolumeMeter (xapofx.c:795) ==3551== by 0x4A1B1A7: test_xapo_creation_modern (xaudio2.c:1053) ==3551== by 0x4A1B463: test_xapo_creation (xaudio2.c:1089) ==3551== by 0x4A1B5B4: func_xaudio2 (xaudio2.c:1122) ==3551== by 0x4A1C74F: run_test (test.h:603) ==3551== by 0x4A1CBAD: main (test.h:687) ==3551== ==3551== 12 bytes in 1 blocks are definitely lost in loss record 95 of 766 ==3551== at 0x7BC51061: notify_alloc (heap.c:254) ==3551== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==3551== by 0x5C7DAFA: CreateAudioReverb (xapofx.c:809) ==3551== by 0x4A1B2D4: test_xapo_creation_modern (xaudio2.c:1067) ==3551== by 0x4A1B463: test_xapo_creation (xaudio2.c:1089) ==3551== by 0x4A1B5B4: func_xaudio2 (xaudio2.c:1122) ==3551== by 0x4A1C74F: run_test (test.h:603) ==3551== by 0x4A1CBAD: main (test.h:687) ==3551== ==3551== 12 bytes in 1 blocks are definitely lost in loss record 96 of 766 ==3551== at 0x7BC51061: notify_alloc (heap.c:254) ==3551== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==3551== by 0x5C7DA6D: CreateAudioVolumeMeter (xapofx.c:795) ==3551== by 0x4A176DB: test_simple_streaming (xaudio2.c:293) ==3551== by 0x4A1B807: func_xaudio2 (xaudio2.c:1158) ==3551== by 0x4A1C74F: run_test (test.h:603) ==3551== by 0x4A1CBAD: main (test.h:687) ==3551== ==3551== 48 bytes in 4 blocks are definitely lost in loss record 349 of 766 ==3551== at 0x7BC51061: notify_alloc (heap.c:254) ==3551== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==3551== by 0x5CA3F03: ??? ==3551== by 0x5CA4059: ??? ==3551== by 0x4A1A97C: test_xapo_creation_legacy (xaudio2.c:932) ==3551== by 0x4A1B3ED: test_xapo_creation (xaudio2.c:1083) ==3551== by 0x4A1B5B4: func_xaudio2 (xaudio2.c:1122) ==3551== by 0x4A1C74F: run_test (test.h:603) ==3551== by 0x4A1CBAD: main (test.h:687) ==3551== ==3551== 48 bytes in 4 blocks are definitely lost in loss record 350 of 766 ==3551== at 0x7BC51061: notify_alloc (heap.c:254) ==3551== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==3551== by 0x5C37F03: ??? ==3551== by 0x5C38059: ??? ==3551== by 0x4A1A97C: test_xapo_creation_legacy (xaudio2.c:932) ==3551== by 0x4A1B401: test_xapo_creation (xaudio2.c:1084) ==3551== by 0x4A1B5B4: func_xaudio2 (xaudio2.c:1122) ==3551== by 0x4A1C74F: run_test (test.h:603) ==3551== by 0x4A1CBAD: main (test.h:687) ==3551== ==3551== 48 bytes in 4 blocks are definitely lost in loss record 351 of 766 ==3551== at 0x7BC51061: notify_alloc (heap.c:254) ==3551== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==3551== by 0x5CA3F03: ??? ==3551== by 0x5CA4059: ??? ==3551== by 0x4A1A97C: test_xapo_creation_legacy (xaudio2.c:932) ==3551== by 0x4A1B415: test_xapo_creation (xaudio2.c:1085) ==3551== by 0x4A1B5B4: func_xaudio2 (xaudio2.c:1122) ==3551== by 0x4A1C74F: run_test (test.h:603) ==3551== by 0x4A1CBAD: main (test.h:687) ==3551== ==3551== 48 bytes in 4 blocks are definitely lost in loss record 352 of 766 ==3551== at 0x7BC51061: notify_alloc (heap.c:254) ==3551== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==3551== by 0x5CA3F03: ??? ==3551== by 0x5CA4059: ??? ==3551== by 0x4A1A97C: test_xapo_creation_legacy (xaudio2.c:932) ==3551== by 0x4A1B429: test_xapo_creation (xaudio2.c:1086) ==3551== by 0x4A1B5B4: func_xaudio2 (xaudio2.c:1122) ==3551== by 0x4A1C74F: run_test (test.h:603) ==3551== by 0x4A1CBAD: main (test.h:687) ==3551== ==3551== 48 bytes in 4 blocks are definitely lost in loss record 353 of 766 ==3551== at 0x7BC51061: notify_alloc (heap.c:254) ==3551== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==3551== by 0x5CA3F03: ??? ==3551== by 0x5CA4059: ??? ==3551== by 0x4A1A97C: test_xapo_creation_legacy (xaudio2.c:932) ==3551== by 0x4A1B43D: test_xapo_creation (xaudio2.c:1087) ==3551== by 0x4A1B5B4: func_xaudio2 (xaudio2.c:1122) ==3551== by 0x4A1C74F: run_test (test.h:603) ==3551== by 0x4A1CBAD: main (test.h:687) ==3551== ==3551== 48 bytes in 4 blocks are definitely lost in loss record 354 of 766 ==3551== at 0x7BC51061: notify_alloc (heap.c:254) ==3551== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==3551== by 0x5E44F03: ??? ==3551== by 0x5E45059: ??? ==3551== by 0x4A1A97C: test_xapo_creation_legacy (xaudio2.c:932) ==3551== by 0x4A1B451: test_xapo_creation (xaudio2.c:1088) ==3551== by 0x4A1B5B4: func_xaudio2 (xaudio2.c:1122) ==3551== by 0x4A1C74F: run_test (test.h:603) ==3551== by 0x4A1CBAD: main (test.h:687) ==3551== ==3551== 48 bytes in 4 blocks are definitely lost in loss record 355 of 766 ==3551== at 0x7BC51061: notify_alloc (heap.c:254) ==3551== by 0x7BC5554F: RtlAllocateHeap (heap.c:1716) ==3551== by 0x5C7DC35: CreateFX (xapofx.c:835) ==3551== by 0x4A1AE99: test_xapo_creation_modern (xaudio2.c:1018) ==3551== by 0x4A1B463: test_xapo_creation (xaudio2.c:1089) ==3551== by 0x4A1B5B4: func_xaudio2 (xaudio2.c:1122) ==3551== by 0x4A1C74F: run_test (test.h:603) ==3551== by 0x4A1CBAD: main (test.h:687) ==3551== -- 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 45557] New: winecfg -> wine: '/home/ich/.wine' is a 64-bit installation, it cannot be used with a 32-bit wineserver.
by wine-bugs＠winehq.org 04 May '19

04 May '19

https://bugs.winehq.org/show_bug.cgi?id=45557 Bug ID: 45557 Summary: winecfg -> wine: '/home/ich/.wine' is a 64-bit installation, it cannot be used with a 32-bit wineserver. Product: Packaging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: Ulf.Zibis(a)gmx.de CC: michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- On Ubuntu 18.04 I installed with: sudo dpkg --add-architecture i386 # Nur auf 64-Bit-Systemen notwendig wget -O - https://dl.winehq.org/wine-builds/Release.key | sudo apt-key add - sudo apt-add-repository 'https://dl.winehq.org/wine-builds/ubuntu/' && sudo apt update sudo apt install winehq-stable winetricks With $ winecfg I get: ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. wine: '/home/ich/.wine' is a 64-bit installation, it cannot be used with a 32-bit wineserver. For ERROR: ld.so: see bug 45434, but there remains the other blocking problem. In /opt/wine-stable/bin/ wine64* is missing, see: $ ls -l /usr/bin/wine lrwxrwxrwx 1 root root 25 Jul 4 11:51 /usr/bin/wine -> /opt/wine-stable/bin/wine ich@T500:~$ ls -l /usr/bin/wine /usr/bin/wine64* lrwxrwxrwx 1 root root 25 Jul 4 11:51 /usr/bin/wine -> /opt/wine-stable/bin/wine lrwxrwxrwx 1 root root 27 Jul 4 11:51 /usr/bin/wine64 -> /opt/wine-stable/bin/wine64 lrwxrwxrwx 1 root root 37 Jul 4 11:51 /usr/bin/wine64-preloader -> /opt/wine-stable/bin/wine64-preloader $ ls -l /opt/wine-stable/bin/wine /opt/wine-stable/bin/wine64* ls: Zugriff auf '/opt/wine-stable/bin/wine64*' nicht möglich: Datei oder Verzeichnis nicht gefunden -rwxr-xr-x 1 root root 9556 Jul 4 12:05 /opt/wine-stable/bin/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 21

[Bug 46428] New: Application crashes: Antscope2.exe
by wine-bugs＠winehq.org 04 May '19

04 May '19

https://bugs.winehq.org/show_bug.cgi?id=46428 Bug ID: 46428 Summary: Application crashes: Antscope2.exe Product: Wine Version: 3.0.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: coccusmatins(a)gmail.com Distribution: --- Created attachment 63202 --> https://bugs.winehq.org/attachment.cgi?id=63202 error log Application (Antscope2.exe) crashes on startup. Source: https://rigexpert.com/products/software/antscope2/ -- 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 44279] New: Wine can' t enumerate HID device that is based on Bluetooth (a Wiimote)
by wine-bugs＠winehq.org 04 May '19

04 May '19

https://bugs.winehq.org/show_bug.cgi?id=44279 Bug ID: 44279 Summary: Wine can't enumerate HID device that is based on Bluetooth (a Wiimote) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: epigramx(a)yahoo.com Distribution: --- On Windows, if I run hclient.exe (source here: https://github.com/Microsoft/Windows-driver-samples/tree/master/hid/hclient) I can normally see my paired and connected device, as shown in this image: https://i.imgur.com/Up60k7s.png It's one of the Wii Remote Plus devices. However, if I do pair and connect the device on Debian and if it correctly appears in /sys/bus/hid/devices and all the tests here work: https://wiki.archlinux.org/index.php/XWiimote , running hclient.exe with wine on linux does not find that hid device which might explain why it's not detected by a console application that relies on enumerating HID devices on windows. I suspect it's a limitation of wine in finding HID devices if they originate from Bluetooth but I can't be sure. I might return with more details later on (when I reboot to Linux) but let me know if you need specific further details. Wiimotes are very common so if a dev could try one and see if he can enumerate it in hclient (source above) that'd be great. -- 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 13

[Bug 44556] New: SYN_DROPPED undeclared on Linux < 2.6.39
by wine-bugs＠winehq.org 04 May '19

04 May '19

https://bugs.winehq.org/show_bug.cgi?id=44556 Bug ID: 44556 Summary: SYN_DROPPED undeclared on Linux < 2.6.39 Product: Wine Version: 3.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winebus.sys Assignee: wine-bugs(a)winehq.org Reporter: Zenitur(a)yandex.ru Distribution: --- When I build Wine on GNU/Linux with 2.6.37 kernel, I'd an error "SYN_DROPPED undeclared". Google says that it was appear in 2.6.39 and tslib project has this code: https://github.com/kergoth/tslib/blob/master/plugins/input-raw.c #ifndef SYN_DROPPED /* < 2.6.39 kernel headers */ # define SYN_DROPPED 3 #endif -- 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 41869] New: undefined reference to `HIDIOCSFEATURE'
by wine-bugs＠winehq.org 04 May '19

04 May '19

https://bugs.winehq.org/show_bug.cgi?id=41869 Bug ID: 41869 Summary: undefined reference to `HIDIOCSFEATURE' Product: Wine Version: 1.9.24 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: version2013(a)openmailbox.org Distribution: --- Created attachment 56272 --> https://bugs.winehq.org/attachment.cgi?id=56272 log file undefined reference to `HIDIOCSFEATURE' my system command: ldd --version ldd (GNU libc) 2.10.1 command: uname -r 3.0.66 command: gcc --version gcc (GCC) 4.3.4 -- 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 44904] New: winebus blocks auto start up of scheduler service
by wine-bugs＠winehq.org 04 May '19

04 May '19

https://bugs.winehq.org/show_bug.cgi?id=44904 Bug ID: 44904 Summary: winebus blocks auto start up of scheduler service Product: Wine Version: 3.5 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: winebus.sys Assignee: wine-bugs(a)winehq.org Reporter: dmitry(a)baikal.ru CC: aric(a)codeweavers.com Regression SHA1: regression Distribution: --- How to reproduce: 1. rm -rf ~/.wine 2. cd wine/dlls/taskschd/tests 3. make testclean && make test 4. wait 5 seconds so that wineserver shuts down 5. make testclean && make test and get 0024:err:ole:start_rpcss failed to start RpcSs service 0024:err:ole:epm_register ept_insert failed with error 1722 0024:err:schedsvc:RPC_init RpcEpRegister error 0x6ba This turned to be a regression caused by 45d82a2464b535c484b0a6e96f9851f9db573edf is the first bad commit commit 45d82a2464b535c484b0a6e96f9851f9db573edf Author: Aric Stewart <aric(a)codeweavers.com> Date: Thu Feb 2 10:38:55 2017 -0600 loader: Start winebus service by default. Signed-off-by: Aric Stewart <aric(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> After the disabling auto startup of winebus by changing "Start"=dword:00000002 to "Start"=dword:00000003 in its "WineBus" service entry in registry the problem disappears. Since by default Scheduler service is disabled (and gets enabled only once at least one task is being added) this regression was not noticed until 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 6

[Bug 13881] New: Stack limits error, hardware incompatibility?
by wine-bugs＠winehq.org 04 May '19

04 May '19

http://bugs.winehq.org/show_bug.cgi?id=13881 Summary: Stack limits error, hardware incompatibility? Product: Wine Version: 1.0-rc4 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dav666666(a)gmail.com Hello. I'm trying to play GunZ : The Duel. Don't delete this bug because you think it's game related. It is not. Why? Everyone got the game working. Except me. I tried reinstalling the whole system and it crashed on a fresh install too. I tried on my brother's computer and it worked without any problem. All this make me think it's a hardware related problem but I need your help to determine which of my hardware is causing trouble. I explained my problem on GunZ page on Winedb: http://appdb.winehq.org/objectManager.php?sClass=version&iId=12057, it is the comment called "Stack limits" I hope you will find a fix, GunZ is the last game that makes deleting windows from my computer impossible... Sorry for english, I'm belgian, I did my best to write correct sentences... -- 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 13

[Bug 10530] New: Flyff doesn't work with wine
by wine-bugs＠winehq.org 04 May '19

04 May '19

http://bugs.winehq.org/show_bug.cgi?id=10530 Summary: Flyff doesn't work with wine Product: WineHQ Apps Database Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: website-bugs AssignedTo: wine-bugs(a)winehq.org ReportedBy: nitzan65(a)gmail.com Flyff Shows me a white screen. Please fix it thanks! -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 5

[Bug 11319] New: GameOverlay (Steam friends In-game) crashes on start
by wine-bugs＠winehq.org 02 May '19

02 May '19

http://bugs.winehq.org/show_bug.cgi?id=11319 Summary: GameOverlay (Steam friends In-game) crashes on start Product: Wine Version: 0.9.53. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P4 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sagman.staredsi(a)gmail.com Created an attachment (id=10425) --> (http://bugs.winehq.org/attachment.cgi?id=10425) A GameOverlayRenderer log The GameOverlayUI.exe and GameOverlayRenderer.dll (Steam in-game friends interface) crashes on start. I attach a log created by the Steam.exe . The file refers to GameOverlayRenderer.dll and this log attach that the dlls or exe wich fails are: 01: hl2.exe 02: ntdll.dll 03: KERNEL32.dll 04: user32.dll 05: gdi32.dll 06: advapi32.dll 07: GameOverlayRenderer.dll 08: winex11.drv 09: imm32.dll Also attach here a minilog (it's 2 lines) of wine trying to start "GameOverlayUI.exe" $ wine GameOverlayUI.exe fixme:process:SetProcessShutdownParameters (000003ff, 00000000): partial stub. -- 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 13

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 February 2019