http://bugs.winehq.org/show_bug.cgi?id=9742
Summary: EngineSite segfaults (Segmentation fault)
Product: Wine
Version: unspecified
Platform: PC
URL: http://luckasoft.com/download/perle_le.exe
OS/Version: Linux
Status: UNCONFIRMED
Keywords: regression
Severity: normal
Priority: P2
Component: wine-gdi-(printing)
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xerox_xerox2000(a)yahoo.co.uk
A user reported trouble with this app in this thread:
http://groups.google.nl/group/comp.emulators.ms-windows.wine/browse_thread/…
I tried it , and it just segfaults after the splash screen. However , in
wine-0.9.2 it gets nicely beyond the spash screen, and seems to start fine.
I'll put some more info into this bug later on
--
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=14212
Summary: Winuae freeze as soon as you hit a key after starting
the emulation.
Product: Wine
Version: 1.1.0
Platform: PC
URL: http://www.winuae.net/
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lorefice2(a)libero.it
The emulator works quite well,but when hitting a key, the emulation hard
freezes (you need ctrl-c to exit), and fps goes to 0.
Tried on 32bit and 64bit.
--
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=14932
Summary: Spore Prototype CityMaze: Rendering issue
Product: Wine
Version: CVS/GIT
Platform: Other
URL: http://www.spore.com/static/war/images/community/prototy
pes/CityMaze.zip
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andrewfenn(a)gmail.com
There is some kind of rendering issue with the CityMaze prototype where the
screen will continuously flicker and shake vertically.
--
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=12689
Summary: Input messages lingering in server slowing down wine
Product: Wine
Version: CVS/GIT
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alexd4(a)inbox.lv
Created an attachment (id=12347)
--> (http://bugs.winehq.org/attachment.cgi?id=12347)
testcase for problem
Attached testcase illustrates the problem. The problem was originally found in
a fan-developed Forsaken mod. I couldn't get feedback on this on wine-devel, so
I'm opening a bug for this. Close if it's not a bug or is non-fixable.
How to reproduce: hold a key and move mouse over the window, preferably also
clicking mouse buttons, main loop latency steadily increases from 10 to 50 (and
even 100) in a short time. In a game this means going from 100 fps to 20 or 10
just because of input messages. Has to be noted that in the actual game the
rate of slowdown seemed at least 2-3 times faster when just holding one key and
moving mouse, for reasons I don't know, but the testcase still should enough to
show the problem.
What the testcase is doing is bad practice, it's basically refusing to process
certain types of messages, and PeekMessage just once during a loop is probably
bad as well, but that's what the game was originally doing in its main game
loop. There are several concerns about it:
1) No slowdown happens on Windows, either in game or in this testcase. No
matter how much I move the mouse holding key and clicking madly, it shows same
stable 15-16 ticks latency in the testcase. I don't know what it does, but
somehow it handles this situation better than Wine.
2) Can this (broken) way of doing things be exposing some inefficiency in
message handling, maybe something that could use optimization? I tried to put
debug hacks into queue_hardware_message(), it seems that when slowdown is
already VERY bad in Forsaken (10fps), message queue in wine server has about
400 or maybe 600 messages. Is that kind of processing overhead per message
inevitable? (This is happening on AMD Athlon(tm) 3200+). Perhaps somebody who
knows that part of code well may be interested in looking into performance
issues in this case. Because, if 400-600 messages in the queue slow down the
application to a crawl, then who knows, perhaps it decreases performance of
more well-behaved but input-intensive apps as well, just less drastically
(holding one or several keys to move, all the while aiming with mouse and
abusing mouse buttons is a common thing in games, so there can be quite a few
input messages flooding the server).
--
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=13752
Summary: Kega Fusion: Direct 3D output does not fill window in
windowed mode
Product: Wine
Version: 1.0-rc4
Platform: Other
URL: http://www.eidolons-inn.net/tiki-index.php?page=Kega
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tgheretford(a)fast4.net
When the program first starts in windowed mode, the graphics in the application
window are shifted down to the bottom and to the right. On the desktop, the
further to the bottom and the right you move the Kega Fusion application
window, the further down and right the graphics move in the window.
Fullscreen mode is not affected by this bug.
Currently using NVidia 169.12 drivers on a Zotac 512MB AMP! Edition card but I
do know that the same problem occurred on my old computer using a Geforce 6200
card.
Below will be two picture attachments of my desktop showing the bug when I move
the application window around my desktop.
--
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=12520
Summary: Yoda Stories main window is too small
Product: Wine
Version: unspecified
Platform: PC
URL: ftp://ftp.lucasarts.com/demos/pc/yodademo.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: megazzt(a)gmail.com
When running Yoda Stories (full game or demo) the main window is too small (it
seems to be minimum size for a window) and cannot be resized. The game is
unplayable since the window is so small as to have no client area.
Get the demo from ftp://ftp.lucasarts.com/demos/pc/yodademo.exe for testing.
You can extract it with unzip if you don't want to go through the hassle of
installing it.
--
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=9291
Summary: iexplore http://pack.google.com crashes
Product: Wine
Version: CVS
Platform: Other
OS/Version: other
Status: NEW
Keywords: download
Severity: enhancement
Priority: P2
Component: wine-shdocvw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dank(a)kegel.com
Wine's built-in iexplore crashes on http://pack.google.com.
Unhandled exception: page fault on read access to 0x0000005c in 32-bit code
(0x7c7bd7a8).
Backtrace:
=>1 0x7c7bd7a8 nsChannel_AsyncOpen+0x4e8(iface=0x1063958, aListener=0x1063998,
aContext=0x0) [/home/dank/wine-git/dlls/mshtml/nsio.c:107] in mshtml
0x7c7bd7a8 nsChannel_AsyncOpen+0x4e8
[/home/dank/wine-git/dlls/mshtml/nsio.c:107] in mshtml: movl
0x5c(%esi),%edi
107 while(!container_iter->doc)
I peeked at nsio.c, and it does look vulnerable to container_iter going
unexpectedly null during that loop, but a real fix wasn't immediately obvious.
--
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=13085
Summary: TH06: No FPS limit in fullscreen mode
Product: Wine
Version: 0.9.61.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P4
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: dottomi(a)gmail.com
The game seems to not limit FPS amount in fullscreen mode. It speeds up to >200
FPS instead of not going above 60.
--
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=14377
Summary: Crusader Kings: Instant crash when using bride ledger
(and some other ledgers)
Product: Wine
Version: 1.0-rc5
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: daniel(a)jackson.kz
CC: daniel(a)jackson.kz
Created an attachment (id=14674)
--> (http://bugs.winehq.org/attachment.cgi?id=14674)
Printout from the terminal from starting the game, loading a game, navigating
to the bride ledger and the following crash
Steps to reproduce:
1. Open Crusaders.exe
2. Load a game (or start one)
3. Go to the ledger and find the "Bride ledger" where you can locate possible
brides.
Result:
Crash to desktop after a few seconds of thought, with an error message
displayed but blanked out due to graphical glitch.
--
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.