http://bugs.winehq.org/show_bug.cgi?id=18829
Summary: K-Meleon 1.5.x : Crash sometimes during browsing
Product: Wine
Version: 1.1.23
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jujuland.46(a)wanadoo.fr
--------------------------------------------------------------------------------
K-Meleon Version : 1.52
K-Meleon profile : in program folder (set during setup)
K-Meleon Extensions : none
K-Meleon kplugins : standard
Netscape plugins : none
Wine version : 1.1.23
Ubuntu : 8.10
kernel : 2.6.27-14-generic
Program Launch : ./K-M_152.sh
--------------------------------------------------------------------------------
shell (K-M_152.sh) used with a console to launch K-Meleon and to keep log
cd "/opt/Program Files/K-Meleon152"
./k-meleon.exe
--------------------------------------------------------------------------------
Crash sometimes during browsing:
---------------------------------------------------------------------------------------------
--
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=22549
Summary: Cannot open external links in help file.
Product: Wine
Version: 1.1.42
Platform: x86
URL: http://www.pmail.com/
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: turbolad995(a)hotmail.co.uk
Upon testing Pegasus Mail under Wine 1.1.42 I find you cannot open the links in
its help file. Clicking on the external links in the help file is supposed to
open your web browser and take you to the web page, but nothing happens when
you click on these links in the help file. This might be a bug in other
programs' help files?
--
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=15915
Summary: cinepak codec reportedly not installed, FourCC case
mismatch
Product: Wine
Version: 1.1.7
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvfw32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hoehle(a)users.sourceforge.net
CC: dmitry(a)codeweavers.com
The Alien Nations / Die Völker complains that the cinepak codec is not
installed.
The reason is a lower/upper case mismatch in a FourCC code.
Upper-case FourCC is being supplied, as the log reveals:
Call msvfw32.ICOpen(43444956,44495643,00000002) ret=00493baf
trace:msvideo:ICOpen (VIDC,CVID,0x00000002)
Call winmm.OpenDriver(0032fda8 L"VIDC.CVID", ...)
trace:driver:OpenDriver (L"VIDC.CVID", L"drivers32", ...);
But dlls/iccvid/iccvid.c implements the check
if (icinfo && icinfo->fccType != ICTYPE_VIDEO)
where ICTYPE_VIDEO refers to 'vidc', not VIDC.
The same check is in msvidc32/msvideo1.c and msrle32/msrle32.c
Probably a case-insensitive check is required? For instance,
msvfw32/msvideo_main.c:ICOpen() uses the case-insensitive helper
function compare_fourcc().
OTOH, after the case-insensitive check perhaps wine should fill in the
icopen.fccType and .fccHandler slots with the FourCC case it expects
(ICTYPE_VIDEO) rather than the argument it received? It seems reasonable to
commit to a known character case early on in the code and use that
consistently.
What is The Right Thing (TRT), i.e. what to store in fccType?
In any case, a case fix lets "Die Völker" work past this issue (and crash
later in ddraw, but that's another issue).
--
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=18325
Summary: Timed events bug in Call of Cthulhu
Product: Wine
Version: 1.1.20
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: monolitonegro(a)gmail.com
There's a bug in the game Call of Cthulhu: Dark Corners of Earth that make some
timed events executate too early in the game, making the game near unplayable,
or downright unplayable.
The earliest noticiable example is the beginning of the Chapter 2:"Attack of
the fishmen". At the beginning of this chapter, the player must avoid an angry
mob of citizens running from room to room before the enemies manage to break in
the bolted doors. While in the Windows XP the game allows plenty of time for
the player to think and act, the linux with wine allows barely enough, making
the game nearly unplayable.
Another point where this bug is noticeable is at the chapter 5, Marsh Refinery.
At midway chapter, the player must outrun a shoggot while closing doors behind
him. While this is perfectly possible in the Windows XP, it is absolutely
impossible in the linux.
Tested with: wine version 1.1.20 binaries from official repository under
GNU/Linux Ubuntu Hardy 8.04 and Windows XP SP2.
Aplication: Call of Cthulhu: Dark Corners of Earth version 1.0
Command line: wine "C:\Arquivos de programas\Bethesda Softworks\ Call of
Cthulhu DCoTE\Engine\CoCMainWin32.exe"
How to reproduce: In a dual boot machine with both Windows XP SP2 and GNU/Linux
Hardy 8.04, install the game twice, one time in each OS. Play the game up to
the beginning of the chapter 2 in the easiest dificulty(Scout Boy). At the
beginning of chapter 2, take a wristwatch, measure the time it takes for the
enemies to break in in each of the four rooms. Compare the results from both
OS.
If that's not enough, play up until midway chapter 5(if you can), compare the
time it takes for the shoggot to outrun the player in both OS.
This video shows what the player is supposed to do in chapter 5. The event
begins at 7:10 onwards:
http://www.youtube.com/watch?v=qBFR1_qnrog
--
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=19926
Summary: Lock On: Modern Air Combat crashes after 2 seconds of
loading
Product: Wine
Version: 1.1.27
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nawitus(a)gmail.com
Created an attachment (id=23405)
--> (http://bugs.winehq.org/attachment.cgi?id=23405)
A terminal log of the crash
While attempting to start Lock On : Modern Air Combat 1.0 (the retail version),
I can see the window for a couple of seconds while something is being read from
the cd, and then the game shuts down (crashes in other words). See the log for
more information.
I've used 2 native DLL's (oleaut32.dll and msvcirt.dll) as specified in winehq,
otherwise the game doesn't start at all. I tried both Win98 and WinXP modes and
got identical results.
--
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=20148
Summary: d3d8: visual tests timeout with pbuffer enabled
Product: Wine
Version: 1.1.29
Platform: PC-x86-64
URL: http://test.winehq.org/data/caf66f0fe28da8964b5f84be68
2c527559fb9e52/wine_ae-ub904-pbuffer/d3d8:visual.htmld
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
visual.c:711: Test failed: Offscreen failed: Got color 0x00ff0000, expected
0x00ffffff.
visual.c:714: Test failed: Offscreen failed: Got color 0x00ff0000, expected
0x00ff00ff.
visual.c:887: Test failed: DSTALPHA on texture returned color 007f0080,
expected 0x000000ff
test failed: timed out
every time on my machine.
--
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=20147
Summary: riched20:editor test fails when pbuffer is enabled
Product: Wine
Version: 1.1.29
Platform: PC-x86-64
URL: http://test.winehq.org/data/bb4050d79280dc83e4f3159eb1
21cb88d84721e9/wine_ae-ub904-pbuffer/riched20:editor.h
tml
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
editor.c:5976: Test failed: Cursor is at 0 instead of 8
Doesn't occur with backbuffer, and very seldomly with fbo. With pbuffer, nearly
every time.
--
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=14094
Summary: Guild Wars crashes after patch screen with pbuffer
Product: Wine
Version: 1.0.0
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nicodarious(a)gmail.com
OK, so I am very new to this, but I am really hoping that I might be able to
throw in a little help.
I have been playing around with regedit and changing little things here and
there, each time testing Guild Wars out after running wineprefixcreate.
One things that I have noticed is that Guild Wars WILL run (at about 5 - 25
FPS) with the OffScreenRenderingMode set to fb0, but will crash out if set to
pbuffer. Is there any reason for this?
Also, I ran Gw.exe from prompt to get output for the reasoning for the crash,
and this is what I get (the last few lines that is):
err:d3d:getColorBits Unsupported format: WINED3DFMT_R32F
err:d3d:IWineD3DImpl_IsPixelFormatCompatibleWithRenderFmt Unable to check
compatibility for Format=WINED3DFMT_R32F
fixme:d3d:IWineD3DResourceImpl_SetPriority (0x352a0b0) : stub
fixme:d3d:IWineD3DResourceImpl_SetPriority (0x352a5a8) : stub
fixme:d3d:IWineD3DResourceImpl_SetPriority (0x352abc0) : stub
fixme:d3d:FindContext The PBuffr context is only supported for one thread for
now!
err:d3d:ActivateContext Failed to activate the new context
err:seh:raise_exception Exception frame is not in stack limits => unable to
dispatch exception.
I also have my registry settings exported for anyone wanting to browse through
them. If you have any info or questions, please let me know and I will do my
best to gather the info for you.
--
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=21273
Summary: python's test_poplib test fails
Product: Wine
Version: 1.1.35
Platform: x86
URL: http://www.python.org
OS/Version: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Created an attachment (id=25580)
--> (http://bugs.winehq.org/attachment.cgi?id=25580)
test output
Install python and run:
wine 'c:\Python31\python.exe' -m test.test_poplib
testTimeoutDefault (__main__.TestTimeouts) ... ERROR
testTimeoutNone (__main__.TestTimeouts) ... ok
testTimeoutValue (__main__.TestTimeouts) ... ERROR
Full output attached.
--
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.