http://bugs.winehq.org/show_bug.cgi?id=9468
Summary: Mortal Kombat Trilogy crashes
Product: Wine
Version: 0.9.44.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: rchayster(a)gmail.com
Created an attachment (id=7810)
--> (http://bugs.winehq.org/attachment.cgi?id=7810)
output
I have Mortal Kombat Trilogy, patched to version 1.1. The game crashes on
startup. When I run $ wine MKTRILW.EXE
The wine outputs:
err:wgl:X11DRV_wglGetProcAddress (wglMakeContextCurrentARB) - not found
err:wgl:X11DRV_wglGetProcAddress (wglGetCurrentReadDCARB) - not found
fixme:win:EnumDisplayDevicesW ((null),0,0x33f688,0x00000000), stub!
fixme:d3d:IWineD3DDeviceImpl_GetAvailableTextureMem (0x125ce0) : stub,
simulating 64MB for now, returning 64MB left
And just stucks there. When I press ctrl+c wine outputs this and quits:
The program encountered a problem at address 00432252 and cannot continue
I'm putting the WINEDEBUG=+all debug log here as an attachment. It's the last
1000 lines.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=20012
Summary: Implement HalGetBusDataByOffset for the
PCIConfiguration BusDataType
Product: Wine
Version: 1.1.29
Platform: PC
URL: http://rh-software.com/
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ray(a)pobox.co.uk
Created an attachment (id=23551)
--> (http://bugs.winehq.org/attachment.cgi?id=23551)
Scren capture showing example code working
With the fix http://bugs.winehq.org/show_bug.cgi?id=19966 SIV
(http://rh-software.com/) no longer crashes when run under Wine, however none
of the PCI Bus reporting actually works. As an experiment I wrote some code to
read the PCI confutation data from "/sys/bus/pci/devices/0000:bb:dd.f/config"
where bb:dd:f are the Bus, Device and Function numbers (the Device and Function
are bits 7...3 and 2...0 of the slot number. The attached screen shot you can
see I was able to read the data what HalGetBusDataByOffset() should return. I
actually did this using the Windows API functions using the following code:
if( ( fhl = CreateFile( file_name,
GENERIC_READ,
FILE_SHARE_READ | FILE_SHARE_WRITE,
NULL,
OPEN_EXISTING,
0,
NULL ) ) != INVALID_HANDLE_VALUE )
{
if( ReadFile( fhl, data, sizeof( data ) &len, NULL ) )
{
...
}
CloseHandle( fhl );
but I would expect the Unix/Linux Native API should be used were this to be
implemented. I am concerned that different Unix/Linux systems may have
different device names, but looking at the lspci source there seems to be a pci
library to address this. I could try and work-a-round this within SIV, but as
SIV would probably not be able to use the Unix/Linux pci library that solution
would be less portable than implementing a solution within
HalGetBusDataByOffset() within Wine. For systems where this data could not be
returned then the current return of 0 (PCI Bus does not exist) would be made.
Note that in the case of the Bus existing and the slot being empty a return of
2 is expected.
--
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=17618
Summary: winecfg does not set drive type correctly for Local Hard
Disk choice
Product: Wine
Version: 1.1.16
Platform: PC-x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lordhavoc(a)ghdigital.com
The Drives panel in winecfg has a Type: dropdown which allows Auto-detect,
Local Hard Disk, Network Share, Floppy Disk, or CD-ROM to be chosen for each
drive.
Each of these sets a registry value, except for Auto-detect and Local Hard Disk
which simply remove the registry value for the respective drive.
Local Hard Disk should set the registry value for the drive to "hd".
--
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=20746
Summary: Bug with bibleworkshop 4.4 loaded with wine on Ubuntu
Karmic
Product: Wine
Version: unspecified
Platform: PC
URL: http://www.bibleworkshop.net
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lgimelfarb(a)gmx.ch
Created an attachment (id=24815)
--> (http://bugs.winehq.org/attachment.cgi?id=24815)
Print screen of the failure
Msg after closing program : BClient.dll must close and wenn I open the
programme again, the registration of the product key have to be enter again.
--
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=21563
Summary: Risiko! Digital does not start
Product: Wine
Version: 1.1.37
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lucak3(a)gmail.com
Created an attachment (id=25985)
--> (http://bugs.winehq.org/attachment.cgi?id=25985)
Rsisiko! Digital console log
Using wine-1.1.37-230-g3ed5df1 and a clean prefix
I tried to launch the game directly from its directory, but it does not change
anything: i issue the command to load the game and almost instantly closes.
I did not use winetricks.
It seemed to me that installation went correctly, but i will attach the setup
log in a second.
--
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=20335
Summary: Uninitialised memory reference in
X11DRV_DIB_SetImageBits()
Product: Wine
Version: 1.1.31
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: winex11.drv
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
I think this is one of the first valgrind warnings
I ever ran into in wine, and it's still here.
Nowadays Wine gives better warnings, so it's a little
easier to see where these are coming from.
Running chromium's base_unittests.exe (and probably
lots of other apps) in valgrind yields this warning:
Conditional jump or move depends on uninitialised value(s)
at XcursorImageHash (xlib.c:294)
by XcursorNoticePutBitmap (xlib.c:365)
by _XNoticePutBitmap (CrGlCur.c:202)
by XPutImage (PutImage.c:1042)
by X11DRV_DIB_SetImageBits (dib.c:3670)
by X11DRV_SetDIBits (dib.c:4040)
by SetDIBits (dib.c:361)
...
Uninitialised value was created by a client request
at RtlAllocateHeap (heap.c:187)
by X11DRV_DIB_SetImageBits (dib.c:3543)
by X11DRV_SetDIBits (dib.c:4040)
by SetDIBits (dib.c:361)
...
Presumably adding HEAP_ZERO_MEMORY to the allocation
at dib.c:3543 would do the job, but maybe there's a
smarter way.
--
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=20508
Summary: F/A-18 PSF Mouse control stops working in 3d view
Product: Wine
Version: 1.1.29
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bgoodwin91006(a)yahoo.com
The mouse works correctly in all menus. On entering the 3D cockpit view, it
works correctly for a few seconds; long enough to take-off. In flight, the
control becomes less and less responsive. The plane noses down and crashes.
Using a joystick instead of the mouse works correctly but I prefer mouse
control because it's smoother and there's no convenient place to put the
joystick with my small desk and chair. The mouse control works correctly under
WindowsXP.
The problem has been the same for a long time (several years.) and through a
steady migration from Fedora 3 to my current Fedora 11.
--
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=20807
Summary: SolidWorks 2008 can't render parts
Product: Wine
Version: 1.1.33
Platform: PC
OS/Version: Mac OS X 10.6
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: opengl
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cdavis(a)mines.edu
Created an attachment (id=24921)
--> (http://bugs.winehq.org/attachment.cgi?id=24921)
Wine 1.1.32-641-ga7bfd6d Log +wgl on Mac OS X
When you create a part, SolidWorks attempts to create a bitmap GL context to do
offscreen rendering. The call to SetPixelFormat() on the bitmap DC fails,
however, because the depth of the pixmap (32) doesn't match the depth of the
visual that winex11 chose (24). (You can add a trace to
create_bitmap_glxpixmap() to see this for yourself.) SolidWorks, however, does
not check the result of SetPixelFormat(), expecting it to succeed, so it goes
ahead and tries to create a GL context. This fails because no pixel format is
set in the DC. As a result, no rendering of parts is done.
I've attached a log showing what happens. There's a second issue that is
demonstrated by that log, so I'm going to file another bug shortly.
I think this is somehow related to Roderick Colenbrander's Xrender patches,
given that we're dealing with a 32-bit pixmap (which wasn't possible until
Xrender support was added).
--
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=20808
Summary: SolidWorks 2008 displays a black screen
Product: Wine
Version: 1.1.33
Platform: PC
OS/Version: Mac OS X 10.6
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: opengl
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cdavis(a)mines.edu
Created an attachment (id=24922)
--> (http://bugs.winehq.org/attachment.cgi?id=24922)
Wine 1.1.32-641-ga7bfd6d Log +wgl on Mac OS X
Like I said in bug 20807, there's a second issue with SolidWorks' rendering. If
you get past the issue in bug 20807, you see only a black screen when it tries
to render parts. I will once again attach the log from bug 20807.
>From reading the log, it seems like SolidWorks is looking for a particular
pixel format. First it tries the pixel format it got back trying to create a
bitmap context earlier. Then it enumerates every pixel format supported by the
driver. Failing that, it tries to create a bitmap context anyway, but fails
because once again no pixel format is set in the DC.
--
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=19871
Summary: Cusom CWnd component redraw flicker
Product: Wine
Version: 1.1.28
Platform: PC
URL: http://www.jtagtest.com/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: martin(a)hinner.info
See bug: http://bugs.winehq.org/show_bug.cgi?id=17394
Window repainting is flickering under Wine. Native Win32 works fine (or at
least I cannot see anything). Can provide "closed" source code of the component
to person who will be dealing with this stuff.
--
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.