http://bugs.winehq.org/show_bug.cgi?id=32618
Bug #: 32618
Summary: Atlantica Online partially hangs when rotating the
view with the mouse.
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: arek75(a)gmail.com
Classification: Unclassified
Created attachment 43044
--> http://bugs.winehq.org/attachment.cgi?id=43044
Bisect log
Starting with Wine 1.5.18, Atlantica Online is no longer playable due to a bug
where if you attempt to rotate the camera with the mouse (right-click and
drag), Atlantica's graphics lock up and the game seems to lose the mouse. You
can get the game to respond again by pressing alt on the keyboard, but you
still can't rotate the camera (or rather not much, it'll move a tiny bit each
time before locking up).
I went ahead and bisected this, and also ran into a problem where Atlantica
never got control of the mouse/keyboard and had to be closed with alt-f4. In
these cases I used 'git bisect skip' to continue. Git finally came up with 18
possible "bad commits". Looking at them in gitk, the following commits are of
note (the first skipped commit and the first known bad commit):
841214ddb4d4dc620e6b51dfe6655b585d423edc - user32: Don't check for driver
events before normal messages in PeekMessage.
a0f039a6049641cc2be8fa32f2afa3c3f394a99b - user32: Fix the wait event mask in
PeekMessage.
The first of these commits caused Atlantica to not respond much to
mouse/keyboard events (you could get a partial response from the mouse if you
could get it over a button, but you can't see the pointer), and while the
second patch fixed that, attempting to rotate the camera using the mouse causes
Atlantica's input/graphics to partially freeze as noted above.
I've attached the bisect log so that you can have a look at it if you need to.
--James
--
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=21369
Summary: Tab bar isn't fully visible in HTML-Kit; must be
scrolled
Product: Wine
Version: 1.1.36
Platform: x86-64
URL: http://www.chami.com/html-kit/download/
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: RandomAccountName(a)mail.com
Created an attachment (id=25731)
--> (http://bugs.winehq.org/attachment.cgi?id=25731)
Terminal output
In HTML-Kit build 292, one of the tab bars (the one below the current working
file) isn't displayed as expected in Wine. In Windows, the entire tab bar is
visible, but in Wine, part of it is cut off, with scroll arrows present to
bring the rest into view. Native comctl32 installed by winetricks fixes the
issue.
Interestingly, increasing Wine's DPI to 120 allows all the tabs to display at
once, though rendering is still a bit different from Windows.
Terminal output is from opening the program and entering "create a new file"
mode (which is when the tabs first become visible).
--
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=29384
Bug #: 29384
Summary: Voobly fails to launch Age of Empires II multiplayer
game (DirectPlay)
Product: Wine
Version: 1.3.35
Platform: x86-64
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lapommegolden(a)gmail.com
Classification: Unclassified
Instead of entering AOE II's brown multiplayer game screen, game will now be
automatically aborted & cancelled unrated instead.
--
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=33239
Bug #: 33239
Summary: VisualBasic arrays of User Defined Type (UDTs) with
strings
Product: Wine
Version: unspecified
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mod(a)navsoft.com
Classification: Unclassified
Created attachment 43964
--> http://bugs.winehq.org/attachment.cgi?id=43964
Uses a simple program to test where the crash occurs
I use arrays of UDTs which work under MS Windows. (Any version post Win 2000
except ME.) The program also works happily on a Mac using a Parallels virtual
machine.
These fail under WINE if one or more of the fields is a string. The "TYPE"
order makes no difference.
UDTs which contain only numbers are not affected.
Failure occurs on any attempt to "ReDim" or "Erase" the array. The problem does
not occur when the strings are fixed length or for flat UDTs containing strings
of undeclared length. Prior to a crash, the content of the UDTs can be read and
written to.
Trying to write a simple program produces strange results. I tried initially on
an old PC and found that it would crash simply by redimming the arrays but when
installed under Parallels, it will handle simple arrays and only crashes as I
start to get more adventurous; i.e. using a UDT type declared in a DLL but
otherwise identical.
My main program can be downloaded at http://navsoft.com/AstroNav_Setup.exe. It
makes no claims to being compatible with WINE but there are references to the
problem area elsewhere in this forum by Users who would like to run it under
WINE.
AstroNav uses UDTs extensively. The problem is the Almanac screen where multi
dimension UDTs are widely used. With AstroNav, simply declaring and then
destroying the arrays will cause a crash. [There is also a problem with WINE's
treatment of SetGraphicsMode which I have not yet pinned down but will
hopefully circumvent very shortly. (The SetGraphicsMode API does not work quite
as Microsoft claim so removing it, is probably desirable.)]
The attached backtrace was caused by the following code. The crash occurs only
for Command4_Click() and only on the third press. (Rapid pressing will cause a
"The array is temporarily locked" error/ crash.)
FORM CODE
==========
Private Type My_UDT
n1 As Long
s1 As String
s2 As String
End Type
Private mUDT() As My_UDT
Private DLL_UDT() As Main_Almanac_Columns
Private Sub Command1_Click() ' NO PROBLEM NOW BUT SIMILAR CODE CAUSED A
Dim i As Long ' CRASH ON AN OLDER PC
ReDim mUDT(99)
For i = 0 To 99
mUDT(i).s1 = "Some String"
mUDT(i).s2 = "Some String"
Next i
ReDim mUDT(99)
End Sub
Private Sub Command2_Click() ' SAME AS ABOVE BUT USING A GLOBAL UDT
Dim i As Long ' = A BIT MORE ADVENTUROUS
ReDim gUDT(99)
For i = 0 To 99
gUDT(i).s1 = "Some String"
gUDT(i).s2 = "Some String"
Next i
ReDim gUDT(99)
End Sub
Private Sub Command3_Click() ' MORE ADVENTUROUS; PASSING DATA USING
Compile_Data ' Public Property Get
gUDT = My_Module_UDT
End Sub
Private Sub Command4_Click() ' CRASHES ON THE THIRD CLICK ON MY MAIN
Alt_Compile_Data ' MACHINE
DLL_UDT = My_DLL_UDT
End Sub
MODULE CODE
===========
Private DLL_UDT() As Main_Almanac_Columns
Type Module_UDT
n1 As Long
s1 As String
s2 As String
End Type
Private mUDT() As Module_UDT
Public gUDT() As Module_UDT
'\\ THE MODULE LEVEL TEST
Sub Compile_Data()
Dim i As Long
ReDim mUDT(71)
For i = 0 To 71
With mUDT(i)
.n1 = i
.s1 = i
.s2 = i
End With
Next i
End Sub
Public Property Get My_Module_UDT() As Module_UDT()
My_Module_UDT = mUDT
End Property
'\\ USING THE IDENTICAL TYPE DECLARED IN A MODULE
Sub Alt_Compile_Data()
Dim i As Long
ReDim DLL_UDT(71)
For i = 0 To 71
With DLL_UDT(i)
.Gap = i
.sGHA = i
.sDec = i
End With
Next i
End Sub
Public Property Get My_DLL_UDT() As Main_Almanac_Columns()
My_DLL_UDT = DLL_UDT
End Property
--
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.
https://bugs.winehq.org/show_bug.cgi?id=38892
Bug ID: 38892
Summary: Please support more architectures.
Product: Wine
Version: unspecified
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: loader
Assignee: wine-bugs(a)winehq.org
Reporter: ytrezq(a)sdf-eu.org
Distribution: ---
Hello,
It might sound useless but the WINAPI supported Itanium PPC MIPSR4000 and dec
alpha in the past.
While windows doesn't provide updates for those platforms, compiling programs
written for the WINAPI to those arch is the best way to get decent speeds (not
to add the need of support for ARC firmware which prevent running them on
recent ppc).
Of course this is not for emulating instructions sets but for running windows
programs natively on those platforms.
For testing on x86 an ARC bios for MIPS which can work on qemu is documented
here http://gunkies.org/wiki/Installing_Windows_NT_4.0_on_Qemu(MIPS)
Visual C++ RISC editions for those platforms are available here
http://bingeflying.com/3.2/
--
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=34708
Bug #: 34708
Summary: Silent Hill 4: The Room don't run in terminal.
Product: Wine
Version: 1.7.4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sov.info(a)mail.ru
Classification: Unclassified
Created attachment 46270
--> http://bugs.winehq.org/attachment.cgi?id=46270
01 terminal output
This game don't start via terminal. BUT!
When i just starting it by clicking on the .desktop file, it runs! This
behavior is pretty interesting. Of cource, this game crushes even if start by
clicking on desktop label. But if we want to see what stubs happens in game, we
should before fix terminal behavior.
--
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=23434
Summary: wine hangs & jumps up to 100% processor load
Product: Wine
Version: 1.2-rc5
Platform: x86
URL: http://www.velumng.com
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: axel.braun(a)gmx.de
Running wine-1.1.48_1.2rc5-1.1, i downloaded the demo from velumng.com, a race
management software.
So far it works well, I created a race, two participants, entered start and end
time, but when I come to the result list creation, the load goes up to 100%,
and caused a hang of the X-session once.
At this point it seems to load a HTML-page that was dynamically generated. wine
did not submit any error message when started from console.
Let me know what I can do to come to a more verbose error output.
--
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=33982
Bug #: 33982
Summary: Steam windows can be resized to 1x1 despite minimum
size
Product: Wine
Version: 1.6-rc2
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: adys.wh(a)gmail.com
Classification: Unclassified
Steam's windows can be resized to 1x1. On Windows they can't. The minimum size
for the main steam window is supposed to be 900x600 and for chat windows
396x351 according to tests.
Using openbox 3.5.0
--
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=13076
Summary: untangle: resize fails
Product: Wine
Version: 0.9.61.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wine(a)wnoise.ofb.net
After any of the games in Simon Tatham's portable puzzle collection is resized,
it only redraws the portion of the window that is the original size.
Under windows, these games rescale to fit in the new window size.
These may all be downloaded at
http://www.chiark.greenend.org.uk/~sgtatham/puzzles/
and have full source available.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=37864
Bug ID: 37864
Summary: When I resize a maximized MDI window it assumes the
new size instead of remaining maximized
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ryampolsky(a)yahoo.com
Distribution: ---
Created attachment 50431
--> https://bugs.winehq.org/attachment.cgi?id=50431
Screenshot showing a maximized MDI child after resizing 'unmaximizes' it.
My app is a 'smart terminal' that supports multiple sessions in MDI windows.
The size of the MDI child windows can be changed by the app running on the
server, so at the end of each transaction, if the app has changed the window
dimenensions, I resize the window. If my MDI window is maximized, this has no
effect on a Windows system (except that if I later unmaximize the MDI child, it
will display at the correct new size). But on recent WINE builds (Linux and
Mac), when I resize the MDI child, the window assumes the new size, even though
it's techincally in the 'mdi maximized' state (i.e., the MDI buttons are still
there on the menubar. If I switch between MDI children, they get redrawn
correctly maximized (including the one I just resized).
I coded a workaround in my app where I don't resize the window if it's
maximized, and that seems to work okay under WINE (though I guess the new size
info is getting lost). In any case, that verifies that the problem is
definitely happening in response to my resize operation.
F.Y.I., my resize operation uses SetWindowPlacement() to change the position
and size of the window - specifically because I don't want it to affect the
window if it's minimized or maximized. Only if it's in the normal state.
It's been a long time since I wrote this code, but again, it's always worked on
all versions of Windows. I have a feeling it might have worked a while back in
WINE - though I rarely run maximized, so I may have just recently noticed a bug
that's always been there...
Here's the basic code logic. SizeWindowForScreenDimentions calls
SetWindowPlacement based on the size calculated for the new row/column grid.
The code below has the workaround that prevents the problem in WINE. Also
attached a screenshot showing the unmaximized children with the MDI buttons
still on the menubar.
// If base screen dimensions don't match prior dimensions, resize the window
here.
// (unless mdi-maximized, in which case, doing this unmaximizes in WINE)
if (!mdi_maximized) {
if ((rows != old_rows) || (cols != old_cols)) {
SizeWindowForScreenDimensions(scr, rows, cols, &resizeable);
}
}
// In case window was hidden under an initial popup, show it now.
ShowWindow(scr->hScreenWnd, SW_SHOW);
--
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.