February 2011 - Wine-Bugs - list.winehq.org

[Bug 18245] New: Polygon Love 2 - model shows up but doesn't have any animation
by wine-bugs＠winehq.org April 13, 2011

April 13, 2011

http://bugs.winehq.org/show_bug.cgi?id=18245 Summary: Polygon Love 2 - model shows up but doesn't have any animation Product: Wine Version: 1.1.20 Platform: PC OS/Version: Windows XP Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: knight666(a)gmail.com Created an attachment (id=20756) --> (http://bugs.winehq.org/attachment.cgi?id=20756) A screenshot of the model standing with her arms wide First off, launching Polygon Love 2 from the command line is impossible, it crashes with the following output: knight666(a)Katja:~$ wine "/media/disk/Program Files/Purple Heart/Polygon Love 2/PL2.exe" fixme:d3d:IWineD3DImpl_FillGLCaps OpenGL implementation supports 32 vertex samplers and 32 total samplers fixme:d3d:IWineD3DImpl_FillGLCaps Expected vertex samplers + MAX_TEXTURES(=8) > combined_samplers fixme:win:EnumDisplayDevicesW ((null),0,0x32f830,0x00000000), stub! fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface It is possible to launch the game by double clicking the exe. Once loaded, everything works as it's supposed to, but once you go in the dressing room, your character doesn't display any animation, and just stands there with her arms wide. I've attached a screenshot demonstrating the effect. Computer specs: - Wine 1.1.20 (latest version at time of writing) - Ubuntu 8.10 - 2.2 GHz AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ - 1 GB RAM - 128 MB (I think) nVidia Corporation GeForce 8600 GT -- 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 9

[Bug 18292] New: Make 8.3 names for LFNs more "Windows-like"
by wine-bugs＠winehq.org April 10, 2011

April 10, 2011

http://bugs.winehq.org/show_bug.cgi?id=18292 Summary: Make 8.3 names for LFNs more "Windows-like" Product: Wine Version: 1.1.20 Platform: PC URL: http://source.winehq.org/source/dlls/kernel32/path.c OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk When Windows creates 8.3 names for long file names, it does so in the form Progra~1 and increments the number by one with each new creation of a similar filename. So, Program Files --> Progra~1 Programmers --> Progra~2 Program Blah blah --> Progra~3 and so on. Under Wine, the 8.3 filenames seem somewhat random (PROG~HAE for example). Is it possible to implement this behaviour? It would make it easier to guess short path names, which makes it easier to add paths to the registry (when needed for workarounds, for example). -- 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 8

[Bug 22059] New: when /dev/input/event* device is accessible, wine fails to consider calibration and correction factors of the linux joydev driver
by wine-bugs＠winehq.org April 10, 2011

April 10, 2011

http://bugs.winehq.org/show_bug.cgi?id=22059 Summary: when /dev/input/event* device is accessible, wine fails to consider calibration and correction factors of the linux joydev driver Product: Wine Version: 1.1.40 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: corvus-wine(a)cybertrench.com Created an attachment (id=26862) --> (http://bugs.winehq.org/attachment.cgi?id=26862) joydev log with event file accessible Linux provides the possibility to correct joystick raw values automatically when accessing /dev/input/js* devices, both autodetected/scaled and "hand-calibrated" with tools like "jscal" if wine uses /dev/input/js* for joystick access, it also takes the correction factors into account, so a joystick that has been calibrated under linux, will be calibrated correctly under wine. However if the /dev/input/event* file corresponding to the joystick device is accessible (at least for reading) wine seems to bypass the joydev driver and accesses the device on a lower (event) level, thus unaware of the calibration data and correction factors - whether manually set and autodetected! As a result programs run under wine that use a joystick but offer no inbuilt calibration option (which is most, since under native win32 joysticks are calibrated system wide in the input device area of the control center) will behave strangely as joysticks are potentially off-centered - mis-scaled - axis flipped - or even unable to cross the zero position at all. Depending on the actual joystick hardware and the required corrections. the attached log1.txt shows the output of a joystick using program (il2fb flightsim) started with dinput WINEDEBIUG output grep'd for "joydev" when the event device is accessible (and the joystick is unusable due to miscalibration > WINEDEBUG=+dinput wine il2fb.exe 2>&1 |grep joydev log2.txt shows the same output with /dev/input/event5 (the joystick event device) chmodded to 000 in this case the axis and buttons are mapped completely different, but centered and scaled correctly (given that the jopystick had been calibrated under linux using jscal) for obvious reasons this bug is only visible if the axis values reported by the event device, especially min and max: ... > cur=97, min=0, max=255, fuzz=0, flat=15 ... are not equal to the actually reachable minimum and maximum values. newer joysticks often autoscale in hard/firmware and actually reach those min/max values with little need for calibration, while some, especially older models, are in dire need of correction values since the actual range (as in this case) is more like 30 to 120 -- 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 5

[Bug 22212] New: Random Crashes in Sacred 2
by wine-bugs＠winehq.org April 8, 2011

April 8, 2011

http://bugs.winehq.org/show_bug.cgi?id=22212 Summary: Random Crashes in Sacred 2 Product: Wine Version: 1.1.41 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: JakobRau(a)web.de When playing sacred 2. from time to time wine crashes (sometimes in game (singleplayer and LAN), sometimes in the menu). It does not happen too often, but it is still annoying. I am using Wine 1.1.41. on Ubuntu Lucid. I am starting the game like this: WINEPREFIX=~/.wine/sacred2 wine sacred2.exe WINEDEBUG=+relay wouldn't work, but I hope you can get some stuff out of the logfile anyway. If you can help me getting it to start with +relay, I will be happy to post the log. -- 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 25910] New: Notepad tries to open a file using wrong sharing mode
by wine-bugs＠winehq.org April 8, 2011

April 8, 2011

http://bugs.winehq.org/show_bug.cgi?id=25910 Summary: Notepad tries to open a file using wrong sharing mode Product: Wine Version: 1.3.12 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: exclusion(a)gmail.com Notepad can't open file, that was opened in another program for writing, while Windows notepad can do it. Difference is in call to CreateFileW. Wine notepad: trace:file:CreateFileW L"D:\\Pr\\Trillian\\users\\default\\logs\\ICQ\\xxxxxx.log" GENERIC_READ FILE_SHARE_READ creation 3 attributes 0x80 Windows notepad: trace:file:CreateFileW L"D:\\Pr\\Trillian\\users\\default\\logs\\ICQ\\xxxxxx.log" GENERIC_READ FILE_SHARE_READ FILE_SHARE_WRITE creation 3 attributes 0x80 In particular, I can't open contact history in Trillian (IM client) while Message window of the contact is open (and the log file is opened for writing). -- 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 6

[Bug 24680] New: loader: segfault after loading krnl386.exe, while LoadLibraryEx for any buildin dll
by wine-bugs＠winehq.org April 8, 2011

April 8, 2011

http://bugs.winehq.org/show_bug.cgi?id=24680 Summary: loader: segfault after loading krnl386.exe, while LoadLibraryEx for any buildin dll Product: Wine Version: 1.3.4 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: loader AssignedTo: wine-bugs(a)winehq.org ReportedBy: wine.dev(a)web.de Created an attachment (id=31193) --> (http://bugs.winehq.org/attachment.cgi?id=31193) +loaddll,+process,+tid.txt Detected while testing https://answers.launchpad.net/ubuntu/+source/wine/+question/127977 When using "wine inetcpl.cpl" (or any other builtin dll: "wine gdi32.dll" as example), the referenced builtin dlls are loaded and a Segmentation fault occur after loading "krnl386.exe16" When loading a native dll, then no referenced dlls are loaded, and the error ".... gdi32.dll is a dll, not an executable") is printed to the console. No referenced dll must be loaded, as we have in ___wine_kernel_init: LoadLibraryExW( main_exe_name, 0, DONT_RESOLVE_DLL_REFERENCES ); After renaming "krnl386.exe16.so", the segfault does no longer occur and the expected message is visible on the terminal: 009:err:module:LdrInitializeThunk L"C:\\windows\\system32\\gdi32.dll" is a dll, not an executable The segfault is present on x86 and x86-64 (wine32) -- By by ... Detlef -- 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 4

[Bug 25301] New: Occasional sock_check_pollhup() error on Solaris
by wine-bugs＠winehq.org April 8, 2011

April 8, 2011

http://bugs.winehq.org/show_bug.cgi?id=25301 Summary: Occasional sock_check_pollhup() error on Solaris Product: Wine Version: 1.3.7 Platform: x86 OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: wineserver AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Created an attachment (id=32142) --> (http://bugs.winehq.org/attachment.cgi?id=32142) Additional sock_check_pollhup() traces On Solaris 10u5 I would sometimes get the following error: sock_init: ERROR in sock_check_pollhup() Apparently I'm not the only one since it's present in the log of bug 18334 (although that bug is about something else entirely). I have now found a way to reliably reproduce it on my system which is to run the following WineLib command: ./wine memtest.exe.so mmap 50 100 Of course make sure that the wine server is not running yet. The purpose of sock_check_pollhup() is to figure out what poll() does when a socket is closed. The error happens because the poll() call that immediately follows a shutdown() call returns no event. I then discovered that giving poll() a 1ms timeout fixes this problem although it still runs in 0.014 to 0.046ms. Note that strictly speaking poll() is allowed to return nothing when given a 0ms timeout: 'if timeout is 0, poll() returns immediately', which it does. Still it's annoying and could well be considered a poll() bug. The workaround seems ok though, especially since this is in code that's only invoked at startup. -- 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 6

[Bug 25680] New: Stale file associations are not properly removed
by wine-bugs＠winehq.org April 8, 2011

April 8, 2011

http://bugs.winehq.org/show_bug.cgi?id=25680 Summary: Stale file associations are not properly removed Product: Wine Version: 1.3.10 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: shell32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: patrakov(a)gmail.com In winemenubuilder.c, in cleanup_associations(), subkeys are deleted while their parent is being enumerated. So, if two consecutive subkeys are to be processed and deleted, only the first of them is actually processed. I.e., some stale associations are not cleared from desktop files and from the registry on the first run of wine winemenubuilder -a. -- 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 5

[Bug 20552] New: Memory leak in alloc_thread_tls?
by wine-bugs＠winehq.org April 8, 2011

April 8, 2011

http://bugs.winehq.org/show_bug.cgi?id=20552 Summary: Memory leak in alloc_thread_tls? Product: Wine Version: 1.1.32 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Valgrinding the chromium tests shows the leak 514 bytes in 2 blocks are definitely lost in loss record 796 of 971 by RtlAllocateHeap (heap.c:1421) by alloc_thread_tls (loader.c:889) by MODULE_DllThreadAttach (loader.c:1184) by start_thread (thread.c:464) on e.g. the following tests: ipc_tests: IPCChannelTest media_unittests: PipelineImplTest VideoRendererBaseTest WinAudioTest net_unittests: DirectoryListerTest ListenSocketTest ProxyScriptFetcherTest SingleThreadedProxyResolverTest TCPPingerTest TelnetServerTest URLRequestTestFTP URLRequestTestHTTP URLRequestTest To reproduce: mkdir demo cd demo wget -c http://kegel.com/wine/chromium/chromium-tests.tar.bz2 tar -xjvf chromium-tests.tar.bz2 valgrind --trace-children=yes --leak-check=full wine src/chrome/Debug/net_unittests.exe --gtest_filter=TCPPingerTest.Ping -- 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 4

[Bug 24800] New: wine try to use float texture even if driver don't support them
by wine-bugs＠winehq.org April 8, 2011

April 8, 2011

http://bugs.winehq.org/show_bug.cgi?id=24800 Summary: wine try to use float texture even if driver don't support them Product: Wine Version: 1.2.1 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fabio.ped(a)libero.it Created an attachment (id=31363) --> (http://bugs.winehq.org/attachment.cgi?id=31363) wine output with mesa git master r300 gallium driver The game Panzers II shows lot of wine warnings and mesa errors like: Mesa: User error: GL_INVALID_VALUE in glTexImage2D(internalFormat=0x822e) err:d3d:check_fbo_compat >>>>>>>>>>>>>>>>> GL_INVALID_VALUE (0x501) from Framebuffer format check @ utils.c / 968 fixme:d3d:check_fbo_compat Format WINED3DFMT_R32_FLOAT with rendertarget flag is not supported as FBO color attachment, and no fallback specified. Full output is attached. According to a mesa developer the problem is that current mesa git master implements ARB_texture_rg and wine thinks it also support R16G16_FLOAT textures: https://bugs.freedesktop.org/show_bug.cgi?id=30823 Indeed when disabling such mesa extension with the env variable: MESA_EXTENSION_OVERRIDE=-GL_ARB_texture_rg the warnings no longer appear (output also attached). Other than the warning I see no obvious visual differences. I am using wine 1.2.1 found on Ubuntu 10.10 with a Radeon X1600 (RV530) card using the gallium r300 driver. -- 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