January 2018 - Wine-Bugs - list.winehq.org

[Bug 44383] Starcraft Remastered 1.18+ no longer launching in Wine

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44383 pull <polalbert(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |polalbert(a)gmail.com -- 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.

Jan. 22, 2018

[Bug 44393] New: cannot read form named pipe in wine 3.0 after bug fix 43217

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44393 Bug ID: 44393 Summary: cannot read form named pipe in wine 3.0 after bug fix 43217 Product: Wine Version: 3.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: luca.cunegondi(a)ocme.com Distribution: --- a commercial cad application has commands that can read directly from named pipe if file name starts with a '|'. Example: open_infile '| /usr/bin/ls /tmp | grep pdf' read_file ... This worked perfectly until wine 2.17 and wine-staging 2.18 (on Arch Linux), then stopped working due to bug 43217 and persists after the bug fix. Enabling trace+process debug option shows a call to create_process_impl (wine 3.0) instead of CreateProcessInternalW as before -- 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.

Jan. 22, 2018

[Bug 44392] BM_SETIMAGE sets image with white background instead of transparent. Is it possible to set a transparent image on wine ?

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44392 Nikolay Sivov <bunglehead(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal -- 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.

Jan. 22, 2018

[Bug 44392] New: BM_SETIMAGE sets image with white background instead of transparent. Is it possible to set a transparent image on wine ?

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44392 Bug ID: 44392 Summary: BM_SETIMAGE sets image with white background instead of transparent. Is it possible to set a transparent image on wine? Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: nikolaysemenkov(a)gmail.com Distribution: --- Created attachment 60312 --> https://bugs.winehq.org/attachment.cgi?id=60312 the transparrent image On windows following code works: But on wine transparent image(attached png) appears with solid white background. The code: #include <windows.h> #include <gdiplus.h> HBITMAP loadBitmap(const wchar_t* path) { HBITMAP tBmp = NULL; ULONG_PTR token = 0; Gdiplus::GdiplusStartupInput input = NULL; Gdiplus::GdiplusStartup(&token, &input, NULL); if (token != 0) { Gdiplus::Bitmap* bmp = new Gdiplus::Bitmap(path); bmp->GetHBITMAP(Gdiplus::Color::Transparent, &tBmp); delete bmp; Gdiplus::GdiplusShutdown(token); } return tBmp; } LRESULT CALLBACK WindowProcedure(HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam) { static HBITMAP tBmp = NULL; switch (message) { case WM_CREATE: { HWND btn = CreateWindow(L"BUTTON", L"TEXT", BS_BITMAP | WS_TABSTOP | WS_VISIBLE | WS_CHILD | BS_DEFPUSHBUTTON, 100, 100, 95, 25, hwnd, (HMENU)1, NULL, NULL); tBmp = loadBitmap(L"C:\\zoomin_disabled.png"); SendMessage(btn, BM_SETIMAGE, IMAGE_BITMAP, (LPARAM)tBmp); ShowWindow(btn, SW_SHOW); } break; case WM_DESTROY: DeleteObject(tBmp); PostQuitMessage(0); break; default: return DefWindowProc(hwnd, message, wParam, lParam); } return 0; } int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE, LPSTR, int) { MSG msg; WNDCLASS wc = { 0 }; wc.lpszClassName = TEXT("EU"); wc.hInstance = hInstance; wc.hbrBackground = GetSysColorBrush(COLOR_3DFACE); wc.lpfnWndProc = WindowProcedure; wc.hCursor = LoadCursor(0, IDC_ARROW); wc.hIcon = NULL; RegisterClass(&wc); CreateWindow(wc.lpszClassName, TEXT("Express Uninstaller"), WS_VISIBLE | WS_CAPTION | WS_SYSMENU | WS_OVERLAPPEDWINDOW | WS_VSCROLL, (GetSystemMetrics(SM_CXSCREEN) - 230) / 2, (GetSystemMetrics(SM_CYSCREEN) - 100 ) / 2, 280 + 10, 110 + 20 + 190, 0, 0, hInstance, 0); while (GetMessage(&msg, NULL, 0, 0)) { TranslateMessage(&msg); DispatchMessage(&msg); } } -- 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.

Jan. 22, 2018

[Bug 44388] gldriverquery.exe crash on wineboot and company of heroes says no 3d

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44388 --- Comment #3 from Bryan Quigley <gQuigs(a)gMail.com> --- -forgot to mention I'm using the winehq 3.0 from https://wiki.winehq.org/Ubuntu. Couldn't find a source package/build log, but will keep looking -- 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.

Jan. 22, 2018

[Bug 44391] Star Trek Online: Hang when clicking "Engage"

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44391 Michael B. Trausch <mbt(a)fortifiedtechsystems.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL|http://store.steampowered.c |http://files.startrekonline |om/app/9900/Star_Trek_Onlin |.com/launcher/Star%20Trek%2 |e/ |0Online.exe --- Comment #3 from Michael B. Trausch <mbt(a)fortifiedtechsystems.com> --- Sorry about the incorrect classification. NVIDIA, current version. The hardware is a 1080 Ti, and it works in other (non-Wine) applications. I don't have any good (non-STO) GL apps to test with on Wine, but the EXE does run and displays its first window (the one which self-updates and then allows you to enter the game), so it's not a dylinker issue. It occurs without Steam or Arc, so it is neither. I've updated URL to point to the actual EXE file. Steam and Arc are the launchers, but the EXE linked to is actually STO and will "patch" (against an empty installation) the first time it is run. So, to clarify: not a launcher problem, as I've tested none of the launchers. The way I play the game on Windows is the same as I want to do here: download STO executable file, let the game download the data files, and then blow some crap outta space. :-) -- 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.

Jan. 21, 2018

[Bug 44383] Starcraft Remastered 1.18+ no longer launching in Wine

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44383 Zel Uneec <zculek(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zculek(a)gmail.com --- Comment #1 from Zel Uneec <zculek(a)gmail.com> --- I can confirm this, just as a dozen of other players who reported it on Battle.net forums: https://us.battle.net/forums/en/starcraft/topic/20761086661?page=6 The game doesn't work after the latest patch/update - version 1.21.2.3514 (patch info: https://us.battle.net/forums/en/starcraft/topic/20761086661#post-1) Battle.net application works the same as before, no issues with it, other games can be started and played (e.g. Starcraft 2). As reported by Igor Polyakov - the game doesn't start - when hitting "Play", throwing only segmentation fault, e.g.: err:seh:setup_exception_record stack overflow 1456 bytes in thread 015b eip 7bc69df8 esp 00240d80 stack 0x240000-0x241000-0x340000 It's also affecting 32bit Windows users and developers have confirmed that they have narrowed the issue to 32bit Windows: "Posted by Matt Sherman 01/19/2018 04:10 PM: We have narrowed the issue down to 32bit Windows." So, most probably the solution lies there. -- 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.

Jan. 21, 2018

[Bug 44391] Star Trek Online: Hang when clicking "Engage"

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44391 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Severity|blocker |normal CC| |dark.shadow4(a)web.de URL| |http://store.steampowered.c | |om/app/9900/Star_Trek_Onlin | |e/ --- Comment #2 from Fabian Maurer <dark.shadow4(a)web.de> --- Not a blocker, that importance is reserved for bugs that blocks development and/or testing work. I linked the URL I guessed, tell me if that's the wrong program. Just for clarification, the launcher works but the game itself doesn't start up? Not sure if that OpenGL error can cause such problems, but I guess it can. Anyways, you need to fix that issue or things will go wrong. I'd fix that, and then report back again. What driver do you use? Is it up to date and properly installed? -- 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.

Jan. 21, 2018

[Bug 44391] Star Trek Online: Hang when clicking "Engage"

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44391 --- Comment #1 from Michael B. Trausch <mbt(a)fortifiedtechsystems.com> --- Oh, and as an additional note: The strace output shows what happens, but I don't have anything in the Wine output (or in STO's debugging output) that shows _anything_ stepping out of the ordinary or going wrong. There is minimal debug output from WINE, the last 13 lines being: 0009:fixme:wbemprox:client_security_Release 0xf767682c libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast 0009:err:wgl:X11DRV_WineGL_InitOpenglInfo couldn't initialize OpenGL, expect problems 0009:fixme:wbemprox:enum_class_object_Next timeout not supported 0009:fixme:win:EnumDisplayDevicesW ((null),0,0x32db14,0x00000000), stub! 0009:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION 0009:fixme:thread:SetThreadIdealProcessor (0xe8): stub 0009:fixme:iphlpapi:NotifyAddrChange (Handle 0x32cb6c, overlapped 0x45ac6788): stub 0009:fixme:winsock:WSALookupServiceBeginW (0x32cc6c 0x00000ff0 0x32ccb4) Stub! [0121/113515:ERROR:network_change_notifier_win.cc(143)] WSALookupServiceBegin failed with: 0 003d:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet 0009:fixme:imm:ImmReleaseContext (0x30050, 0x4bd54fb8): stub Of course, I don't know that the OpenGL error has anything to do with the hang; it appears that it could be as simple as a read-from-not-ready IPC channel? -- 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.

Jan. 21, 2018

[Bug 44391] New: Star Trek Online: Hang when clicking "Engage"

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=44391 Bug ID: 44391 Summary: Star Trek Online: Hang when clicking "Engage" Product: Wine Version: 3.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mbt(a)fortifiedtechsystems.com Distribution: --- Updated to Wine 3.0 and decided to try STO to see if it would work. The upside is that it works better than it did when I tried it last time, but it still doesn't work. It patches (slowly, but it does finish), but when clicking the "Engage" button after the patch has done, the program blocks, never to be heard from again. Now, the debug output in total is too large to even really attach as a compressed archive of files, so I'm going to defer to waiting for a detailed request for information. However, what I _do_ know is that the program is blocking on a read of a pipe file descriptor that is apparently not ready. The pipe is created during program startup: pipe2([7, 8], O_CLOEXEC) = 0 And then (MUCH, MUCH LATER), when I click on the Engage button: write(3, "\v\1\0\0\0\0\0\0\0\0\0\0\234\1\0\0D\244\254E\0\0\0\0D\244\254E\0\0\0\0"..., 64) = 64 read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM CHLD IO], [], 8) = 0 writev(3, [{iov_base="\32\0\0\0000\0\0\0\0\0\0\0\2\0\0\0\330\3162\0\0\0\0\0\377\377\377\377\377\377\377\177"..., iov_len=64}, {iov_base="\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=40}, {iov_base="\1\0\0\0\340\1\0\0", iov_len=8}], 3) = 112 read(5, "\3\1\0\0\0\0\0\0\377\377\377\377\377\377\377\177\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 read(7, It will sit for _forever_ that way. (At that point, it is still the socket from earlier; I actually worked backwards from the fd number in /proc/$PID/fd/7 in order to figure out where it was instantiated in the log file.) The only way out of it is to kill the process, which then wraps out the log as thus: read(7, <unfinished ...>) = ? +++ killed by SIGKILL +++ At that point, of course, the program ends and Wine shuts back down. Retrial does the same time, and it does not appear to matter what version of Windows WINE is set to report. I would _love_ to report more information. But I need to be told what to gather to turn this into a _really_ useful bug report. STO is just about the only thing I boot up Windows for... it'd sure be nice to be rid of that requirement! Thanks, and keep up the good work. -- 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.

Jan. 21, 2018