http://bugs.winehq.org/show_bug.cgi?id=7478
Summary: Unreal Tournament crashes
Product: Wine
Version: 0.9.30.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: wine-misc
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: sz__g(a)freemail.hu
Hello!
Unreal Tournament worked on 0.9.30, it crashes on 0.9.31
--
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=7448
------- Additional Comments From jisakiel(a)yahoo.es 2007-18-02 14:41 -------
Created an attachment (id=5005)
--> (http://bugs.winehq.org/attachment.cgi?id=5005&action=view)
tail of output with CFLAGS="-O0"
Should I check any prior attachment as obsolete, please just tell me (to save
space on the bugs server, perhaps). I don't know if they are to be replaced or
not, as I didn't have the time nor possibly the knowledge needed to read
through them...
--
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=7467
------- Additional Comments From focht(a)gmx.net 2007-18-02 14:38 -------
Hello,
next time you supply an executable, make sure you uncheck "UPX Stub" option when
using aut2exe tool.
Packed/protected executable add unnecessary overhead while
debugging/disassembling target.
>From what i've seen its a bug in autoit software itself and can be considered
harmless (at least in this case).
The compiled script app runs fine.
OleUninitialize() gets called in app shutdown code without any previous call to
OleInitialize().
Wine is a bit chattier about mismatched OLE init/uninit reference count - hence
the error message.
Native windows ole just ignores mismatched counts.
You could fix it by creating a "fake" ole object in your script like
$objShell = ObjCreate ("Shell.Application")
which implicitly calls ole init. The cleanup uninit whould then match.
Just report the bug to the authors of the autoit software.
They should use some flag to balance a call to OleUninitialize in their shutdown
code when OleInitialize has been called once (or not).
Regards
--
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=7448
------- Additional Comments From jisakiel(a)yahoo.es 2007-18-02 14:38 -------
OK, just O0... I noticed gentoo (I guess the ebuild) adds something else to the
flags automatically (as I exported CFLAGS="O0", CXXFLAGS="O0"): -fPIC -Wall
-pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wwrite-strings
-Wpointer-arith -O0
-fPIC is because of the PIC useflag, as I usually prelink (but I haven't since I
recompiled wine); could be stripped if needed. -pipe only accelerates the
compile, so shouldn't be a problem. -fno-strict-aliasing should not do any harm
(and if the mantainers of the ebuild leave it always on I guess it's for good
reasons). And the W are warnings, aren't they? At least I recognize Wall as
so... Nevertheless if they are a problem next time I will just unpack the source
and install under a prefix.
Still hangs, unfortunately.
By the way, I noticed 0.9.31 got released into gentoo, if necessary I can try
recompiling that one (but please with only a set of CFLAGS! :))
--
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=7473
tais.hansen(a)osd.dk changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
------- Additional Comments From tais.hansen(a)osd.dk 2007-18-02 14:31 -------
I had been playing with ulimit in the console from where I started wine which
didn't help. Apparently it just wasn't wine but X who was complaining here.
Increased maximum number of open files before starting X and the problem seems
to be gone. It's still odd that the limit doesn't seem to affect KDE but
that's another story.
Thanks.
--
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=7477
Summary: Uplink demo crashes
Product: Wine
Version: 0.9.30.
Platform: Other
URL: http://www.uplink.co.uk/demo_win32.html
OS/Version: other
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: test
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: spzakulec(a)mail.widener.edu
The version 1.54 demo of Uplink (for Windows) crashes Wine 0.9.31.
I've attached the Errorlog the game writes out.
--
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=7476
tehstealth(a)yahoo.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|critical |normal
OS/Version|Linux |other
------- Additional Comments From tehstealth(a)yahoo.com 2007-18-02 14:14 -------
Ok, so it's already a known bug, meaning it'll probably be fixed next version,
and I don't need to do this regression testing...?
Also, I've never done a "patch" to my Wine before, I suppose I'd use it in the
GIT tree that I have. Can you point me to a Howto on adding a patch? I suppose this:
diff --git a/dlls/wined3d/device.c b/dlls/wined3d/device.c
...is a command, and everything afterwards is the actual code of the patch...
--
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.