wine-bugs May 2008

wine-bugs@winehq.org

2 participants
4586 discussions

[Bug 12166] New: Richedit "word wrap" refresh
by wine-bugs＠winehq.org 09 May '08

09 May '08

http://bugs.winehq.org/show_bug.cgi?id=12166 Summary: Richedit "word wrap" refresh Product: Wine Version: 0.9.58. Platform: Other URL: http://emuleplus.info OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: vladimiroski(a)gmail.com In the logs of the program, when changing the "word wrap" option of the RichEdit control, the option does not affect the behavior of the control until I select a different log, then switch back. This, I think, may be a "refresh" issue, on Windows the "word wrap" option affects the control behavior instantly. By the way, automatic scroll of RichEdit looks strange too, when automatic scroll is needed, it scroll to random places on the RichEdit. -- 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 12165] New: Wrong height on 1st list item, on eMule Plus preferences.
by wine-bugs＠winehq.org 09 May '08

09 May '08

http://bugs.winehq.org/show_bug.cgi?id=12165 Summary: Wrong height on 1st list item, on eMule Plus preferences. Product: Wine Version: 0.9.58. Platform: PC URL: http://emuleplus.info OS/Version: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: vladimiroski(a)gmail.com Created an attachment (id=11561) --> (http://bugs.winehq.org/attachment.cgi?id=11561) See the bug on the selected item. The first item on the left list of preferences of eMule Plus is getting at least twice of the height of other items following on the list. This of course is not the same on Windows, where all items have equal height. -- 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 15

[Bug 12064] New: SkySorter halts while starting
by wine-bugs＠winehq.org 09 May '08

09 May '08

http://bugs.winehq.org/show_bug.cgi?id=12064 Summary: SkySorter halts while starting Product: Wine Version: 0.9.57. Platform: PC URL: http://www.satnavigator.ru/page-id-439-a-dl.html OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mike2006michael(a)mail.ru CC: mike2006michael(a)mail.ru With Wine 0.9.20 or 0.9.36 this programm runs but in the latest versions I see this fixme only.. And Programm Halts fixme:systray:handle_incoming unhandled tray message: 4 -- 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 12052] New: Flatout 2, dinput_test: crashes if joystick axis mapping is enabled, different joystick sensitivity
by wine-bugs＠winehq.org 09 May '08

09 May '08

http://bugs.winehq.org/show_bug.cgi?id=12052 Summary: Flatout 2, dinput_test: crashes if joystick axis mapping is enabled, different joystick sensitivity Product: Wine Version: 0.9.56. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: ErV2005(a)rambler.ru because Wine currently maps joystick hat as axes (which makes playing IL2 really difficult), I've been trying to use axis mapping. However, some applications crash on startup if axis mapping is enabled, AND "POV" is mentioned somewhere. I'm using Thrustmaster USB (2960623) joystick. for jstest device information see jstest_info.txt. Under wine device feels different: joystick seems to have different sensitivity and small unexpected deadzone (which doesn't exist on windows). Without axis mapping joystick seems to work mostly fine, but joystick hat is being mapped as axes, not as Point-of-view control. dinput_test works normally and reports 2 failrues (see dinput_test_normal.txt for log). When I try to use following axis mapping (to make hat work in IL2): "X,Y,Z,POV1,Rz", dinput_test crashes on second test and hangs while printing backtrace. see dinput_test_crash.txt. For dinput and trace debug data see dinput_test_trace.txt (Aquired using "WINEDEBUG+=trace,dinput wine dinput_test.exe.so joystick") With this mapping Flatout 2 crashes after intro movies. see flatout_2_crash.txt With this mapping IL2 works fine, but doesn't recognize hat controls anyway. With another mapping: "X,Y,Z,POV1" dinput_test crashes in the same way. see dinput_test_crash2.txt for details. It looks like crashes occur only when POV1 is included in axis mapping. -- 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 11644] New: Crashes in the dinput device.c and joystick.c tests...
by wine-bugs＠winehq.org 09 May '08

09 May '08

http://bugs.winehq.org/show_bug.cgi?id=11644 Summary: Crashes in the dinput device.c and joystick.c tests... Product: Wine Version: 0.9.55. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput AssignedTo: wine-bugs(a)winehq.org ReportedBy: lionel_debroux(a)yahoo.fr I have a Microsoft Digital Media Pro keyboard, USB ID 045e:00b0 (description: http://www.microsoft.com/hardware/mouseandkeyboard/productdetails.aspx?pid=… ). As can be seen on the photo, this keyboard has a "zoom" slider, which is exposed to the computer as a joystick. When I'm running the dinput tests with WINEDEBUG=warn+heap, and this keyboard/joystick is plugged in, two tests, device.c and joystick.c, outright crash, due to accesses at address 0x55555555 (magic value indicating an access to uninitialized allocated memory). These two tests have been consistently crashing since around november 2007, when I started running "make test". I mentioned this problem as part of bug #9916 ("make test usually fails"): http://bugs.winehq.org/show_bug.cgi?id=9916#c27 At first, I tried debugging the issue on my own: * I have already submitted a patch for improved traces in dinput, which Alexandre committed as efc81cb233538ba72198ea9b80b160abfa0e8ecc on 2008-01-02; * I added a couple of printf (number of axes, number of buttons) to alloc_device in dlls/dinput/joystick_linux.c. but I came up to nothing interesting. Several interesting facts about the keyboard: * on this computer, a laptop Core 2 Duo @ 2 GHz with 2 GB of RAM running SimplyMEPIS 7.0 (kernel 2.6.22.x), the keyboard has 37 axes and 37 buttons (?!); * on another computer, a laptop Pentium 4 @ 2.6 GHz with 512 MB of RAM running SimplyMEPIS 6.5 (kernel 2.6.15.x), the keyboard has 37 axes and 7 buttons (?!); * on both computers, I have to unplug the keyboard if I want games such as PlanetPenguinRacer and Nexuiz to be playable. Otherwise, the penguin strongly drifts leftwards (PPR), or the weapon drifts up-leftwards very fast (Nexuiz). => there's certainly another problem outside of Wine (the kernel, since Wine uses the kernel API, and the number of buttons reported has changed between 2.6.15.x and 2.6.22.x ?). But still, the dinput implementation should try not to crash, even if it's fed up incorrect data - that's the reason of me opening this bug here. To help debugging the Wine part of the issue, I can * try patches that would be provided to me; * run executables on Wine and native Windows. Both laptops still have the Windows XP (1 Home, 1 Pro) that was on the HD when I bought the computers. I never installed the suite of Microsoft programs that would enable the Zoom slider. (I currently have nothing installed for compiling native Windows executables, be it mingw or MSVC + PSDK - but I could probably ask a friend to compile programs for me on MSVC 2008 + PSDK) To help debugging the other part of the issue, where should I write ? -- 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 17

[Bug 11559] New: Blood 2: The Chosen (version 1.0) - D3D crash
by wine-bugs＠winehq.org 09 May '08

09 May '08

http://bugs.winehq.org/show_bug.cgi?id=11559 Summary: Blood 2: The Chosen (version 1.0) - D3D crash Product: Wine Version: 0.9.55. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: liquid.acid(a)gmx.net Created an attachment (id=10724) --> (http://bugs.winehq.org/attachment.cgi?id=10724) Blood 2 version 1.0 in D3D mode Hi there, this is partially referring to my other bugreport about "Blood 2: The Chosen", but this time I didn't update to version number 2.1, but left the game unpatched (with NO copy protection fix applied). The game has version number 1.0 and crashes when running the engine in D3D mode. Software rendering works and also results in a smoother input in the menu, but graphics are really ugly. So, anyway I can manage to start the game in D3D mode, and the intros, etc. play. But this is really slow and the "client.exe" (main engine executable) consumes 99% CPU time. I can get to the menu of the game, but after selecting campaign and difficulty level the screen stops updating and I have a crashreport on the console where I started wine from. Going to attach the logs. I have made one log when trying the game with D3D mode, and two logs in software mode (both low quality and high quality). Not much console output difference there. Greets, Tobias -- 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 11339] New: serial.c:wait_on() sanity checks seem to be too strict
by wine-bugs＠winehq.org 09 May '08

09 May '08

http://bugs.winehq.org/show_bug.cgi?id=11339 Summary: serial.c:wait_on() sanity checks seem to be too strict Product: Wine Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: e_val(a)inbox.ru Created an attachment (id=10448) --> (http://bugs.winehq.org/attachment.cgi?id=10448) Trivial patch to fix the problem In its present state, wait_on() function implemented in ntdll/serial.c fails more often then it should. This means that in some cases serial events are not reported to the calling Windows program (even if in practice they could be) leading to application malfunction. The problem is in the sanity check: if ((status = get_irq_info(fd, &commio->irq_info)) || (status = get_modem_status(fd, &commio->mstat))) goto out_now; which bails out and silently returns 0 if low-level Unix kernel driver for serial device doesn't implement TIOCGICOUNT or TIOCMGET ioctl()s. This is, in fact, intended behavior if the calling program wants to monitor events like EV_BREAK, EV_ERR or EV_CTS and friends (otherwise, Wine will loop forever in wait_for_event()) but is useless and even harmful if the event in interest is EV_RXCHAR or EV_TXEMPTY. In latter case the check just prevents the program from working correctly. I've came across this bug when trying to make control software for AnyData CDMA modems (EasyWirelessNet 1.00.xx) working. In Linux, those devices use "option" driver, which lacks TIOCGICOUNT ioctl(). The trivial patch is attached. It's not against git clone of Wine so it is not meant for applying directly. -- 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 10627] New: child window position is not updated
by wine-bugs＠winehq.org 09 May '08

09 May '08

http://bugs.winehq.org/show_bug.cgi?id=10627 Summary: child window position is not updated Product: Wine Version: 0.9.50. Platform: PC OS/Version: other Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-user AssignedTo: wine-bugs(a)winehq.org ReportedBy: dmda(a)yandex.ru A popup window appears with content placed in wrong offset. See logs below I grabbed from an application: Popup window created: trace:win:WIN_CreateWindowEx (null) L"TEditPopup" ex=00000080 style=42040000 445,332 425x164 parent=0x10254 menu=0x0 inst=0x400000 params=0x0 trace:win:dump_window_styles style: WS_CHILD WS_CLIPCHILDREN WS_THICKFRAME trace:win:dump_window_styles exstyle: WS_EX_TOOLWINDOW trace:win:WIN_SetWindowLong 0x10270 -12 0 W trace:win:GetWindowRect hwnd 0x10270 (803,536)-(1228,700) Its content created: trace:win:WIN_CreateWindowEx (null) L"TVirtualStringTree" ex=00000000 style=46310000 0,0 423x143 parent=0x10270 menu=0x0 inst=0x400000 params=0x0 trace:win:dump_window_styles style: WS_CHILD WS_CLIPSIBLINGS WS_CLIPCHILDREN WS_VSCROLL WS_HSCROLL WS_TABSTOP trace:win:dump_window_styles exstyle: trace:win:WIN_SetWindowLong 0x10272 -12 0 W trace:win:WIN_SetWindowLong 0x10272 -4 2320726 A trace:win:alloc_winproc allocated 0xffff017b for A 0x2320726 (380/8192 used) trace:win:WIN_SetWindowLong 0x10272 -12 10272 A trace:win:GetWindowRect hwnd 0x10272 (804,537)-(1227,680) Position of the popup window is updated and SWP_SHOWWINDOW is requested: trace:win:SetWindowPos hwnd 0x10270, after 0xffffffff, 445,332 (425x164), flags 00000050 trace:win:dump_winpos_flags flags: SWP_NOACTIVATE SWP_SHOWWINDOW trace:win:GetWindowRect hwnd 0x10270 (445,332)-(870,496) Position of child window remained the same: trace:win:GetWindowRect hwnd 0x10272 (804,537)-(1227,680) full log is attached and four points listed above are marked in it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 13

[Bug 10431] New: GPSMapEdit: Unimplemented function gdiplus.dll. GdipGetImageDimension
by wine-bugs＠winehq.org 09 May '08

09 May '08

http://bugs.winehq.org/show_bug.cgi?id=10431 Summary: GPSMapEdit: Unimplemented function gdiplus.dll.GdipGetImageDimension Product: Wine Version: 0.9.49. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-gdiplus AssignedTo: wine-bugs(a)winehq.org ReportedBy: renaud(a)olgiati-in-paraguay.org When trying to load a .map file into GPSMapEdit, we no longer have an app crash as in bug 9963, but the app now freedzes while the following message appears in the Konsole from which I launched the app: wine: Call from 0x7ee39360 to unimplemented function gdiplus.dll.GdipGetImageDimension, aborting -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 7

[Bug 10046] New: Regression GPSMapedit under .47
by wine-bugs＠winehq.org 09 May '08

09 May '08

http://bugs.winehq.org/show_bug.cgi?id=10046 Summary: Regression GPSMapedit under .47 Product: Wine Version: 0.9.47. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-user AssignedTo: wine-bugs(a)winehq.org ReportedBy: renaud(a)olgiati-in-paraguay.org Created an attachment (id=8591) --> (http://bugs.winehq.org/attachment.cgi?id=8591) Debug output lifted from a Konsole. Under .47 editing the label of a map object causes GPSMapEdit to crash. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 15

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 May 2008