wine-bugs October 2018

wine-bugs@winehq.org

1 participants
7892 discussions

[Bug 44072] New: Agents of Mayhem does not start
by wine-bugs＠winehq.org 19 Oct '18

19 Oct '18

https://bugs.winehq.org/show_bug.cgi?id=44072 Bug ID: 44072 Summary: Agents of Mayhem does not start Product: Wine Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: byi5000(a)gmail.com Distribution: --- Created attachment 59787 --> https://bugs.winehq.org/attachment.cgi?id=59787 wine debug log: 13.4 mb unzipped Using wine-2.21-staging *Could* be because of Steam CEG https://bugs.winehq.org/show_bug.cgi?id=32515 Could be something else -- 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

[Bug 46009] New: "Total WAR: Attila" visual artifacts and slow performance
by wine-bugs＠winehq.org 18 Oct '18

18 Oct '18

https://bugs.winehq.org/show_bug.cgi?id=46009 Bug ID: 46009 Summary: "Total WAR: Attila" visual artifacts and slow performance Product: Wine Version: 3.18 Hardware: x86 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: svyatpro(a)gmail.com Created attachment 62581 --> https://bugs.winehq.org/attachment.cgi?id=62581 Photo Running Total War:Attila on WineD3D has artifacts and very low framerate. -- 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 45969] New: ArcGIS Pro crashes on start
by wine-bugs＠winehq.org 18 Oct '18

18 Oct '18

https://bugs.winehq.org/show_bug.cgi?id=45969 Bug ID: 45969 Summary: ArcGIS Pro crashes on start Product: Wine Version: 3.17 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 62523 --> https://bugs.winehq.org/attachment.cgi?id=62523 console output To reproduce: 1. Run `winetricks dotnet461`. This is a prerequisite of ArcGIS Pro. 2. Run `wine ArcGISPro_22_163783.exe`. Note that this is a 64-bit program. 3. Run `wine 'C:\Program Files\ArcGIS\Pro\bin\ArcGISPro.exe'`. Console output is attached. $ sha256sum ArcGISPro_22_163783.exe b6acceb36d51cdb1cc283478fd6170b7e51630f127ea4c841fef67d662d40f1e -- 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 43263] New: Wine cannot coexist with other ALSA programs, even with dmix
by wine-bugs＠winehq.org 17 Oct '18

17 Oct '18

https://bugs.winehq.org/show_bug.cgi?id=43263 Bug ID: 43263 Summary: Wine cannot coexist with other ALSA programs, even with dmix Product: Wine Version: 2.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winealsa.drv Assignee: wine-bugs(a)winehq.org Reporter: sgilles(a)math.umd.edu Distribution: --- Created attachment 58587 --> https://bugs.winehq.org/attachment.cgi?id=58587 .asoundrc This machine runs Gentoo and ALSA + dmix (.asoundrc attached). I have observed this issue with wine installed from Gentoo's repositories, but also with wine built from git (I have observed this with commit 6ec3cd9434488ba5bc0fd271a47b7d46827477c5 for example, which is the latest at time of writing). Every native program on this machine (mpv, mpd, ffplay, firefox, etc) is able to play sound concurrently with every other such program. My options under winecfg's audio tab are different depending on whether an ALSA-using program is currently running: [A] (System default) [A] Out: default [A] Out: HDA NVidia - HDMI 3 [A] Out: HDA NVidia - HDMI 2 [A] Out: HDA NVidia - HDMI 0 [A] Out: HDA NVidia - HDMI 1 [B] Out: HDA Intel PCH-ALC887-VD Anal... The entry marked [B] only appears if there is no such program running. The entries marked [A] cause the "Test Sound" to be truncated abruptly, while the entry marked [B] allows the test sound to fully die down. Furthermore, if an entry marked [A] is selected, running a program that produces sound will fail with lines like err:dsound:DSOUND_ReopenDevice Initialize failed: 8889000f in the output. I have attached a log created with wine from commit 6ec3cd9434488ba5bc0fd271a47b7d46827477c5, from a fresh, WINEARCH="win32" wineprefix, running Warning Forever 1.08, with "(System default)" selected (mpd is running in the background), and with WINEDEBUG="+tid,+mmdevapi,+winmm,+driver,+midi,+dsound,+dsound3d,+dmusic,+mci,+oss,+alsa,+coreaudio" The expected behavior is that, since I have dmix configured, wine should behave like other programs and play sound concurrently with them. I've looked around for solutions to this, and people claim that wine has been able to coexist with other programs in the past (hence my reporting it as a bug), but every piece of advice I find seems to be outdated. -- 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 37950] New: Listview in uTorrent 2.4.2 (32-bit) unresponsive when removing torrent
by wine-bugs＠winehq.org 17 Oct '18

17 Oct '18

https://bugs.winehq.org/show_bug.cgi?id=37950 Bug ID: 37950 Summary: Listview in uTorrent 2.4.2 (32-bit) unresponsive when removing torrent Product: Wine Version: 1.7.34 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shomari.sharpe(a)gmail.com Distribution: --- Created attachment 50556 --> https://bugs.winehq.org/attachment.cgi?id=50556 uTorrent 3.4.2 screenshot The following problems are noted when working with uTorrent 3.4.2 (37754) 32-bit * clicking on a torrent (gives a textbox appearance with a cursor) * uTorrent appears to hang when deleting a torrent * listview redraw problems * listview items on the left are too big -- 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 46003] New: glibc (libpthread.so.0) crashes 64-bit FPUs and freezes screen in 32-bit applications
by wine-bugs＠winehq.org 16 Oct '18

16 Oct '18

https://bugs.winehq.org/show_bug.cgi?id=46003 Bug ID: 46003 Summary: glibc (libpthread.so.0) crashes 64-bit FPUs and freezes screen in 32-bit applications Product: Wine Version: 3.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: wine.fixes(a)gmail.com Distribution: --- The 64-bit glibc libraries (specifically, libpthread.so.0 - version 2.27) apparently use the sysenter / syscall assembly commands in order to initiate the __libc_write() system calls, rather than the "int 0x80" command that the 32-bit libraries use. This is fine for 64-bit Windows applications in Wine, but seems to cause a CPU exception when running certain 32-bit applications on a 64-bit Intel CPU (such as the Core i5), which - in turn - seems to cause stack underflow and NaN errors on the FPU unit under certain circumstances, thus preventing the screen from updating whenever floating point calculations are required in order to calculate the final screen position. It can also cause unhandled exceptions and cause the application to terminate entirely in some applications. I am yet to identify any commercial applications which suffer from this problem, but I have written several simple SDL and Win32 graphical programs (compiled with version 0.9.25 of the TCC Tiny C Compiler) which demonstrate the effects. I have provided sample code of one such application below. This problem also appears to manifest on 64-bit Intel CPUs even when using 32-bit operating systems (such as Ubuntu 18.04-i386), but I can confirm from testing that the 32-bit QEMU virtual machine appears to be unaffected (and, presumably, so are 'real' 32-bit CPUs too). I have been told that 64-bit AMD CPUs (unlike 64-bit Intel CPUs) will not trigger an error when using sysenter / syscall in 32-bit mode, but I am yet to confirm this as I currently only have access to Intel CPUs. Incidentally, I believe that Intel themselves advise against sysenter / syscall in 32-bit mode. I have been able to temporarily fix the problem from within Wine by calling the assembly command "fninit" (which resets the FPU) at the start of the DC_UpdateXforms() function in dlls/gdi32/dc.c, or by calling the "fninit" command from within the application (or, in some circumstances, simply moving the window across the screen), but obviously it would be preferable to fix the error at source from within the glibc libraries... I realise that this is not an error with the Wine source code itself per se, but I have registered it here in case anybody else encounters the same problem in future. SAMPLE CODE (Note: This code requires the 32-bit v.0.9.25 or v.0.9.24 version of the TCC Tiny C Compiler, as the error does not appear to manifest on newer versions) This simple program should display a window which changes colour between red, green, and blue every 0.5 seconds on Windows; however, when run from within Wine on 64-bit Intel CPUs, it appears to freeze on the first colour due to the FPU encountering an error during the __libc_write() routine #include <windows.h> #include <string.h> MSG msg; WNDCLASS wc; HWND hwnd; BITMAPINFO bmp = { { sizeof(BITMAPINFOHEADER), 400, 400, 1, 32 } }; unsigned char *pBits = NULL; HDC hdc, compatibleDC; HBITMAP dib_section; float f = 1.0f; unsigned char color[3][4] = { {255, 0, 0, 255}, {0, 255, 0, 255}, {0, 0, 255, 255} }; unsigned char current_color = 0; unsigned int i; int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow) { ZeroMemory(&wc, sizeof wc); wc.hInstance = hInstance; wc.lpfnWndProc = (WNDPROC)DefWindowProc; wc.lpszClassName = "Test App"; if (RegisterClass(&wc) == FALSE) return 0; hwnd = CreateWindow("Test App", "Test App", WS_OVERLAPPEDWINDOW|WS_VISIBLE, CW_USEDEFAULT, CW_USEDEFAULT, 400, 400, 0, 0, hInstance, 0); hdc = GetWindowDC(hwnd); compatibleDC = CreateCompatibleDC(hdc); dib_section = CreateDIBSection(NULL, &bmp, DIB_RGB_COLORS, (VOID**)&pBits, NULL, (DWORD)NULL); SelectObject(compatibleDC, dib_section); while(TRUE) { while(PeekMessage(&msg,NULL,0,0,PM_REMOVE)) { if (msg.message == WM_QUIT) break; TranslateMessage(&msg); DispatchMessage(&msg); } /* The two float operations below will trigger the error */ f += 1.0f; f -= 1.0f; for(i=0; i < (400 * 400 * 4); i+=4) memcpy(&pBits[i], &color[current_color][0], 4); /* If called here, the "fninit()" assembly routine will reset the FPU and enable the screen to update */ // __asm__ volatile ("fninit"); BitBlt(hdc, 0, 0, 400, 400, compatibleDC, 0, 0, SRCCOPY); current_color++; if (current_color >= 3) current_color = 0; Sleep(500); } return msg.wParam; } -- 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 0

[Bug 45999] New: Opening File dialog in Micrographx Windows Draw 4.0 causes Unhandled exception
by wine-bugs＠winehq.org 16 Oct '18

16 Oct '18

https://bugs.winehq.org/show_bug.cgi?id=45999 Bug ID: 45999 Summary: Opening File dialog in Micrographx Windows Draw 4.0 causes Unhandled exception Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jklaas(a)appalachian.dyndns.org Distribution: --- Created attachment 62564 --> https://bugs.winehq.org/attachment.cgi?id=62564 Backtrace saved after application crash Installation of Micrographx Windows Draw 4.0 works without issue. Micrographx Windows Draw 4.0 starts without any difficulty. I can drag a file from a file manager onto the open application to open a file. However, if I attempt to open or save a file from any of the file management dialogs, the application crashes with an Unhandled exception. -- 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

[Bug 45903] New: internet Downlaod Manager Problem in Deepin Desktop
by wine-bugs＠winehq.org 16 Oct '18

16 Oct '18

https://bugs.winehq.org/show_bug.cgi?id=45903 Bug ID: 45903 Summary: internet Downlaod Manager Problem in Deepin Desktop Product: Wine Version: 3.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mahmoud.elswerky(a)gmail.com Distribution: --- again again ,, no one listen to me i face this problem it is a major problem for me this problem wasn't presnt untill wine 3.5 devel then it appeared in coming updates till latest version now 3.17 please read this problem and reply to me to feel that am not talking to my self the problem is : in deepin desktop when i install internet downlaod manager ,, the system tray icon of internet download manager and active running schedule updates icon on system tray are not working both the idm icon on system tray ( or topbar if i installed unofficial deepin topbar ) and the active running schedule downalod icon on system tray also not working the most important for me is the icon of running schedule downloads in system tray where i can't restore windows of runnig schedule downloads this problem occures with me on deepin desktop from version 3.6 to version 3.17 the most recent version now please i reported this problem before and no one reply me and you even didn't see it currently i am stuck with version 3.5 due to this bug as idm is one of reasons for using wine please fix this problem and reply to me to know that you saw this bug report i am using manjaro deepin also same bug occur in deepin os my email is mahmoud.elswerky(a)gmail.com and Telegram id is : @elswerky https://t.me/elswerky -- 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 40267] New: ChoosePixelFormat and SetPixelFormat always fail on X11 with invalid format error
by wine-bugs＠winehq.org 16 Oct '18

16 Oct '18

https://bugs.winehq.org/show_bug.cgi?id=40267 Bug ID: 40267 Summary: ChoosePixelFormat and SetPixelFormat always fail on X11 with invalid format error Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)winehq.org Reporter: alexchandel(a)gmail.com Distribution: --- Created attachment 53892 --> https://bugs.winehq.org/attachment.cgi?id=53892 Anomalous ChoosePixelFormat and SetPixelFormat error Attempting to run a T3 emulator with wine 1.9.5-1 on Arch always produces two error popup boxes saying "ChoosePixelFormat failed" and "SetPixelFormat failed". After the ChoosePixelFormat error, the following is logged: fixme:event:wait_for_withdrawn_state window 0x10072/e00004 wait timed out err:wgl:set_pixel_format Invalid format 0 Then after the SetPixelFormat error, the following is logged: fixme:event:wait_for_withdrawn_state window 0x20072/e00006 wait timed out I've attached a complete log with WINEDEBUG=trace+wgl that yields ore information. From the log, the PIXELFORMATDESCRIPTOR clearly has a valid format, despite Wine's "Invalid format 0" error. Despite these popup errors, the program paints a mostly correct window. But it detects the errors through error code checking, and they are sufficient to prevent the program from functioning at all. -- 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 40578] New: "msiexec /uninstall ..." shows "Install" button.
by wine-bugs＠winehq.org 16 Oct '18

16 Oct '18

https://bugs.winehq.org/show_bug.cgi?id=40578 Bug ID: 40578 Summary: "msiexec /uninstall ..." shows "Install" button. Product: Wine Version: 1.9.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: htl10(a)users.sourceforge.net Distribution: --- trying to ungrade to the latest mono by uninstalling the old one first: http://download.mono-project.com/archive/4.0.2/windows-installer/mono-4.0.2… was a little alarmed that "msiexec /uninstall ..." shows a "Install" button, but it does the right thing anyway, so this is mainly a cosmetic thing. -- 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

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 October 2018