http://bugs.winehq.org/show_bug.cgi?id=8427
Summary: CPUZ fails to load
Product: Wine
Version: CVS
Platform: PC-x86-64
URL: http://www.cpuid.com/cpuz.php
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: greg87(a)online.de
Msgbox pops up:
An error occured when opening the driver. CPU-Z will launch but not all
information will be available
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=8276
------- Additional Comments From winter.blood(a)gmail.com 2007-18-05 03:23 -------
Confirmed. This is really annoying, as i take screenshots rather often, and i
have to clear out one every time i take one. :/
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=8426
Summary: Darkstone Demo: Main menu and mouse cursor invisible
Product: Wine
Version: 0.9.37.
Platform: PC-x86-64
URL: http://www.clubic.com/lancer-le-telechargement-1925-0-
darkstone.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P4
Component: wine-directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hightower(a)tregt.net
In Darkstone demo(behaves the same as the full version) the main menu and mouse
cursor(the game one, as the double cursor bug is still there I have the X one)
is missinng.
I did a regression test on it, and found 0.9.27 to be working and the commit
c83562af697e735fe6d8e96aa8c033759a124cd2 to be the cause.
Although the way it was working was with black borders around text and cursor,
but atleast one could see something.
(the link is to the download of the french version, 3dgamers site was way to
slow for my liking)
(the game crashes bad when trying to start the actual game, but that's another
issue)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5774
------- Additional Comments From damjan.jov(a)gmail.com 2007-18-05 01:33 -------
Created an attachment (id=6341)
--> (http://bugs.winehq.org/attachment.cgi?id=6341&action=view)
send a UDP datagram with a bad checksum
And the second part of the test is sending a bad UDP datagram.
Compile this code and run it on a different computer, as root, specifying the
IP address of the first computer as the command-line parameter.
Wireshark shows a UDP datagram coming in with a bad checksum.
The first computer will print out:
poll() reported readability but recvfrom got EAGAIN
Theory proven.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5774
------- Additional Comments From damjan.jov(a)gmail.com 2007-18-05 01:29 -------
Created an attachment (id=6340)
--> (http://bugs.winehq.org/attachment.cgi?id=6340&action=view)
poll/recvfrom test
I was asked by Alexandre to present some evidence for the correctness of this
patch, so this seems like as good a place as any to post what I found.
The theory being tested is that when you are polling a non-blocking datagram
socket, and a datagram with a bad checksum arrives, the poll will wake up and
report that the socket is readable, but reading will fail with EAGAIN.
This code does the polling and receiving part of the test. Compile this and run
it on one computer.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7674
------- Additional Comments From saulius.krasuckas(a)elst.vtu.lt 2007-18-05 01:10 -------
Last lines in the log are:
trace:d3d:IWineD3DSwapChainImpl_Present returning
trace:d3d:IWineD3DSwapChainImpl_Release (0x1c98d8) : ReleaseRef to 1
trace:d3d:IWineD3DDeviceImpl_GetViewport (0x17a4c0)
trace:d3d:IWineD3DDeviceImpl_SetViewport (0x17a4c0)
trace:d3d:IWineD3DDeviceImpl_SetViewport (0x17a4c0) : x=0, y=0, wid=640,
hei=480, minz=0.100000, maxz=1.000000
trace:d3d:IWineD3DDeviceImpl_Clear (0x17a4c0) Count (0), pRects ((nil)), Flags
(3), Z (1.000000), Stencil (0)
wine: Unhandled page fault on read access to 0x000002a0 at address 0x7eaa12a6
(thread 001c), starting debugger...
wine: Unhandled exception 0x80003007 at address 0x7ee5f610 (thread 001e),
starting debugger...
Jeremie, there was no backtrace (and other info from debugger) below those
lines? I guess a backtrace would help a lot.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.