wine-bugs July 2014

wine-bugs@winehq.org

1 participants
9888 discussions

[Bug 34865] New: Can't execute mingw toolchain provided by Rtools
by wine-bugs＠winehq.org 23 Jan '20

23 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=34865 Bug #: 34865 Summary: Can't execute mingw toolchain provided by Rtools Product: Wine Version: 1.7.4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mail(a)kirill-mueller.de Classification: Unclassified I can't execute "R CMD INSTALL" on an installation of R + Rtools in Wine (latest version from PPA "ppa:ubuntu-wine/ppa"). A reproducible script and console output can be found here: https://gist.github.com/krlmlr/7333242 . The script will set and write to $WINEPREFIX and download to $DOWNLOAD_DIR. Unfortunately, the logs do not show enough detail. After the line `about to run R CMD SHLIB -o kimisc.dll rcpp_hello_world.cpp RcppExports.cpp --debug`, a call to `gcc` is made. (I have added the output of the same call on my Linux system to the Gist.) To me, it seems that the calling process is not notified when the child process has completed, and it stops after a timeout. My hope is that this has been seen before and that there's an easy fix. I'm really new to Wine. -- 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.

2 11

[Bug 35344] New: Cygwin's post-install scripts fail on fork errors
by wine-bugs＠winehq.org 23 Jan '20

23 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=35344 Bug ID: 35344 Summary: Cygwin's post-install scripts fail on fork errors Product: Wine Version: 1.7.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mail(a)georg.so Classification: Unclassified Executing 'wine setup-x86.exe' seems to work quite well (you can step through the wizard, packages are downloaded and extracted) until the post-installation bash scripts are executed. Then I get for each script a message like: running: C:\cygwin\bin\bash.exe --norc --noprofile "/etc/postinstall/glib2.0.sh" [..] fixme:ntdll:NtQueryInformationProcess (process=0xffffffff) Unimplemented information class: ProcessSessionInformation [..] fixme:ntdll:NtQueryVolumeInformationFile 0xf0: faking attribute info fixme:ntdll:NtQueryVolumeInformationFile 0xec: faking attribute info fixme:ntdll:NtQueryInformationFile Unsupported class (34) [..] fixme:ntdll:NtQueryVolumeInformationFile 0xf4: faking attribute info fixme:ntdll:NtQueryInformationFile Unsupported class (8) [..] fixme:ntdll:NtQueryVolumeInformationFile 0xfc: faking attribute info [..] fixme:ntdll:NtQueryVolumeInformationFile 0x100: faking attribute info fixme:ntdll:NtQueryVolumeInformationFile 0x124: faking attribute info [..] fixme:ntdll:NtQueryVolumeInformationFile 0x128: faking attribute info [..] /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: retry: Resource temporarily unavailable /etc/postinstall/glib2.0.sh: fork: Resource temporarily unavailable abnormal exit: exit code=254 The fork error message are always displayed after some kind of timeout. Where to get the setup-x86.exe: http://cygwin.com/setup-x86.exe $ md5sum setup-x86.exe c9818d3500e42fd9eb755d424450871a setup-x86.exe Executing Cygwin's setup exe inside wine looks a little bit silly, but I want to create a reference cygwin installation for deployment purposes. see also: http://wiki.winehq.org/CygwinSupport -- 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.

2 13

[Bug 35561] New: Some MSYS2 commands generate a stackdump
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=35561 Bug ID: 35561 Summary: Some MSYS2 commands generate a stackdump Product: Wine Version: 1.7.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: irwin(a)beluga.phys.uvic.ca Classification: Unclassified Created attachment 47484 --> http://bugs.winehq.org/attachment.cgi?id=47484 strace log of execution of mintty The general problem is I cannot start MSYS2 (the successor to MSYS) using its msys2_shell.bat startup batch file (see directions at http://sourceforge.net/p/msys2/wiki/MSYS2 installation/ concerning how to start MSYS2). That batch file (which executes a number of different MSYS2 commands) exits almost immediately with a stack dump. Alexey Pavlov, the developer of MSYS2, suggested I narrow down the problem by attempting to execute the MSYS2 version of mintty.exe directly, and if that did not work (which was the case) then run that app via the MSYS2 strace.exe facility to help figure out what the exact problem is. MSYS2 strace.exe did appear to work and I attach its log (and also the associated stackdump for mintty.exe). Here are some additional details in case there are any difficulties replicating this issue. I have used 3 different versions of 32-bit Wine which I built myself on my Debian Wheezy system. Those are Unpatched Wine-1.6.1, patched Wine-1.6.1, and patched Wine-1.7.12. The patch used was "Hackish patch to fix APC problem" taken from http://bugs.winehq.org/show_bug.cgi?id=24018. The reason why that extremely small patch is relevant is MSYS2 is essentially a simplified modern Cygwin (as opposed to MSYS which is essentially a simplified ancient version of Cygwin). Because the patched versions give improved results (see below), apparently the modern bits of Cygwin that are still part of MSYS2 trigger at least the APC Wine bug for modern Cygwin that did not occur for older Cygwin versions. The version of MSYS2 I am using is msys2-base-i686-20140205.tar.xz. Unpacking that created a top-level directory name of msys32 which I have changed to MSYS2-20140205 to help keep better track of which version of MSYS2 I am trying. I ran the MSYS2 version of strace with the patched versions of Wine as follows: wine@raven> wineserver -k wine@raven> wineserver -p wine@raven> wineconsole --backend=curses cmd Microsoft Windows 5.1.2600 (1.7.12) Z:\home\wine\newstart>PATH=Z:\home\wine\newstart\MSYS2-20140205\bin;%PATH% Z:\home\wine\newstart>MSYS2-20140205\bin\strace.exe MSYS2-0140205\bin\mintty.exe > strace.log 1069046 [main] mintty 44 cygwin_exception::open_stackdumpfile: Dumping stack trace to mintty.exe.stackdump The mintty terminal momentarily appeared before the stackdump occurred. After that stack dump strace did not return (i.e., everything was hung), and the last line in strace.log at that point was 616 1255194 [main] mintty 44 pinfo::exit: Calling ExitProcess n 0x8B, exitcode 0x8B00 I exited the combination of mintty, strace, cmd, and wineconsole the brute-force way by typing "wineserver -k" in a different Linux xterm which added nothing else to strace.log. The strace and stackdump results for patched wine-1.6.1 and patched wine-1.7.12 were virtually identical (except for numerical data like PID numbers). I have attached the wine-1.7.12 versions. When initially investigating this issue I was using unpatched wine-1.6.1. The result of everything I tried was Wine error boxes concerning dll problems. Those error boxes reminded me very much of my troubles in trying to run modern Cygwin from Wine so I applied the APC-related patch, and sure enough, that got rid of the error boxes, and I could get a lot further before I ran into a different problem which is what I have described above. -- 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.

2 21

[Bug 13863] New: Armed Assault (ArmA) doesn't render any 3D graphics
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=13863 Summary: Armed Assault (ArmA) doesn't render any 3D graphics Product: Wine Version: 1.0-rc4 Platform: PC-x86-64 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: ben(a)atomnet.co.uk Created an attachment (id=13933) --> (http://bugs.winehq.org/attachment.cgi?id=13933) Entire log minus 40000 duplicate lines. The game fails to display any of the in-game graphics whether it's on the menu or inside the game itself. It still renders the HUD and Menu's themselves, but not the actual 3D game graphics. It spits out the errors (the ones which appear many times in the attached log) about 5000 times a second. -- 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.

2 43

[Bug 34146] New: Wings of Prey demo background image in launcher is not shown
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=34146 Bug #: 34146 Summary: Wings of Prey demo background image in launcher is not shown Product: Wine Version: 1.6 Platform: x86 URL: http://www.fileplanet.com/208822/200000/fileinfo/Wings -of-Prey--Demo OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: andrey.goosev(a)gmail.com Classification: Unclassified Created attachment 45421 --> http://bugs.winehq.org/attachment.cgi?id=45421 launcher settings (wine) Launcher hasn't background image. -- 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.

2 14

[Bug 33476] New: fxc, the Microsoft Effect Compile, to work due to d3d
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=33476 Bug #: 33476 Summary: fxc, the Microsoft Effect Compile, to work due to d3d Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: titan.costa(a)gmail.com Classification: Unclassified Created attachment 44310 --> http://bugs.winehq.org/attachment.cgi?id=44310 fxc log Hi, I can't get the fxc, the Microsoft Effect Compile, to work. Something goes wrong with d3d. The command line is: wine fxc.exe /T fx_2_0 BasicHLSL.fx Both fxc.exe and BasicHLSL.fx come from the DXSDK. d3dcompiler_43.dll must be set as native. Here is the output: NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. fixme:win:EnumDisplayDevicesW ((null),0,0x32f6e8,0x00000000), stub! err:d3d:context_create Failed to set pixel format 1 on device context 0x80026. err:d3d:context_choose_pixel_format Can't find a suitable iPixelFormat err:d3d:context_create Failed to set pixel format 1 on device context 0x6002b. fixme:d3d:wined3d_get_format Can't find format WINED3DFMT_R24_UNORM_X8_TYPELESS (0x49) in the format lookup table fixme:d3d:getDepthStencilBits Unsupported depth/stencil format WINED3DFMT_UNKNOWN. err:d3d:context_create Failed to set pixel format 25 on device context 0x10033. err:d3d:context_create Failed to set pixel format 13 on device context 0x10035. err:d3d:context_choose_pixel_format Can't find a suitable iPixelFormat err:d3d:context_create Failed to set pixel format 1 on device context 0x10037. Failed to create D3D device Please check your SDK installation. disassembly failed; no disassembly produced -- 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.

2 15

[Bug 32596] New: Skydrift background glitches
by wine-bugs＠winehq.org 21 Jan '20

21 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=32596 Bug #: 32596 Summary: Skydrift background glitches Product: Wine Version: unspecified Platform: x86 OS/Version: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: paulthetall(a)gmail.com Classification: Unclassified The game Skydrift works fine itself, but it has some nasty background glitches which are very annoying. Especially in some specific levels this makes the game un-enjoyable. Seems this counts for everyone tested this game: http://appdb.winehq.org/objectManager.php?sClass=version&iId=25176&iTesting… http://appdb.winehq.org/objectManager.php?sClass=version&iId=25176&iTesting… Have a screenshot attached. If you need me to do some test debugrun stuff with some extensions let me know. Mac OSX 10.8.2 AMD Radeon 6770M graphicscard -- 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.

2 10

[Bug 29092] New: Myst Masterpiece crashes on game entry
by wine-bugs＠winehq.org 19 Jan '20

19 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=29092 Bug #: 29092 Summary: Myst Masterpiece crashes on game entry Product: Wine Version: 1.3.32 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: michael(a)mizapf.de Classification: Unclassified Myst Masterpiece Edition crashes on game entry, i.e. when you touch the first link book. Link sound occurs, then a Program Error window pops up, reporting that "The program mystmaster2k-d.exe has encountered a serious problem and needs to close". The close button does not shut down the application, need to close the window. Same results for myst.exe, myst9x.exe, and mystmaster2k-d.exe. Reinstall of Myst did not help. Seems to be a regression some time ago, because I could play the same game about a year ago when it stopped working after a new OS installation (including a new wine version). I gave up on it and tried to run it again just recently but things seem to have not changed. Last lines on console: fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels fixme:alsa:AudioClient_GetMixFormat Don't know what to do with 10000 channels, pretending there's only 2 channels fixme:ddraw:DirectDrawEnumerateExA flags 0x00000001 not handled fixme:win:EnumDisplayDevicesW ((null),0,0x31aee0,0x00000000), stub! fixme:font:CreateScalableFontResourceW (0,L"C:\\windows\\QTFont.for",L"C:\\windows\\QTFont.qfn",(null)): stub fixme:d3d:wined3d_device_decref Device released with resources still bound, acceptable but unexpected. fixme:d3d:wined3d_device_decref Leftover resource 0x1c1fe8 with type WINED3DRTYPE_SURFACE (0x1). wine: Unhandled page fault on read access to 0x0251736d at address 0x36fe0b8 (thread 002d), starting debugger... -- 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.

2 39

[Bug 33999] New: IncrediMail crashes on startup (GetNextDlgTabItem shouldn't return NULL?)
by wine-bugs＠winehq.org 17 Jan '20

17 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=33999 Bug #: 33999 Summary: IncrediMail crashes on startup (GetNextDlgTabItem shouldn't return NULL?) Product: Wine Version: 1.6-rc4 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Classification: Unclassified After working around bug 33996 with 'winetricks wsh56vb vcrun2005', and bug 33998 with 'winetricks ie7', it eventually finishes its very long 'configuring' progress bar. The next dialog crashes when you click 'next', with: Unhandled exception: page fault on read access to 0x00000020 in 32-bit code (0x25ff6766). +relay,+seh reveals: 006e:Ret user32.GetNextDlgTabItem() retval=00000000 ret=67b5438d trace:seh:raise_exception code=c0000005 flags=0 addr=0x67b54393 ip=67b54393 tid=006e And applying the patch http://marc.info/?l=wine-patches&m=127045782322161&q=raw "user32/dialog.c: GetNextDlgTabItem returns hwndDlg if next item not found" by Mikhail Maroukhine works around the problem. Tested with f05f8f39b559f2763f9e917dacb15c225357e7c4 IncrediMailSetup.exe -- 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.

2 6

[Bug 26037] New: Tahoma Bold is not bold
by wine-bugs＠winehq.org 13 Jan '20

13 Jan '20

http://bugs.winehq.org/show_bug.cgi?id=26037 Summary: Tahoma Bold is not bold Product: Wine Version: 1.3.12 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: fonts AssignedTo: wine-bugs(a)winehq.org ReportedBy: mansonigor(a)gmail.com Created an attachment (id=33207) --> (http://bugs.winehq.org/attachment.cgi?id=33207) screenshot from wordpad Tahoma Bold is bold only when has 9pt Difference between "bold" and "bold italic" is that "bold italic" has larger inverval between characters. But it's not bold. -- 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.

2 17

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 July 2014