http://bugs.winehq.org/show_bug.cgi?id=12831
Summary: after start any win programm wineserver got stable 34%
cpu usage until they will be killed
Product: Wine
Version: 0.9.60
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P1
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: neos(a)blizzz.ru
after start any windows programm, wineserver use ~34% cpu permanently. helps
only kill process. Same for me and on 59 wine, but not 58.
AMD64
gcc-4.1.2, glibc-2.6.1-r0, 2.6.23-gentoo-r8 x86_64
--
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.
http://bugs.winehq.org/show_bug.cgi?id=12680
Summary: jack driver produces buffer underruns (regression)
Product: Wine
Version: 0.9.59.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: webmaster(a)tonstube.de
This is a regression introduced by the patch for winejack.drv by Andrew Talbot.
After this patch, wine produces buffer underruns with the following error
output:
err:wave:JACK_callback_wwo buffer underrun of 1024 frames
(where '1024' my differ from system to system depending on the jack
configuration).
When winejack.drv is substituted by the one from 0.9.58 everything is fine.
To reproduce, just use the jack driver in winecfg.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=12429
Summary: Gamepad buttons not working in PES 6
(ProEvolutionSoccer)
Product: Wine
Version: 0.9.48.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: agusmba(a)terra.es
I am trying to use a Guillemot gamepad with PES6 but the buttons are not
recognized.
In my kubuntu (8.04beta) system settings I can see my pad, callibrate the
joysticks and see the buttons are recognized, but not inside wine (only the
joysticks are recognized).
I have tried different combinations for the DirectInput entry in the registry
but either I have not stumbled upon the correct one or there is another issue
preventing the working of the buttons.
I have tried the joystick and the evdev approach, none work for the buttons.
I tried wine-test and according to it the gamepad is ok (buttons work)
I also tried with a different generic usb gamepad and still no buttons were
recognized in the game.
See thread
http://forum.winehq.org/viewtopic.php?t=362&postdays=0&postorder=asc&start=0
for a more detailed walkthrough of the problem
I'll upload some logs with "WINEDEBUG=+dinput" later.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=12373
Summary: [REGRESSSION 0.9.59] Nothing is rendered in Crimsonland
- blank black screen
Product: Wine
Version: unspecified
Platform: PC
URL: http://arcade.reflexive.com/downloadgame.aspx?AID=9&CID=
22028
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: contact(a)i-nz.net
Crimsonland was on the platinum list with 0.9.58, but now with 0.9.59 there is
a regression and nothing is rendered at all - not in windowed more, not in full
screen. Just a black blank screen.
I am running WINE 0.9.59 on openSUSE 10.3 on a machine with an ATi Mobility
Radeon X1600 with the proprietary Catalyst 8.3 gfx driver from ATi
There is no 0.9.59 version to set in bugzilla, so please one added set it for
this bug report.
--
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.
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.
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.
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.
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.
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.
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.