February 2016 - Wine-bugs - list.winehq.org

[Bug 34375] New: Terraria: Toggling fullscreen retains "Always On Top" flag
by wine-bugs＠winehq.org 29 Apr '17

29 Apr '17

http://bugs.winehq.org/show_bug.cgi?id=34375 Bug #: 34375 Summary: Terraria: Toggling fullscreen retains "Always On Top" flag Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: billy65bob(a)gmail.com Classification: Unclassified When running terraria, changing from a fullscreen state to a windowed state (such as by pressing Alt + Enter), the window retains the "always on top" flag. It can easily enough be removed manually via Alt+F3. The window is otherwise correct. OS: Arch Linux x86_64 WM: KWin 4.11 Tested wine revision: 8ef3a142263e6db11f1514f77b3de84c8b08d7a0 -- 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 7

[Bug 16783] New: Guild Wars: Game window is not displayed
by wine-bugs＠winehq.org 29 Apr '17

29 Apr '17

http://bugs.winehq.org/show_bug.cgi?id=16783 Summary: Guild Wars: Game window is not displayed Product: Wine Version: 1.1.12 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: siska.pe(a)gmail.com Created an attachment (id=18454) --> (http://bugs.winehq.org/attachment.cgi?id=18454) Log of Gw.exe After starting Guild Wars (GW), download window appear, but main game window with login is not displayed. Music Plays etc. GW worked well with wine version 1.1.9, both 1.1.10 up to 1.1.12 have same problem. In attachment is full log from console. Error is: err:d3d:getColorBits Unsupported format: WINED3DFMT_R32F Configuration: Kernel - 2.6.27 Nvidia - quadro mobile nvs 140 (177.80 driver version) -- 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 19

[Bug 32063] New: Guild Wars: Orange square appearing
by wine-bugs＠winehq.org 29 Apr '17

29 Apr '17

http://bugs.winehq.org/show_bug.cgi?id=32063 Bug #: 32063 Summary: Guild Wars: Orange square appearing Product: Wine Version: 1.5.15 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: sworddragon2(a)aol.com Classification: Unclassified Created attachment 42259 --> http://bugs.winehq.org/attachment.cgi?id=42259 Orange square In the area Majestry's Rest I saw a small orange square appearing. After moving a few steps it disappeared. But if I'm moving a few steps back it appears again. The screenshot shows the position of the square. -- 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 3

[Bug 38460] New: winecfg hangs audio hangs while opening Audio tab (pulseaudio)
by wine-bugs＠winehq.org 29 Apr '17

29 Apr '17

https://bugs.winehq.org/show_bug.cgi?id=38460 Bug ID: 38460 Summary: winecfg hangs audio hangs while opening Audio tab (pulseaudio) Product: Wine Version: 1.7.41 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pva(a)gentoo.org Distribution: --- I've run winecfg from user that is not allowed to play music. After I click Audio tab winecfg hangs with no reaction and in console I see following message: err:pulse:pulse_contextcallback Context failed: Connection refused -- 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 32319] New: Direct3D output in SNES9x is blank
by wine-bugs＠winehq.org 28 Apr '17

28 Apr '17

http://bugs.winehq.org/show_bug.cgi?id=32319 Bug #: 32319 Summary: Direct3D output in SNES9x is blank Product: Wine Version: 1.5.18 Platform: x86-64 URL: http://files.ipherswipsite.com/snes9x/snes9x-1.53-win3 2.zip OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: markk(a)clara.co.uk Classification: Unclassified Created attachment 42658 --> http://bugs.winehq.org/attachment.cgi?id=42658 DirectDraw mode, stretch image disabled (this looks correct) I'm testing with Wine 1.5.18-72-g0c0b229, Lubuntu 11.10 x86-64, Nvidia driver 304.64, SNES9x 1.53. SNES9x can use Direct3D, DirectDraw or OpenGL output methods. The default is Direct3D. On my system, with the default settings the output area of the main window (i.e. excluding menu bar) is blank. To reproduce this issue: - Download and unzip SNES9x. - Download a SNES ROM image, e.g. from http://pdroms.de/files/supernintendoentertainmentsystem/skipp-and-friends-p… - Run SNES9x. Select File->Load Game... and select SAF.smc (or another ROM image you have handy). - At this point you should see graphics in the window, but it's blank. Select Video->Display Configuration..., change Output Method to DirectDraw and click OK. The correct output image appears. Change back to Direct3D and get a black window again. - Change to DirectDraw and un-check the "Stretch Image" checkbox. The image is no longer doubled in size, occupying the centre quarter of the window. That's correct. - If you now change output method to Direct3D, the Direct3D image does appear! It's in the upper left quarter of the window. It should be centred. - Even if you enable Stretch Image (select Video->Stretch Image or press Alt-Backspace) the image remains unchanged. You can also enable or disable bilinear filtering and there is no visible change. But if you switch to DirectDraw and back to Direct3D again when Stretch Image is enabled, get a blank window. It seems you only get anything displayed in Direct3D mode if Stretch Image is disabled before you switch from DirectDraw to Direct3D. Also of note... In both DirectDraw and Direct3D modes, if you click in the menu strip and move the mouse to open the various menus, the previously-drawn menus remain visible. They should not be. -- 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 7

[Bug 12311] New: Corman Lisp requires implementations for richedit stubs
by wine-bugs＠winehq.org 28 Apr '17

28 Apr '17

http://bugs.winehq.org/show_bug.cgi?id=12311 Summary: Corman Lisp requires implementations for richedit stubs Product: Wine Version: CVS/GIT Platform: PC URL: http://scguy318.freeshell.org/CormanLisp_3_01_setup.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: nodisgod(a)yahoo.com Corman Lisp (obtainable from http://www.cormanlisp.com/cgi/rgcorman/ccl_download_form30.cgi) running on current Git (wine-0.9.58-357-g338539c) hangs and fails to redraw or properly render the window. Outputted messages consists of: fixme:richedit:RichEditWndProc_common WM_STYLECHANGING: stub fixme:richedit:RichEditWndProc_common WM_STYLECHANGED: stub fixme:richedit:RichEditWndProc_common WM_STYLECHANGING: stub fixme:richedit:RichEditWndProc_common WM_STYLECHANGED: stub fixme:richedit:RichEditWndProc_common ECO_AUTOWORDSELECTION not implemented yet! fixme:richedit:RichEditWndProc_common ECO_AUTOVSCROLL not implemented yet! fixme:richedit:RichEditWndProc_common ECO_NOHIDESEL not implemented yet! thus indicating a richedit issue. Using native richedit resulted in a working window but unusually small text font size in the code window that could not be rectified by increasing font size. -- 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 22

[Bug 32426] New: TreeView of QvodSetupPlus5 unexpectedly draw a piece of blank area when clicking on a checkbox
by wine-bugs＠winehq.org 28 Apr '17

28 Apr '17

http://bugs.winehq.org/show_bug.cgi?id=32426 Bug #: 32426 Summary: TreeView of QvodSetupPlus5 unexpectedly draw a piece of blank area when clicking on a checkbox Product: Wine Version: 1.5.19 Platform: x86 URL: http://dl.kuaibo.com/QvodSetupPlus5.exe OS/Version: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Depends on: 32423 Classification: Unclassified 1. winetricks -q msxml3, works around Bug 32423 2. start the installer: $ QvodSetupPlus5.exe 3. click on any checkbox in the treeview Compare the two screenshot will found the bug. Workaround by `winetricks -q cc580` -- 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 10

[Bug 40007] New: Dirt 3 requires d3d11_immediate_context_CSSetShaderResources
by wine-bugs＠winehq.org 28 Apr '17

28 Apr '17

https://bugs.winehq.org/show_bug.cgi?id=40007 Bug ID: 40007 Summary: Dirt 3 requires d3d11_immediate_context_CSSetShaderResources Product: Wine Version: 1.9.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: mikk150(a)gmail.com Distribution: --- Created attachment 53453 --> https://bugs.winehq.org/attachment.cgi?id=53453 Backtrace Dirt 3 needs whole bunch of d3d11 methods to be implemented -- 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 29287] New: Heroes of Might and Magic IV: performance issues with Opengl renderer
by wine-bugs＠winehq.org 26 Apr '17

26 Apr '17

http://bugs.winehq.org/show_bug.cgi?id=29287 Bug #: 29287 Summary: Heroes of Might and Magic IV: performance issues with Opengl renderer Product: Wine Version: 1.3.34 Platform: x86 OS/Version: Linux Status: NEW Keywords: regression Severity: minor Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com CC: hverbeet(a)gmail.com Classification: Unclassified Regression SHA1: 94c0da184e18252ca2df7f9f462e9a4df9c5f2df Created attachment 37882 --> http://bugs.winehq.org/attachment.cgi?id=37882 plain terminal output There is a noticeable slowdown in HoMM IV during gameplay with the default Opengl renderer. This is noticeable in the map screen (when the player is wandering around, collecting items and exploring the land), but it doesn't occur during combat. I tested with HoMM IV Complete (also available on GOG.com) Actually, there are 2 distinct issues, both of them are originating from the same commit. 1. the game is much slower than it was in 1.3.33 (or earlier): scrolling the map as well as animations are lagging/redrawing slowly. 2. the mouse pointer is acting weird: while moving the mouse pointer across the screen, it frequently jumps in different directions by several pixels. It makes pointing to an icon or item more difficult. The result of the regression test: 94c0da184e18252ca2df7f9f462e9a4df9c5f2df is the first bad commit commit 94c0da184e18252ca2df7f9f462e9a4df9c5f2df Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Thu Dec 1 07:31:41 2011 +0100 wined3d: Create a PBO in surface_load_location() even if SFLAG_INSYSMEM is already set. In the longer term, sysmem and pbo should be separate resource locations. :040000 040000 0ea129726096c1508557eacfc8272cf884f0c61b 4e1bfdfeccfc95e0b700f75d6841dbb7cc1889da M dlls Reverting the patch on wine-1.3.34-166-g71199ea fixed both problems. No demo available. Workaround: ddr=gdi Other opened bugs related to this commit: bug #29234, bug #29235. The attached console log is probably not much of use. Please let me know if you need a log with debug channels enabled. Fedora 16 x86 Nvidia 250 / driver 290.10 X.Org X Server 1.11.2 -- 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 39505] New: Wine renders fonts out of way
by wine-bugs＠winehq.org 25 Apr '17

25 Apr '17

https://bugs.winehq.org/show_bug.cgi?id=39505 Bug ID: 39505 Summary: Wine renders fonts out of way Product: Wine Version: 1.7.53 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: a.shahbazi91(a)gmail.com CC: bunglehead(a)gmail.com, dmitry(a)baikal.ru Distribution: --- Created attachment 52647 --> https://bugs.winehq.org/attachment.cgi?id=52647 Screenshot_Antialiasing_Disabled Wine font rendering seems faulty. The attached screenshots show wine wordpad showing multiple lines with different sizes for the "Times New Roman"(default font in many apps) beside libreoffice writer showing the same lines. * On the two screenshots I have antialiasing enabled and disabled for wine but not much difference. ** I used wine 1.7.53 but it seems to be an old wine bug *** I use ubuntu based distro and native apps other than libreoffice have no problem rendering fonts **** I checked with Tahoma font and it seems out of way too Some of the differences I noticed: - Glyphs seem to be rendered wider than libreoffice(compare "H"s in 20pt). It's worse when antialiasing is enabled. - At the same time that the glyphs seem to be rendered wider the width of lines seem to be lower(compare "0"s in 20) -"!" is not rendered straight in regular fonts! - exclamation-mark tail ending is not that sharp(compare 20pt bold) - 9pt and 12pt are complete mess! -- 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