wine-bugs November 2011

wine-bugs@winehq.org

1 participants
9461 discussions

[Bug 25454] New: scifinder: Non-English character on certain pages (ie. search result)
by wine-bugs＠winehq.org 05 Feb '12

05 Feb '12

http://bugs.winehq.org/show_bug.cgi?id=25454 Summary: scifinder: Non-English character on certain pages (ie. search result) Product: Wine Version: 1.3.8 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdi32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: jian_xing(a)hotmail.com Created an attachment (id=32396) --> (http://bugs.winehq.org/attachment.cgi?id=32396) Screen shot of the scifinder windows with wrong character This is a regression bug. Wine 1.3.5 does not have the bug. Characters on certain pages are not displayed as English The error message from the terminal is: fixme:gdi:ExtCreatePen Hatches not implemented -- 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 28190] New: winepath: No output in wineconsole
by wine-bugs＠winehq.org 05 Feb '12

05 Feb '12

http://bugs.winehq.org/show_bug.cgi?id=28190 Summary: winepath: No output in wineconsole Product: Wine Version: 1.3.26 Platform: x86 OS/Version: All Status: NEW Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com To reproduce this start the console with 'wine wineconsole cmd' and then type 'winepath c:' in the wine console. The usage will be displayed in the terminal in which you started the wineconsole instead of in wineconsole itself. This is because winepath uses regular Unix stdio functions like printf() instead of WriteConsole(). See the XCOPY_wprintf() function in programs/xcopy/xcopy.c or the output_*() functions in programs/net/net.c for a model on how to fix this. After fixing this, verify that running 'winepath c:' still works fine in a regular xterm or equivalent. (split off from bug 13861) -- 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 11670] New: Anno 1602 page fault
by wine-bugs＠winehq.org 04 Feb '12

04 Feb '12

http://bugs.winehq.org/show_bug.cgi?id=11670 Summary: Anno 1602 page fault Product: Wine Version: 0.9.55. Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: anakin.skyw(a)gmx.de Created an attachment (id=10881) --> (http://bugs.winehq.org/attachment.cgi?id=10881) Output of wine 1602 While playing Anno 1602 Königsedition (1602AD Kings edition), wine crashes with an unhandled page fault after about one minute of play. See Attachment for output. This is wine-0.9.55 compiled on Gentoo. -- 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 22559] New: Final Fantasy 8: text is rendered incorrectly
by wine-bugs＠winehq.org 03 Feb '12

03 Feb '12

http://bugs.winehq.org/show_bug.cgi?id=22559 Summary: Final Fantasy 8: text is rendered incorrectly Product: Wine Version: 1.1.43 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: kgbricola(a)web.de CC: thunderbird2k(a)gmail.com In FF8 the text rendering is broken since commit 9fec1a02b9e13969f929a3eed249e67773286033 . This is with a geforce8 and driver 195.36.15. The broken rendering is shown here ( http://bugs2.winehq.org/attachment.cgi?id=27638 ). >From the commit message I guess, I have to try it on windows, to see if the rendering is also broken. Changing the FF8 render engine to uses software mode works around that problem. 9fec1a02b9e13969f929a3eed249e67773286033 is the first bad commit commit 9fec1a02b9e13969f929a3eed249e67773286033 Author: Roderick Colenbrander <thunderbird2k(a)gmail.com> Date: Mon Apr 5 20:05:15 2010 +0200 wined3d: Disable paletted texture support. It was only offered on a few cards, so can be missed. :040000 040000 b11ffa7bd20131ea4a3416c5b5b07e0263847c66 71fb12b39fd165362923aa34f5e5283568e688e9 M dlls -- 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 22778] New: PlayOnline viewer's window is not correctly updated
by wine-bugs＠winehq.org 03 Feb '12

03 Feb '12

http://bugs.winehq.org/show_bug.cgi?id=22778 Summary: PlayOnline viewer's window is not correctly updated Product: Wine Version: 1.1.44 Platform: x86 URL: http://dl.square-enix.co.jp/polus/setup.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: wylda(a)volny.cz Created an attachment (id=28102) --> (http://bugs.winehq.org/attachment.cgi?id=28102) pol.exe refresh problem when in windowed mode In windowed mode, when you move app's window that only part is visible, then in this partially visible state is not correctly updated. 1) Probably nobody can explain that better than Henri I think what happens is that the blit is rejected because it's partially outside the screen. While moving the window to the outside that isn't very noticeable, but as soon as you move it back you see the now cleared parts of the window that don't get updated until the window is fully inside the screen again. 2) Another test scenario: When app's window is only partly visible and then resized, it becomes black. Attachment shows the 1st test scenario (they are probably related, thus in one bug report). Starting line for this bug report is wine-1.1.44-322-g5cc00e8 (there were many bug before: bug 22145, bug 22197, bug 22290, bug 22294, bug 22311, bug 22735). -- 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 14

[Bug 17808] New: AutoCAD Mechanical 2007 fails to install
by wine-bugs＠winehq.org 03 Feb '12

03 Feb '12

http://bugs.winehq.org/show_bug.cgi?id=17808 Summary: AutoCAD Mechanical 2007 fails to install Product: Wine Version: 1.1.17 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com I'm using Wine 1.1.17 (compiled from source using gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) ) on Fedora 10 i386. I installed gecko,msxml3,vcrun2005,dotnet20,corefonts,gdiplus through winetricks. The problem is that AutoCAD Mechanical 2007 fails to install properly (default installation). It doesn't crash and AutoCAD installer doesn't notify about any error. On the end of the installation it shows that AutoCAD was installed successfully, but it does not because there wasn't copied all files. The error in terminal err:msi:msi_cabextract FDICopy failed err:msi:ACTION_InstallFiles Failed to extract cabinet: L"acad6.CAB" err:msi:ITERATE_Actions Execution halted, action L"InstallExecute" returned 1627 -- 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 17806] New: AutoCAD LT 2008 fails to install
by wine-bugs＠winehq.org 03 Feb '12

03 Feb '12

http://bugs.winehq.org/show_bug.cgi?id=17806 Summary: AutoCAD LT 2008 fails to install Product: Wine Version: 1.1.17 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: lukasz.wojnilowicz(a)gmail.com Created an attachment (id=20038) --> (http://bugs.winehq.org/attachment.cgi?id=20038) WINEDEBUG=+msi Wine 1.1.17 I'm using Wine 1.1.17 (compiled from source using gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) ) on Fedora 10 i386. I installed gecko,msxml3,vcrun2005,dotnet20,corefonts,gdiplus through winetricks. The problem is that AutoCAD LT 2008 PL fails to install (default installation). It doesn't crashes but the AutoCAD installer notifies about that. The error in terminal is (installation stops at this) err:msi:ITERATE_Actions Execution halted, action L"InstallExecute" returned 1603 -- 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 27937] New: winmm kept busy playing silence after play finishes
by wine-bugs＠winehq.org 02 Feb '12

02 Feb '12

http://bugs.winehq.org/show_bug.cgi?id=27937 Summary: winmm kept busy playing silence after play finishes Product: Wine Version: 1.3.25 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mmdevapi AssignedTo: wine-bugs(a)winehq.org ReportedBy: hoehle(a)users.sourceforge.net CC: aeikum(a)codeweavers.com The winmm player is kept busy for several seconds after audible rendering ends. This is easily reproduced using my MCI shell from bug #20232, comment #10. Issue these commands to the MCI: open 8k8bitpcm.wav alias 8 ; any sample with at least 2 seconds of data play 8 from 1000 to 2000 notify ; play sample from position 1s to 2s play 8 from 1000 to 2000 WAIT status 8 mode I recommend to use a multi-line copy&paste to the console instead of typing. The MCIWAVE player will correctly play 1 second worth of data. After that however, a random amount of upto 4 messages about ALSA pcm underrun are sent to the console, approx. 1 per second. It's only after those that the player eventually stops, i.e. execution of the synchronous command ends. The command "status 8 mode" serves to show when execution of the previous command ends. I suspect the cause is the way mmdevapi handles silence and/or feeds too much data into the "default" ALSA device. I have no idea where that 1s log message spacing comes from. Expected behaviour (as in 1.3.24): the synchronous (WAIT flag) player is kept busy for 1 second, after which the MCI shell processes the next command. Upto one ALSA pcm underrun log message is the norm, since indeed WINMM is closed only after all buffers (headers in waveOut* speak) have been returned to the app, i.e. there's a tiny gap between "played last header => Set Event" and waveOutClose. I.e. one underrun is designed into the WINMM API, after playing ends. -- 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 29122] New: Sonic R has rendering (color keying) issues in Direct3D mode
by wine-bugs＠winehq.org 02 Feb '12

02 Feb '12

http://bugs.winehq.org/show_bug.cgi?id=29122 Bug #: 29122 Summary: Sonic R has rendering (color keying) issues in Direct3D mode Product: Wine Version: 1.3.32 Platform: x86-64 URL: http://www2.sega.co.jp/download/pc/sonicr/sonicr.exe OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Classification: Unclassified Regression SHA1: c8901d6f6253f6c97610eb1068ac4ff89758ed0a When Sonic R is run with the Direct3D renderer, it has some rendering issues (various objects have a green background instead of transparent) as seen in this screenshot: http://appdb.winehq.org/appimage.php?iId=9421 The DirectDraw renderer works without this problem. According to bug 21878, comment 5, it's a regression caused by: commit c8901d6f6253f6c97610eb1068ac4ff89758ed0a Author: Stefan Dösinger <stefandoesinger(a)gmx.at> Date: Fri Jun 9 19:36:12 2006 +0200 ddraw: Rewrite most of ddraw using WineD3D. Attachment 36962 from that bug fixes the issue. The demo has the same problem. It will most likely crash on startup due to a game bug unless the CPU power available to it is limited somehow, e.g. by running a program with high CPU usage while starting it. -- 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 23682] New: Suggestion: Editbox with terminal output in crash window
by wine-bugs＠winehq.org 02 Feb '12

02 Feb '12

http://bugs.winehq.org/show_bug.cgi?id=23682 Summary: Suggestion: Editbox with terminal output in crash window Product: Wine Version: 1.2 Platform: All OS/Version: All Status: UNCONFIRMED Severity: enhancement Priority: P5 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: VincentBeers(a)gmail.com This is a feature request, not a bug. Wine has an utterly useless "the application has crashed" window, or at least, it had for a while, I don't know if that has changed. Anyway, I think said window should have an unfoldable edit box containing all the terminal output of the application up to its crash, and a button to copy the content in this edit box. Finally, the crash description should indicate that you should copy that text and bring it to the Wine forums in order to get help/troubleshooting. Why? Because it makes giving feedback on Wine apps a lot quicker. A lot of us do actually run Wine apps from the terminal, but most newbies don't, and this is a way to assist them helping the Wine devs know about the problem a lot more quickly than the usual routine, which is: - Make a forum thread about how the app doesn't work, with little to no further info; - Have someone tell you to run in terminal; - Possibly learn to use the terminal, then run the app from there; - (At this point, a day may have passed) Run back to the forums with actual terminal output. Adding the text box with the terminal output straight into the "application crashed" window not only makes the window actually useful, but it also eliminates the delay that exists because new users may have to be assisted in actually running the app from terminal. Further notes: of course, from that point, the user may be advised as to how to run the app from terminal anyway, but at least for this time, or for any time when they just want to double-click an app to run, they'll get the actual log much more quickly. -- 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

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 November 2011